Path: /Applications/Colloquy.app/Contents/MacOS/ColloquyĮxception Codes: KERN_INVALID_ADDRESS at 0x000000000000000bĬrashed Thread: 0 Dispatch queue: -thread It looks like a trivial problem but my C skills are underwhelming.RAW Paste Data Copied Process: Colloquy Program received signal EXC_BAD_ACCESS, Could not access memory. Some module aborted the connection attempt Starting program: /Users/cb/work/server/native/znc/bin/znc -f -D -datadir=/dlh/native/znc.confd (gdb) run -f -D -datadir=/dlh/native/znc.confd
That authentication should occur at the same time so cleartext passwords do not have to be stored permanently. If ZNC is a proxy then it is probably safe to assume that both a connection to ZNC _as well_ as to the target server requires authentication. ZNC doesn't have to connect on startup, it can delay the initial outgoing connection until the first client incoming connection is made.
Colloquy bouncer password#
If that means that we can only login to the target IRC server when a user connects to ZNC (because only then will the cleartext password be available), that is probably fine. I think ZNC should be able to simply use the connecting users password when ZNC itself connects to the server. Ideally, I'd like to get rid of the clear text password here. This is the same password I use to connect to ZNC, which is stored in znc.conf as well but hashed.
My IRC server requires authentication with the IRC PASS operation, which works fine if I provide my password in cleartext in znc.conf:
0 kommentar(er)
