Subject: Re: Transport hexdump output

Re: Transport hexdump output

From: Sofian Brabez <sofian.brabez_at_wallix.com>
Date: Mon, 1 Feb 2010 13:35:47 +0100

On Mon, Feb 01, 2010 at 12:08:24PM +0100, Simon Josefsson wrote:
> Would you accept having two spaces instead? I find it annoying to not
> be able to visually find the 8-octet delimiter quickly. A colon or
> something really helps. With two spaces then it would look like:
>
> > => libssh2_transport_write send() (84 bytes)
> > 0000: 78 CE C0 22 88 B7 EE 84 28 DB FD 11 7C 72 76 4A : x.."....(...|rvJ
> > 0010: 2B 33 10 38 4A 29 A6 5C 91 89 34 C0 26 F5 91 34 : +3.8J).\..4.&..4
> > 0020: 1B BC 4A 3E E3 6D FD 29 81 3A 5A EA 2F 77 10 EF : ..J>.m.).:Z./w..
> > 0030: E9 00 6E B0 C7 38 C5 82 93 2D EA 89 44 9B FA 6A : ..n..8...-..D..j
> > 0040: F7 FB 9A 08 24 A6 D4 54 1B 4B 71 2B 2C 2F 27 18 : ....$..T.Kq+,/'.
> > 0050: 08 9C 68 3F : ..h?
>
> I think this is the most readable and still helpful for those of us
> still reading the hex output.
>

I'm agree, two spaces instead is most readable to visually find the
8-octets delimiter.

Btw, the displayed format it's not really important, but it was
strange when i've seen the colon in middle of dump. That's why i asked you
about this.

Regards

-- 
Sofian Brabez
Security R&D Engineer
Email: sbz_at_wallix.com
Website: www.wallix.com
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-02-01