Am 21.04.13 22:29, schrieb Evan Huus:
>> There is only one issue left: How can I split up this string. The
>> g_strsplit() function seems to don't accept NULL as a delimiter.
>
> It depends what you need the results for. If you just need them
> separated by a NULL then they're already in that sta
On Sun, Apr 21, 2013 at 4:22 PM, Uli Heilmeier wrote:
> Hi,
>
> Thanks for both replies!
> I did a complete clean-up of my code and now the decoded string is 14
> bytes long. So the epan_base64_decode() function is working correct.
>
> Sorry for the work and the confusion.
>
> There is only one is
Hi,
Thanks for both replies!
I did a complete clean-up of my code and now the decoded string is 14
bytes long. So the epan_base64_decode() function is working correct.
Sorry for the work and the confusion.
There is only one issue left: How can I split up this string. The
g_strsplit() function se
Hi,
On Wed, Apr 17, 2013 at 10:27:42PM +0200, Uli Heilmeier wrote:
> With the PLAIN mechanism the packet has a base64 encoded string containing:
> [authorization user](\x00)[authentication user](\x00)[password]
>
> For example:
> dGVzdAB0ZXN0ADEyMzQ= contains test(NUL)test(NUL)1234
>
> I tried t
Glib has g_base64_decode_inplace as of 2.20 so you could try using
that. We support way back to 2.14 at the moment so we keep
epan_base64_decode() available, but if the glib function works it's
probably a bug in our code.
Evan
On Wed, Apr 17, 2013 at 4:27 PM, Uli Heilmeier wrote:
> Hello list,
>
Hello list,
I'm currently trying to improve the SMTP dissector regarding the AUTH command.
Up to now I finished the 'AUTH LOGIN' mechanism (s. Bug 8591). Next I
would like to decode the 'AUTH PLAIN' mechanism (RFC 4616).
With the PLAIN mechanism the packet has a base64 encoded string containing:
