Mikael Szreder

There are multiple issues here: # First Issue An example of a message which failes to decode is the initial TOTP message, which is always base32 encoded. https://github.com/BishopFox/sliver/blob/c8a7948671eafba4d6f871c2f2b46b900202699d/implant/sliver/transports/dnsclient/dnsclient.go#L926-L937 The problem...

Sorry, but I do not understand. The code I referenced in the previous comment is from the master branch and not to the 1.5.x/master branch. Is there a more updated...

> I'm having this issue even with force-base32 enabled. Should this work or is it a problem with my setup? Unfortunately no. The base32 encoder does not force lowercase characters,...

@to016 It has been a while since I was looking at this. Based on a cursory look, you are correct. Removing the error, is however not correct. The first location...

@to016 `decodeSubdata` will return a `nil` value in the `msg` variable. Which will fail in subsequent lines. We also don't want to attempt to interpret an invalid message incorrectly.

I believe this might have to do with the fact that strings in Go are not null-escaped. This causes the strings to continue untill a null character is found. A...