Displaying 3 results from an estimated 3 matches for "206c".
Did you mean:
206
2013 Jan 05
1
imap: Error: net_connect_unix(/.../auth-master) failed: Invalid argument
...t4 0
303 dovecot CALL gettimeofday(0xbfbfc888,0)
303 dovecot RET gettimeofday 0
303 dovecot CALL kevent(0x2f,0,0,0x806b000,0x35,0xbfbfc8c0)
768 imap-login CALL write(0x2,0x804f570,0xbb)
768 imap-login GIO fd 2 wrote 187 bytes
0x0000 0102 3736 3820 496e 7465 726e 616c 206c |..768 Internal l|
0x0010 6f67 696e 2066 6169 6c75 7265 2028 7069 |ogin failure (pi|
0x0020 643d 3736 3820 6964 3d31 2920 2869 6e74 |d=768 id=1) (int|
0x0030 6572 6e61 6c20 6661 696c 7572 652c 2031 |ernal failure, 1|
0x0040 2073 7563 6365 7366 756c 2061 7574 6873 |...
2002 Dec 20
3
Bad packet length problem with "aes128-cbc" and openssh3.1p1
Hi,
I am trying to run openssh 3.1p1. But it is giving "Bad packet length" error
when I run sshd with default config file. On further investigation I found
that the error is coming only for the cipher algorithm "aes128-cbc". Also
the error comes only when I don't specify any protocol file
(/usr/local/etc/ssh_host_[rd]sa_key) or specify only "protocol 2" files.
I
2008 Jul 14
5
EOL in stderr of ssh - Linux
Hello everyone,
recently I've found something I consider a bug.
Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A.
Imagine my surprise when I saw that all messages that are being output
on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are
terminated with 0x0D, 0x0A.
Maybe that's standard behaviour of all stderr messages in all Linux