| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both the constructor “Sid.create” and the string format parser must
reject inputs lacking a subauthorities array of at least size one. Since
the array is no longer optional, reorder the the constructor arguments
to match the data representation.
It is still possible to create SIDs without subauthorities via the
“Sid.create_unsafe” constructor. Also, the packet representation will
happily accept them because their definition (as well as that that of
the identical RPC version) does not specify a minimum count.
This is all rather ambiguous and exacerbated by the fact that [MS-DTYP]
happily specifies an invalid SID “S-1-5” as the “NT_AUTHORITY”. However,
both the grammar and the Win API “ConvertStringSidToSidA()” function
reject SA-less inputs as invalid, so we should too.
|
|
|
|
| |
Establish symmetry with of_string / to_string and the StringFmt module.
|
|
|
|
| |
Reject ia’s greater than six bytes can encompass.
|
| |
|
| |
|
|
|
|
| |
Add the constants from MS-DTYP 2.4.2.4 to Sid.WellKnown.
|
| |
|
|
|
|
|
|
| |
Get rid of all “StringFmt” APIs involving exceptions.
There is now only the “decode” function which returns
a result type.
|
| |
|
| |
|
|
|
|
|
| |
Oddly enough this only has an effect on the sub_auths since the 48 bits
of “identifier authority” are always handled in big endian.
|
| |
|
| |
|
|
|