java – ASN. 1 encoding – decoding

I am currently developing a client server program, a client in Java / C and a server in C

In this case, I realized the importance of using some transmission protocols to identify data and transfer data effectively

On this point, my question is: ASN Is 1 a good agreement? I know OpenSSL on BC (on Java) and C supports it So use ASN Is 1 notation a good idea to transfer data between the client and the server?

Can you give me some starting points? If you have a better understanding of the existing agreement, please let me know

thank you!!

Solution

BC and OpenSSL only support ASN A small part of 1 In fact, there was no complete ASN for a long time Implementation, at least for the public Telecommunications and telephone equipment manufacturers may have a fairly complete ASN 1. Implementation At present, the most advanced ASN is open to the public 1 the implementation was developed as part of the osmocom project. Harald Welte wrote on his blog: http://laforge.gnumonks.org/weblog/2011/04/12#20110412 -mapv1_ available

Worse, ASN 1. In particular, its highly redundant coding scheme (at least three different methods to encode strings in ASN. 1) has become the cause of several security problems in the past few years because of the problems caused by its correct handling of x509 certificates X509 is another crushing technology from hell. With all due respect, it is better avoided Of course, SSL depends on it, but getting a certificate signed by a "trusted" CA doesn't mean anything; Any CA can sign any domain. After viewing, your browser trusts me by default and no longer trusts my browser

So in short: ASN 1 has been broken and should be avoided in the new design Its only major use outside the telephone network is the x509, which has also been broken So I won't use it Use JSON, bson, protocol buffer, netstrings or something sensible