[erlang-questions] asn1 and the new ssl module

[Jakob Cederlund]

thisIt was very useful, thanks!
And here is a patch. It simply adds asn1 package support for the new 
ssl. It should work with R12B-1, and probably fine with R12B.
Hope this helps!
/Jakob


Pablo Polvorin wrote:
> Thanks for the clarification!
>
> ...it isn't a patch, .. probably it isn't usefull  to you. .
> anyway, this is the code i'm using
> http://ppolv.wordpress.com/2008/02/15/erlang-ssl-and-asn1/
>
> cheers
> pablo
>
> 2008/2/15, Jakob Cederlund <jakob@REDACTED>:
>   
>> Nope, not yet.
>>  Currently, the new ssl (the one you get with {ssl_imp, new}) only
>>  supports these packet-options: raw, 1, 2, 4, cdr and line. (Packaging is
>>  handled by the function ssl_connection:check_packet/3.) The rest are
>>  fairly easy to add, and we hope to do that in the next release. Patches
>>  are welcome! :-)
>>
>> /Jakob
>>
>>
>>  Pablo Polvorin wrote:
>>  > Hi all,
>>  > I'm using the new ssl module to "upgrade" a gen_tcp socket to ssl. But
>>  > I couldn't find a way to easily receiving asn1 packets from it.
>>  > My question is, it's possible to use the {packet,asn1} option when
>>  > using the new ssl module?.
>>  >
>>  > ssl_connection.erl seems to not have any reference to that option.
>>  >
>>  > Finally  I implemented the buffering and packet delimiting code in my
>>  > application, but I wonder if there is an easy and early way to
>>  > accomplish the same.
>>  > regards,
>>  >
>>
>>
>>     
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080220/4b4c1fa7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ssl_asn1.patch
Type: text/x-patch
Size: 1129 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080220/4b4c1fa7/attachment.bin>