Displaying 5 results from an estimated 5 matches for "6f67".
Did you mean:
667
2006 Nov 16
1
[3.0.23d] winbind: ads_connect for domain X failed: Operations error
...4 6f6d .....>....DnsDom
0x0040: 6169 6e04 1161 6474 6573 742e 6c69 6e62 ain..adtest.linb
0x0050: 6f78 2e63 6f6d a30d 0404 486f 7374 0405 ox.com....Host..
0x0060: 5044 4330 31a3 0d04 054e 7456 6572 0404 PDC01....NtVer..
0x0070: 0600 0000 300a 0408 4e65 744c 6f67 6f6e ....0...NetLogon
17:23:25.902620 IP 192.168.0.247.389 > 172.20.0.221.33128: UDP, length: 193
0x0000: 4500 00dd 5324 0000 7f11 795b c0a8 00f7 E...S$....y[....
0x0010: ac14 00dd 0185 8168 00c9 afb3 3084 0000 .......h....0...
0x0020: 00a5 0201 0464 8400 0000 9c04...
2013 Jan 05
1
imap: Error: net_connect_unix(/.../auth-master) failed: Invalid argument
...(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 | succesful auths|
0x0050 293a 207...
2004 Dec 08
0
dovecot 1.0-test-56 mail doesn't show up with Mac Entourage clients
...7261 6e73 n..Content-Trans
0x00a0: 6665 722d 456e 636f 6469 6e67 3a20 7175 fer-Encoding:.qu
0x00b0: 6f74 6564 2d70 7269 6e74 6162 6c65 0d0a oted-printable..
0x00c0: 0d0a 0d0a 0d0a 2d2d 3d2d 4e68 4c71 2f62 ......--=-NhLq/b
0x00d0: 2b37 5a69 3852 4752 3473 5570 6f67 0d0a +7Zi8RGR4sUpog..
0x00e0: 436f 6e74 656e 742d 5479 7065 3a20 6170 Content-Type:.ap
0x00f0: 706c 6963 6174 696f 6e2f 7067 702d 7369 plication/pgp-si
0x0100: 676e 6174 7572 653b 206e 616d 653d 7369 gnature;.name=si
0x0110: 676e 6174 7572 652e 6173 630d 0a43...
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
2016 Nov 21
2
Winbind traffic not encrypted
...0 0005 1500 0000 1...............
0x01a0: c816 e03b 4e0e eba9 3755 a787 5204 0000 ...;N...7U..R...
0x01b0: 3027 040e 6163 636f 756e 7445 7870 6972 0'..accountExpir
0x01c0: 6573 3115 0413 3932 3233 3337 3230 3336 es1...9223372036
0x01d0: 3835 3437 3735 3830 3730 1104 0a6c 6f67 8547758070...log
0x01e0: 6f6e 436f 756e 7431 0304 0130 3019 040e onCount1...00...
0x01f0: 7341 4d41 6363 6f75 6e74 4e61 6d65 3107 sAMAccountName1.
0x0200: 0405 7573 6572 3230 1d04 0e73 414d 4163 ..user20...sAMAc
0x0210: 636f 756e 7454 7970 6531 0b04 0938 3035 countType1...80...