On Thu, Feb 27, 2025 at 9:44 AM Paul Wouters <paul.wout...@aiven.io> wrote:
>
> paul@thinkpad:/tmp$ echo aYhba4dGQEHhs3uEe6CuLN4ByNQ= | base64 -d |
> hexdump
> 0000000 8869 6b5b 4687 4140 b3e1 847b a07b 2cae
> 0000010 01de d4c8
> 0000014
>
> Note my output has 88:69:6B:5B[....] and you have [69:88:5B:6B][...]
>
> I assume it is a network vs host order issue. I just wanted to make sure
> there is no confusion here for people.
>
Ah! Yes, this makes sense. By default, hexdump respects the endianness of
the host machine, and x86_64 is a little-endian architecture. You can ask
hexdump to instead provide the canonical output regardless of host machine
endianness, and then you see the expected result:
$ echo aYhba4dGQEHhs3uEe6CuLN4ByNQ= | base64 -d | hexdump --canonical
00000000 69 88 5b 6b 87 46 40 41 e1 b3 7b 84 7b a0 ae 2c |i.[k.F@A.
.{.{..,|
00000010 de 01 c8 d4 |....|
00000014
Thanks,
Aaron
_______________________________________________
Acme mailing list -- acme@ietf.org
To unsubscribe send an email to acme-le...@ietf.org
