Feature - Ability to specify GUID or generate pseudo-GUID #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add ability to generate pseudo-guid, it uses only srand() and so pseudo
if GUID is not specified - pseudo-guid will be generated
sh also can accept switch -G, but by default this switch is not specified(corresponding variable is empty)
commented guids removed from code and can be found below
proof of GUID on example of values that were commented out in main()
version (4 bits, always 4)
| variation (2 bits as 0b10, so only 8,9,A,B)
| |
| Data1 | Data2 | Data3 v | v Data4 | <- GUID layout
0xDD, 0x43, 0x67, 0xE3, 0x2B, 0xAB, 0xE1, 0x44, 0xB7, 0xCB, 0xEC, 0x31, 0xCE, 0xB9, 0xD5, 0xA6
0xEF, 0xAB, 0xFC, 0x01, 0x4F, 0xD8, 0x47, 0x42, 0xA0, 0x0B, 0x7C, 0x78, 0x8E, 0x6D, 0xD1, 0xC1
0x58, 0x72, 0xA5, 0x5B, 0xFE, 0xF3, 0xCD, 0x46, 0x91, 0x3C, 0xEF, 0x00, 0xC7, 0x7A, 0x97, 0x69
0x59, 0x72, 0xA5, 0x5B, 0xFE, 0xF3, 0xCD, 0x46, 0x91, 0x3C, 0xEF, 0x00, 0xC7, 0x7A, 0x97, 0x69
why is the version byte mixed up - https://devblogs.microsoft.com/oldnewthing/20220928-00/?p=107221
in short - the GUID is chunked in v1 fashion and stores bytes in each of first three chunks in LE order
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
shscript and program now can accept optional-Gswitch followed by GUID in one of three UUID formats:windows(38 symbols) -
{00000000-0000-4000-8000-000000000000}general(36 symbols) -
00000000-0000-4000-8000-000000000000dashless(32 symbols) -
00000000000040008000000000000000used GUID is UUID version 4 variation 1
if GUID is specified - its certain bytes will be validated according to RFC 9562 section 4.1 and 4.2 plus dash and curly braces, all based on the value length.
if not specified - pseudo-GUID will be generated
if specified GUID is invalid - program will exit with error message and code 1
switch is optional, but default value not specified because value, produced by for-loop is actually invalid UUIDv4.
So you can use one of the GUID that were commented in main() or keep it blank and let program generate it
commented GUIDs in general format:
E36743DD-AB2B-44E1-B7CB-EC31CEB9D5A601FCABEF-D84F-4247-A00B-7C788E6DD1C15BA57258-F3FE-46CD-913C-EF00C77A97695BA57259-F3FE-46CD-913C-EF00C77A9769note: generator uses
srand()(allowed by RFC) and so GUID called pseudo, so you can generate one with other tool and use itnote:
shscript not tested on live system, only some constructions, used in it, in online compilersnote: this feature assumed to be merged on top of the time feature, but not necessary. On merging after the time feature there expected few conflicts, be careful with
getopt do:h:O:A:lines