Data.Conduit.Network.TLS

allow to build a server config directly from raw bytestring data (exact same string as if the certificates were read from the filesystem). this enables to plug another backend to fetch certifcates (other than FS)

Like tlsConfigBS, but also allow specifying chain certificates.

Since 1.1.1

Like tlsConfig, but also allow specifying chain certificates.

Since 1.1.1

Create an AppData from an existing tls Context value. This is a lower level function, allowing you to create a connection in any way you want.

Sample usage:

import Network.Simple.TCP.TLS

myapp :: Application IO
...
main = do
    cset <- getDefaultClientSettings
    connect cset "host" "port" $
        (\(ctx, addr) -> myapp $ tlsAppData ctx addr Nothing)

Since 1.0.1

Like runTCPServerTLS, but monad can be any instance of MonadUnliftIO.

Note that any changes to the monadic state performed by individual client handlers will be discarded. If you have mutable state you want to share among multiple handlers, you need to use some kind of mutable variables.

Since 1.1.2

run a server un-crypted but also pass a call-back to trigger a StartTLS handshake on the underlying connection

Sample usage:

runTCPServerStartTLS serverConfig $ \(appData,startTLS) -> do
  abortTLS <- doSomethingInClear appData
  unless abortTLS $ startTls $ \appDataTls -> do
    doSomethingSSL appDataTls

Settings type for TLS client connection.

Since 1.0.2

Smart constructor for TLSClientConfig.

Since 1.0.2

Run an application with the given configuration.

Since 1.0.2

Run an application with the given configuration. starting with a clear connection but provide also a call back to trigger a StartTLS handshake on the connection

Since 1.0.2

Since 1.0.2

Since 1.0.2

Default is True. If set to False, will make a non-TLS connection.

Since 1.0.2

TLS settings to use. If not provided, defaults will be provided.

Since 1.0.2

Socks configuration; default is Nothing. If absent, Socks will not be used.

Since 1.0.2

Connection context. Default is Nothing, which will generate a new context automatically. If you will be making many connections, it's recommended to call initConnectionContext yourself.

Since 1.0.2

Read from a Connection.

Write to a Connection.