On 11/04/2015 11:21 AM, JBarry wrote:
The oid is encoded according to DER rules for encoding oids. In general the first 2 bytes encode to a single byte, and bytes under 128 encode to themselves.Hi Bob,Thank you for the helpful reply. I have looked at the files you have mentioned and am a little confused about something. For example (secoid.c lines 34-35): /* USGov algorithm OID space: { 2 16 840 1 101 } */ #define USGOV 0x60, 0x86, 0x48, 0x01, 0x65 In this snippet, the OID appears to be 2.16.840.1.101. However, the hex translation does not equal the decimal string because 0x60, 0x86, and 0x48 do not translate to 2, 16, 840 respectively, but 0x1 and 0x65 do convert to 1 and 101. Clearly I am missing something here in how to convert between the two. I am also waiting to hear back from my supervisor as to whether or not I can disclose the OID and its purpose. Thanks again, Jim
Microsoft had a decription here: https://msdn.microsoft.com/en-us/library/windows/desktop/bb540809%28v=vs.85%29.aspx A program which does it can be found here: http://www.rtner.de/software/oid.html (I have not verified the program myself).
bob
-- View this message in context: http://mozilla.6506.n7.nabble.com/Add-New-OID-to-NSS-tp346875p346880.html Sent from the Mozilla - Cryptography mailing list archive at Nabble.com.
smime.p7s
Description: S/MIME Cryptographic Signature
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
