using network+conduit+tls for a client application?
Dear Haskellers, I wanted to write a small TLS application (connecting to IMAP over TLS) and it seemed natural to use conduit for that. I found the network-conduit-tls package, but then I realized it's meant only for server applications. Is there something similar for client applications? Thank you, Petr Pudlak
there's a similar one for client
http://hackage.haskell.org/package/http-conduit-browser/
2013/7/29 Petr Pudlák
Dear Haskellers,
I wanted to write a small TLS application (connecting to IMAP over TLS) and it seemed natural to use conduit for that. I found the network-conduit-tls package, but then I realized it's meant only for server applications. Is there something similar for client applications?
Thank you, Petr Pudlak
______________________________**_________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/**mailman/listinfo/haskell-cafehttp://www.haskell.org/mailman/listinfo/haskell-cafe
I've actually been intending to add the client side code to that package,
but I simply haven't gotten around to it yet. It's actually not that
complicated, but it does require some thought on the right interface for
things like approving/rejecting server side certificates. If you open up an
issue on Github for this, I'd be happy to continue the conversation there
and we can try to get out a new version of the library. (I just don't want
to spam the Cafe with an exploratory design discussion.)
On Mon, Jul 29, 2013 at 11:08 AM, Petr Pudlák
Dear Haskellers,
I wanted to write a small TLS application (connecting to IMAP over TLS) and it seemed natural to use conduit for that. I found the network-conduit-tls package, but then I realized it's meant only for server applications. Is there something similar for client applications?
Thank you, Petr Pudlak
______________________________**_________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/**mailman/listinfo/haskell-cafehttp://www.haskell.org/mailman/listinfo/haskell-cafe
On 07/29/2013 10:43 AM, Michael Snoyman wrote:
I've actually been intending to add the client side code to that package, but I simply haven't gotten around to it yet. It's actually not that complicated, but it does require some thought on the right interface for things like approving/rejecting server side certificates. If you open up an issue on Github for this, I'd be happy to continue the conversation there and we can try to get out a new version of the library. (I just don't want to spam the Cafe with an exploratory design discussion.)
Michael, I've been meaning to add TOFU (Trust on first use) and certificate exceptions support (e.g. self signed) inside the TLS stack directly, maybe we should talk about this. Few design stuff that blocked me so far, one of them is how to store those things. -- Vincent
On 07/29/2013 09:08 AM, Petr Pudlák wrote:
Dear Haskellers,
I wanted to write a small TLS application (connecting to IMAP over TLS) and it seemed natural to use conduit for that. I found the network-conduit-tls package, but then I realized it's meant only for server applications. Is there something similar for client applications?
Hi Petr, There's 2 packages that provide easy client TLS side API. I don't think it would be difficult to provide a conduit wrapper for both: http://hackage.haskell.org/package/network-simple-tls http://hackage.haskell.org/package/connection connection is a bit more low level for easily integration into something higher level. -- Vincent
participants (4)
-
14875 -
Michael Snoyman -
Petr Pudlák -
Vincent Hanquez