<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
thisIt was very useful, thanks!<br>
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.<br>
Hope this helps!<br>
/Jakob<br>
<br>
<br>
Pablo Polvorin wrote:
<blockquote
cite="mid:1ffe809c0802151131s2fd81c16vdb7aebd67fabd51@mail.gmail.com"
type="cite">
<pre wrap="">Thanks for the clarification!
...it isn't a patch, .. probably it isn't usefull to you. .
anyway, this is the code i'm using
<a class="moz-txt-link-freetext" href="http://ppolv.wordpress.com/2008/02/15/erlang-ssl-and-asn1/">http://ppolv.wordpress.com/2008/02/15/erlang-ssl-and-asn1/</a>
cheers
pablo
2008/2/15, Jakob Cederlund <a class="moz-txt-link-rfc2396E" href="mailto:jakob@erix.ericsson.se"><jakob@erix.ericsson.se></a>:
</pre>
<blockquote type="cite">
<pre wrap="">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,
>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>