CALICO(1)
π CALICO(1): calico β dispatches cat π
(General Commands Manual, but make it group chat) π«Ά
π NAME π
calico β dispatches cat. that's the whole name, bestie, and she said what she said π
β¨
β¨ SYNOPSIS β¨
calico [-H host] [-P port] [-t timeout] directory
πΈ DESCRIPTION πΈ
okay so the calico program dispatches incoming TLS connections to instances of pounce(1) by Server Name Indication (SNI). bestie, that's the whole vibe: SNI in, right pounce(1) instance out π
Instances of pounce(1) should be configured with -U to bind to UNIX-domain sockets in the directory passed to calico. yes, -U, UNIX-domain sockets, the whole little socket situation π«Ά
β οΈ note note note:calicois not a proxy. Incoming connections are passed directly to instances ofpounce(1), which handle TLS negotiation. Instances ofpounce(1)andcalicocan be restarted independently of each other. iconic separation, no cap π
okay bestie, the arguments are as follows:
-H hostβ Bind to host. The default host islocalhost. like,localhostis the main character unless u say otherwise π-P portβ Bind to port. The default port is6697. iconic port fr π₯-t timeoutβ Set the timeout in milliseconds after which a connection will be closed if it has not sent theClientHellomessage. The default timeout is1000milliseconds. noClientHello? bye πdirectoryβ The path to the directory containingpounce(1)UNIX-domain sockets. yes bestie,directoryis right there and it matters π
π EXAMPLES π
okay so start and dispatch to two instances of pounce(1):
$ pounce -U /var/run/calico -H oftc.example.org oftc.conf
$ pounce -U /var/run/calico -H libera.example.org libera.conf
$ calico -H example.org /var/run/calico
The two instances can be connected to via oftc.example.org:6697 and libera.example.org:6697, respectively. literally two little hostname eras, slay π
π¦ SEE ALSO π¦
pounce(1)β the whole reason we're here, go read it bestie π«Ά
π STANDARDS π
- D. Eastlake 3rd, Transport Layer Security (TLS) Extensions: Extension Definitions, IETF, RFC 6066, https://tools.ietf.org/html/rfc6066, January 2011.
- E. Rescorla, The Transport Layer Security (TLS) Protocol Version 1.3, IETF, RFC 8446, https://tools.ietf.org/html/rfc8446, August 2018.
π AUTHORS π
June McEnroe <june@causal.agency> π
π BUGS π
Send mail to β¨list+pounce@causal.agencyβ© or join #ascii.town on irc.tilde.chat. that's the whole bug situation, bestie ππ«Ά
π Debian β’ August 27, 2020 β’ CALICO(1) β’ byeee bestie, mwah! π
π¦ where this page comes from
- nixos 26.05: pounce 3.1
- nixpkgs unstable: pounce 3.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms