Home
Date Settings According to «ISO 8601 Format»
Looking for an unambiguous calendar-and-clock format that is internationally understood? It’s time for ISO 8601.
This ISO standard helps remove doubts that can result from the various day–date conventions, cultures and time zones that impact a global operation. It gives a way of presenting dates and times that is clearly defined and understandable to both people and machines.
What can ISO 8601 do for me?
When dates are represented with numbers they can be interpreted in different ways. For example, 01/05/12 could mean January 5, 2012, or May 1, 2012. On an individual level this uncertainty can be very frustrating, in a business context it can be very expensive. Organizing meetings and deliveries, writing contracts and buying airplane tickets can be very difficult when the date is unclear.
ISO 8601 tackles this uncertainty by setting out an internationally agreed way to represent dates:
YYYY-MM-DD
For example, September 27, 2012 is represented as 2012-09-27.
ISO 8601 can be used by anyone who wants to use a standardized way of presenting:
- Date
- Time of day
- Coordinated Universal Time (UTC)
- Local time with offset to UTC
- Date and time
- Time intervals
- Recurring time intervals
ISO 8601 only specifies numerical notations and does not cover any dates and times in which words are included.
It’s not intended as a substitute for language-dependent wording, such as «February 1, 2032».
https://www.iso.org/iso-8601-date-and-time-format.html
https://www.ionos.com/digitalguide/websites/web-development/iso-8601/
Microsoft Windows 11 add the following registry key for quick result:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Control Panel\International]
"sShortDate"="yyyy-MM-dd"
... or you may use
PowerShell:
$currentThread = [System.Threading.Thread]::CurrentThread
$culture = $CurrentThread.CurrentCulture.Clone()
$culture.DateTimeFormat.ShortDatePattern = 'dd-MM-yyyy'
$currentThread.CurrentCulture = $culture
$currentThread.CurrentUICulture = $culture
- Details
Self-Signed Certificate
https://docs.microsoft.com/en-us/windows/win32/seccertenroll/cng-cryptographic-algorithm-providers
Create a Self-Signed Certificate Using PowerShell
CNG Cryptographic Algorithm Providers
Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation
Example
New-SelfSignedCertificate -Type Custom -Subject "My Subject.." `
-KeyUsage DigitalSignature `
-KeyDescription "My Key" `
-KeyExportPolicy ExportableEncrypted `
-FriendlyName "My Friendly Name" `
-CertStoreLocation "Cert:\CurrentUser\My" `
-TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.3", "2.5.29.19={text}")
switches (only those of interest)
-Subject "Urs Salvisberg"
-FriendlyName "MyFriendlyName"
-CertStoreLocation "Cert:\CurrentUser\My"
-HardwareKeyUsage
Specifies how a hardware key associated with the new certificate may be used.
This parameter applies only when you specify the Microsoft Platform Crypto Provider.
The acceptable values for this parameter are:
None (default)
SignatureKey
EncryptionKey
GenericKey
StorageKey
IdentityKey
-KeyDescription "My Key"
-KeyExportPolicy ExportableEncrypted
-KeyFriendlyName "Urs dodo xx"
-KeyLength 32
login.microsoftonline.com is blocked
login.microsoftonline.com refused to connect.
-NotAfter
-NotBefore
- Details
Page 4 of 5