Jump to content
IGNORED

Aphex Twin: Read part 1 of SYROBONKERS! - an interview with Aphex Twin


Recommended Posts

  On 11/7/2014 at 8:46 PM, mcbpete said:

No, still not got anywhere with it. The = sign at the end really hinted as BASEn encoding (they're usually used to pad the file to make it the right number of bits) but I can't get any to work at all.

 

homer-simpson.gif

Thanks user487363530. And user4873635301. Now 48736353001.

  • Replies 332
  • Created
  • Last Reply

Top Posters In This Topic

  On 11/7/2014 at 8:52 PM, olo said:

 

  On 11/7/2014 at 8:46 PM, mcbpete said:

No, still not got anywhere with it. The = sign at the end really hinted as BASEn encoding (they're usually used to pad the file to make it the right number of bits) but I can't get any to work at all.

 

homer-simpson.gif

 

 

Agreed with mcbpete. In fact, one of the first things I saw in reply to the code tweet was mcb complaining that it wasn't base64!

 

Small world wattmmms.

  On 11/7/2014 at 8:57 PM, Ascdi said:

 

  On 11/7/2014 at 8:52 PM, olo said:

 

  On 11/7/2014 at 8:46 PM, mcbpete said:

No, still not got anywhere with it. The = sign at the end really hinted as BASEn encoding (they're usually used to pad the file to make it the right number of bits) but I can't get any to work at all.

 

homer-simpson.gif

 

 

Agreed with mcbpete. In fact, one of the first things I saw in reply to the code tweet was mcb complaining that it wasn't base64!

 

Small world wattmmms.

 

 

*Confused Homer*. I know fuck all about codes, coding, ciphers, etc.

 

It's all way over my head. Hoping you or MCB can knock it out.

Thanks user487363530. And user4873635301. Now 48736353001.

  On 11/7/2014 at 8:46 PM, mcbpete said:

No, still not got anywhere with it. The = sign at the end really hinted as BASEn encoding (they're usually used to pad the file to make it the right number of bits) but I can't get any to work at all.

Well, it certainly looks like base64, in that it uses the only special characters (+, /) that are part of the acceptable set for base64, along with the padding character at the end.

 

I was working on the idea that the string doesn't decode to text, but might be a file of some sort (e.g small image) so decoded as base64 to a binary file and ran it through a little program called TrID, which can detect over 5,400 file formats, but that drew a blank too - it doesn't recognise it

Guest austin2

Don't rule out base64 just because it doesn't decode to a string. The hexadecimal of the output is b4eb60a7f97607213921abfc107cfecb15784eb1799d881fe352354456109a7d0703c792a4837421333921152f7804213131213f44184266

 

Maybe we need to take it a step further. 56 bytes long. It's not the length of any standard hash digest or anything.

  On 11/7/2014 at 2:00 PM, mcbpete said:

The guys just posted this on twitter: tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=

 

I'm shite at spotting decryption types - Doesn't look like the traditional ROT/Caesar cipher. Base32 & Base64 doesn't seem to come up with anything either. The tweet ( https://twitter.com/noyzelab/status/530703478528544768) has a safe lock pointing to 32, guessing that's a clue (and why I originally thought ROT again)

possibly related to the TOR stuff for SYRO?

WATMM-Records-Signature-Banner-500x80.jpg

 

Follow WATMM on Twitter: @WATMMOfficial

  On 11/8/2014 at 4:20 PM, Consul said:

That's the first tweet, already been discovered (see a couple posts above). Still nothing on the second though? Don't think it will be revealing something huge, but who knows...

jharvard@appliance (~): ~cs50/pset2/devigenere SYROBONKUS

Ciphertext: tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=

Plaintext: bQ

Guest Atom Dowry Firth
  On 11/8/2014 at 5:29 PM, fenton said:

 

jharvard@appliance (~): ~cs50/pset2/devigenere SYROBONKUS
Ciphertext: tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=
Plaintext: bQ

 

 

How did you get to this point? This is 5deep6me so I'm looking at this thing like a caveman at a monolith. jharvard@appliance led me to a page about how to use CS50 Appliance which is p interesting. The 'devigenere' bit means it's a vigenere cipher? Am slow pls halp

  On 11/9/2014 at 5:37 PM, Timothy Forward said:

 

  On 11/8/2014 at 5:29 PM, fenton said:

 

jharvard@appliance (~): ~cs50/pset2/devigenere SYROBONKUS
Ciphertext: tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=
Plaintext: bQ

 

 

How did you get to this point? This is 5deep6me so I'm looking at this thing like a caveman at a monolith. jharvard@appliance led me to a page about how to use CS50 Appliance which is p interesting. The 'devigenere' bit means it's a vigenere cipher? Am slow pls halp

 

tumblr_ltjlk35lqf1r124nx.jpg

  On 11/9/2014 at 5:37 PM, Timothy Forward said:

 

  On 11/8/2014 at 5:29 PM, fenton said:

 

jharvard@appliance (~): ~cs50/pset2/devigenere SYROBONKUS
Ciphertext: tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=
Plaintext: bQ

 

 

How did you get to this point? This is 5deep6me so I'm looking at this thing like a caveman at a monolith. jharvard@appliance led me to a page about how to use CS50 Appliance which is p interesting. The 'devigenere' bit means it's a vigenere cipher? Am slow pls halp

 

 

dis is getting pretty spoopy

Guest Toastmann

tOtgp/l2ByE5Iav8EHz+yxV4TrF5nYgf41I1RFYQmn0HA8eSpIN0ITM5IRUveAQhMTEhP0QYQmY=

 

Looks like a AES-256 string for me, with 2 secret keys.

 

Could someone try to decrypt it with CIRCLONT6A as first key and syro u473t8+e as second key?

 

nvm il try myself

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   1 Member

×
×