asn.1

Its's been a while since I've written ASN.1 so.. Our data model is comprised of several table definitions within a table. This is not workable in SNMP, so we need to flatten the definitions. The easiest way to do this would be to have the embedded table indexed by the same OID as the parent table. Thus someTableEntry ::= SEQUENCE { someTableIndex Integer32, someTableDomain Integer32, someTableFooTable SEQUENCE OF SomeTableFooTable } becomes someTableEntry ::= SEQUENCE { someTableIndex Integer32, someTableDomain Integer32, } someTableFooTable ::= SEQUENCE { someTableIndex Integer32, .... } The

Is there a way to determine programmatically if the currently running app was built and signed for development only or whether it was built for distribution? And can one determine if was build for app store or ad hoc distribution? Is it e.g. possibly to access the code signature and get the information from there? Or are there certain files present in one of variants that don't exist in the other ones? Is part of the bundle info? Or can it be derived from the executable file? Any hints are appreciated. It seems that the embedded.mobileprovision file is in ASN.1 format. The easiest way to check

I'm trying to read a custom extension from a digital certificate. I know the value is a GeneralString encoded in DER. Is there an easy way to correctly decode it and get a Java String? I tried the following, but 's' includes some of the encoding metadata as junk characters at the start of the string. byte[] ext = cert.getExtensionValue("1.2.3.4"); String s= new String(ext); System.out.println(s); Is there a quick and easy way to do this? Or do I really need to use some full fledged ASN.1 library? Thanks! BouncyCastle is (among everything else): A library for reading and writing encoded ASN.1

I'm looking into a mechanism for serialize data to be passed over a socket or shared-memory in a language-independent mechanism. I'm reluctant to use XML since this data is going to be very structured, and encoding/decoding speed is vital. Having a good C API that's liberally licensed is important, but ideally there should be support for a ton of other languages. I've looked at google's protocol buffers and ASN.1 . Am I on the right track? Is there something better? Should I just implement my own packed structure and not look for some standard? Given your requirements, I would go with Google

I'm currently trying to create an RSACryptoServiceProvider object solely from a decoded PEM file. After several days of searching, I did manage to wrangle a working solution but it's not one that would be production ready. In a nutshell, in order to create an RSACryptoServiceProvider object from the bytes that make up the public key in a PEM file, I must create the object specifying the keysize (currently 2048 using SHA256, specifically) and then importing a RSAParameters object with the Exponent and Modulus set. I'm doing this as so; byte[] publicKeyBytes = Convert.FromBase64String