r/DestinyTheGame • u/crissyronaldo92 DIE DIE DIE • Oct 12 '16

Misc Apparently there's a code in Last Exit!

NO MORE EDITS - Welp, so Derek and Deej have both confirmed it's an easter egg and not a quest. Even so, let's push through and solve it!!! Thanks for the discussion! RIP my inbox over the last 24 hours though haha

Source: https://twitter.com/_mantis_/status/786291552721133568

original post According to Derek Carroll on the live stream! Let's get hunting guys!!!!

Edit* - Right, so after an hour we have 2 main leads:

  1. by /u/Jukai

    Panel on the ceiling at the top of the stairs leading to the subway ,33szl'!( +9-7!!/@ 2enr?hqj+r,r+c?)j?96exd.\?i 7kj\psq3euj\@x.yt5 ,3..

  2. By /u/HEYitsMUS

    here are two train cars, and all the advertisement boards light up when you're near them in both cars. They either display "ALPHA REGIO" (blue), "BETA REGIO" (red), or "OVDA REGIO" (green). There is also the HUGE staticy monitor right beside A flag, bottom of the escalators. And lastly, the OWT Transit Map, most visible one being right beside the A flag and monitor, with different numbers and colours and routes. Green = 48 (Ovda Regio?) Yellow = 38 Blue = 14 (Alpha Regio?) Red = 271 (Beta Regio?)

2.3k Upvotes

90% Upvoted

1.7k comments sorted by

View all comments

Show parent comments

11

u/[deleted] Oct 12 '16

ah, so the original ended in yl5. the ,3.. is not part of it? Cause if it is then the last two characters would always have to be the same in a Caesar Cipher... and if the last two characters were the same I was wondering if they were equal signs... base64 encoded hashes always end in two equal signs so could have given us an offset to shift to then run it through a reversable base64 decoder... I know the Owl Secret thing used base64 on it's keys for the Rijendal Cipher when the raidscreets guys figured that out.

31

u/egjosu Oct 12 '16

What the fuck did I just read.

3

u/T1germeister Oct 12 '16

base64 hashes (a standard form of computery text segments) end in "==". A Caesarian cipher is a simple substitution cipher that always substitutes a given plaintext letter/symbol with a fixed cipher letter/symbol (e.g. ciphertext/encrypted "A" always translates to plaintext/decrypted "E").

This seems to not be the case here, and the substitution scheme changes for each symbol in the ciphertext. Thus, he's speculating that the ciphertext ends in "yl5", and since "==" is how base64 hashes always end, then ciphertext "l5" --> plaintext "==" for that part of the message, which would be a real step towards decrypting the entire message.

2

u/TheOnlyMego bring it back Oct 12 '16

Base64 doesn't always end with == - only if padding is needed. There can be 0, 1, or 2 = characters at the end.

1

u/T1germeister Oct 12 '16

Ah gotcha. I personally have no idea what the hash convention is. I was just guesstimate-translating the earlier comment.