> Here's the patch to sic trunk to support this, it adds a new
> argument (-a) that needs to be an base64 encoded SASL PLAIN response.
Passing secrets in argv may be quite harmful. I can't imagine a use
case where you'd not want a wrapper to read the secret in from a file
or unnamed pipe.
Some servers, like freenode when used with Tor[1] require user authentication
on connect via SASL against the NickServ database. This done using CAP[2]
command and simple SASL exchange[3].
Here's the patch to sic trunk to support this, it adds a new
argument (-a) that needs to be an base64 enco