Blockchain first 16 encrypted bytes, IV, and iter_count – all encoded in Base64:
Does it looks like “correct” PBKDF2-SHA1 or does
AAAAAA… indicate that something was broken?
During the login attemp to blockchain.info I get a response with a base64-encoded payload, that in fact authorizes my encrypted PBKDF2-SHA1 wallet. I have had no success trying to decrypt this (original BCI server/utils). I am absolutely sure that I’m using the correct passphrase (it's written on paper and was used successfully in 2016 and earlier 2017 before application update).
Anyway, the reason I’m asking if this looks like something suspicious and/or broken is that during my other analysis projects I never met a Base64 payload starting with 21 "A":
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c6 aa f3 09 f1 6c 41 a7 55 67 98 10 a2 73 2d 9d f0 b0 39 32 ec e9 96 22 ab 2f 76 ff 6b 2b c5 c9 c1 5a ... >
When I compare that to my other newly created accounts, this seems to be a bit weird, since all other accounts produce payloads with a more random sequence at start… for example
Do those 21
As in that one payload (related to one specific account) point to a security or cryptographic problem?