The passcode format is as in all the previous 13ar challenges XXXXXX<Keyword>13ar where XXXXXX is digits and letters. Getting 13ar is part of the decoding again.
Base32 uses a 32-character set comprising the twenty-six upper-case letters A–Z, and the digits 2–7.
So no, you're not wrong.
And it doesn't appear to be Base64, either; at the very least, not straight Base64. (It's possible there might be something we can do to this to get a Base64 string that can be further processed, but...)
ETA: To be clear, if this is Base64, it's not any standard Base64 encoding, as all the standard ones I've tried - barring UTF-16 - net me little more than gibberish loaded with unprintable characters, and UTF-16 gets you nothing but nonsense in Chinese.
(And near as I can tell, Base128 isn't a thing, because that would impinge on the ASCII 'control codes', like BEL [the 'bell' character, which triggers an alert on the receiving terminal], SOT [Start Of Transmission], and EOT [End Of Transmission]...)
ok, got groups of 3 alphanumeric chars, a keyword a bit of known plain-text. applying cryptoanalysis yields 3 possible passcodes. of course none of them works :-/
finally got it... I have to admit, this is the meanest, most evil challenge so far. I can not say why because that would spoiler the work of the past 3 hours.. perhaps tomorrow... it is just not right.
You and me both. I mean, I saw someone comment that he got base32 to yield something, but the original character string can't be base32 because it contains characters outside the base32 encoding scheme... and if it's base64, it ain't no base64 I've ever used before (and it's very precisely encoded, so that it didn't need the == padding you commonly see in other puzzles that use base64).
This is my first decoding with these challenges, so it's a bit more difficult. Some of the hints are starting to click in - no 0, 1, 8 or 9 in Base32, yet there is a 1 and lots of 8's and 9's, still reading into it on how to decode that...
Not sure how to solve the whole thing yet, but got to "jJTWF..." part and this decoder has been VERY useful for experimenting that got me there:
gchq.github.io/CyberChef
It has hex, base32, 64, etc., reverse and so on...
EDIT: Got from "jJTWF..." to "Y3c" and I clearly see there is a pattern in what I did that keeps repeating (pattern given by "n2esab" and "4" but not sure if "^3" means I should repeat it 3 times what I did), but now I guess something else is needed to make sense of "Y3c"
Same question here ... I cannot see how to keep progressing as the next 2x level does not appear to exist and no other related method appears to go anywhere
Comments
This is for a fact.
Are there any red herring or all clues stated are legit?
yeah, i'm pretty sure the significance of 4^3 is eluding me.
i am absolutely convinced this is base32.
i am also convinced i need sleep.
I got a base32 thing to work but have no idea what to do with the output.
I have a guess that the output is x###<keyword>#x#x###xx. Is anyone able to confirm or reject this?
The passcode format is as in all the previous 13ar challenges XXXXXX<Keyword>13ar where XXXXXX is digits and letters. Getting 13ar is part of the decoding again.
I thought Base32 could not include the numeral 1, 8 or 9. Therefore this can't be Base32 (for the first step)...? Am I wrong?
Glad to say I finally am ... any progress from here? And is this the right path?
According to Wikipedia:
Base32 uses a 32-character set comprising the twenty-six upper-case letters A–Z, and the digits 2–7.
So no, you're not wrong.
And it doesn't appear to be Base64, either; at the very least, not straight Base64. (It's possible there might be something we can do to this to get a Base64 string that can be further processed, but...)
ETA: To be clear, if this is Base64, it's not any standard Base64 encoding, as all the standard ones I've tried - barring UTF-16 - net me little more than gibberish loaded with unprintable characters, and UTF-16 gets you nothing but nonsense in Chinese.
(And near as I can tell, Base128 isn't a thing, because that would impinge on the ASCII 'control codes', like BEL [the 'bell' character, which triggers an alert on the receiving terminal], SOT [Start Of Transmission], and EOT [End Of Transmission]...)
Now I'm stuck on "Y3c..." ... still wondering if I'm down a rabbit hole
I got there like 2 hrs ago, not sure if this is the right path but can't think of anything else with
font size="n2esab"that leads somewhere else.Anyway my guess is that
pixel depth="^3"means "3-step-solution" with getting jjTWF is maybe 2 step out of these 3?Oo good luck
ok, got groups of 3 alphanumeric chars, a keyword a bit of known plain-text. applying cryptoanalysis yields 3 possible passcodes. of course none of them works :-/
Same here ... not sure how to go on.
finally got it... I have to admit, this is the meanest, most evil challenge so far. I can not say why because that would spoiler the work of the past 3 hours.. perhaps tomorrow... it is just not right.
I should have seen your comments earlier:)
at least they are getting something from me yet nothing
You and me both. I mean, I saw someone comment that he got base32 to yield something, but the original character string can't be base32 because it contains characters outside the base32 encoding scheme... and if it's base64, it ain't no base64 I've ever used before (and it's very precisely encoded, so that it didn't need the == padding you commonly see in other puzzles that use base64).
Same here. I've gone from base64>binary8bit>binary6bit>ascii>nowhere.
This is my first decoding with these challenges, so it's a bit more difficult. Some of the hints are starting to click in - no 0, 1, 8 or 9 in Base32, yet there is a 1 and lots of 8's and 9's, still reading into it on how to decode that...
I've just learned that Base256 is an actual thing. But I'm not sure if I'm scared, excited, or if it's of zero relevance to this challenge...
ya estoy viendo la luz de apoco jajajajajja
Not sure how to solve the whole thing yet, but got to "jJTWF..." part and this decoder has been VERY useful for experimenting that got me there:
gchq.github.io/CyberChef
It has hex, base32, 64, etc., reverse and so on...
EDIT: Got from "jJTWF..." to "Y3c" and I clearly see there is a pattern in what I did that keeps repeating (pattern given by "n2esab" and "4" but not sure if "^3" means I should repeat it 3 times what I did), but now I guess something else is needed to make sense of "Y3c"
You're still on the right path, a couple more steps needed.
From what I've read, it's probably as relevant as the joke programming languages Befunge or LOLCODE.
(Of course, that means we'll probably have to use one of those in an upcoming challenge, just you watch...)
...What did I say? 🤔🤔🤔
Are these couple more steps related to what was needed to get to "Y3c", or is it something completely wild?
Same question here ... I cannot see how to keep progressing as the next 2x level does not appear to exist and no other related method appears to go anywhere
Looks like I've just gone down a rabbit hole for the last 50min. Sigh.
Divide et Impera