It has the right passcode format, go through the usual set of tools (atbash, rot, morse…) to try to find the answer.
[hint]If your a gamer you’ll see were you need to Link[/hint]
That one was not obvious. ROT and Morse didn’t give any hint of a keyword sub. The only thing that makes it look a bit better is Atbash.
8yjz3nonagf8y6k
Nonag doesn’t really mean anything but reversed it gives Ganon. Any of you played The legend of Zelda right to the end ? Ganon is the final boss you needed to defeat with Link.
8yjz3linkf8y6k
Code #2
Observations
Again, go through your normal routine of atbash, rot, morse… to see what you can get.
Well no easy way to explain that one, it comes with experience and gut feeling. It’s all letters so most probable that the numbers are to be in the written form. First thing is try to see if you have repeated letter sequence.
ohodwxfsxnysxndsiqfdc
Next step would be to see how you can convert SXN to a number and also OHO since they are the first letters of the code that needs to start with a number.
Atbash doesn’t give anything. Let’s try ROT. ROT +1 on SXN is interesting. It give TYO, really close to TWO. To get the X to convert to W it would need to be ROT -1. What if we alternate ROT -1 & ROT +1
The sum of characters is 114. Divided by 6 is gives 19 which is a good length for a passcode. Let’s see how we can convert that to braille. One way I find that is quick and easy is to remove all the space and make a 3 by X rectangle. In this case it’s 3 by 38.
I then use a transposition cipher to make them horizontal ..-.-.--...--.-..-.--.-..--.-...--..--
--..--.--.-...-.-.----..--.-.-.-.--...
----....---.--..-.-.-...-...---.-.-.-.
And then simply add spaces to make groups of two on each lines .. -. -. -- .. .- -. -. .- .- -. -. .- -. -. .. -- .. --
-- .. -- .- -. -. .. -. -. -- -- .. -- .- .- .- .- -. ..
-- -- .. .. -- -. -- .. -. -. -. .. -. .. -- -. -. -. -.
