[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] decode base64 auth info in -snoop output?
From: |
David Levine |
Subject: |
Re: [Nmh-workers] decode base64 auth info in -snoop output? |
Date: |
Sat, 13 Aug 2016 12:12:30 -0400 |
Ken wrote:
> I don't think you can make an assumption what the _decoded_ base64 SASL
> tokens are; that is just talking about what appears in the AUTH messages,
> not what the tokens contents are. I mean, we can't even make an assumption
> with regards to character set without knowing more about the particular
> SASL mechanism.
I'm not sure, but in any case, there's no character set identification. So I
know what else we can do, other than display a single byte at a time, with
hexified non-printable (as ASCII) bytes.
> >I'd rather not extend the length of the current indications such as
> >tls-decrypted and sasl-decrypted. tls-b64decryp and sasl-b64decryp ?
>
> Well, if you're using pure SASL encryption/decryption, encryption doesn't
> start until SASL is complete, so I'm not sure that works.
Looking at the code, it should. But I like this better, anyway:
> Here's an idea. How about:
>
> 334 b64<Username:>
> b64<address@hidden>
David
Re: [Nmh-workers] decode base64 auth info in -snoop output?, Valdis . Kletnieks, 2016/08/12