Nordinho.net Community

My best bruteforced result so far:
I have not seen one who loves virtue as he loves beauty

[EDIT]
Turns out, Confucius said that...

Well, I didn't want to be the only one who uses bruteforcing to solve things
Now you're the new member of the bruteforcing club

...Any other applicant to the club? All new members will be welcome.

Your turn, Bolaf... What new exciting adventure is awaiting for us?

login
> user: david
> pass: ********
> logging in..... ok

mial -open
> unknown command

mail -open
> connecting..... ready

mail -inbox
> loading headers..... done
> ==== begin: inbox list ====
> id:1 utc:432225531 from:falken
> ==== end: inbox list ====

mail -id:1
> loading data..... done
> ==== begin: inbox msg id:1 ====
> date: utc432225531
> from: falken
> body (binary enc-type:eor view:hex):
> 02 06 53 2c 14 17 23 0b 5c 38 19 04
> 2b 1c 16 48 14 12 21 4f 0a 07 00 13
> 6a 02 1c 05 55 07 25 1d 53 1c 1d 04
> 6a 0e 03 18 19 04 6a 1f 1a 0d 55 13
> 2f 0c 1a 18 10 5a 6a 26 53 06 10 04
> 2e 4f 07 07 55 12 3f 1d 03 1a 1c 12
> 2f 4f 1e 11 55 0f 2f 18 53 0f 13 41
> 3d 06 07 00 55 00 6a 1c 16 04 13 4c
> 27 0e 17 0d 55 02 2b 04 16 46 5a 32
> 3e 0a 03 00 10 0f
> ==== end: inbox msg id:1 ====

mail -close
> closing connection..... done

exit
> logging out..... done

"mial -open
> unknown command"

That's about everything I've identified

Well, let's resume:
Someone at a terminal logs in to check his mail.
He sees there's a (new) message in the inbox.
The mail body is shown in hex format, because it contains non-printable chars (due to encryption).
Our aim, of course, is to decipher this message.

We can't solve this without knowing the background story. And some hints are available:
- their names
- the year (see the date in the mail header: utc 432225531 is a UNIX timestamp)

You may also have noticed the term enc-type:eor in the body info, which refers to the type of encryption - and suggests usage of a key(word).
I know, it's not easy at first, but hey, you asked for an exciting adventure...

According to the online converters, the message was sent on Mon, 12 Sept 1983, 14:38:51 GMT
(GMT and UTC seem to be the same)

... and now let's investigate the type of encryption

[edit] EOR redirects me to XOR (I remember it from a previous one, but I'm not sure whether they're actually the same type of encoding)... I'll be back.

Yes, EOR and XOR mean the same thing.

Oh, and while you're at it: extra bonus if you guess David's password

I understand - time for a hint. It's Jennifer, the name of his girlfriend...

[EDIT]
... and 1983 is the right year

So we should convert the hex characters to binary, I guess: "body (binary enc-type:eor view:hex)
And then use XOR cipher with a keyword, that can be -including but not limited to-
falken or david or falkendavid or davidfalken or fromfalkentodavid or 1983 or falkendavid1983 or 091983 or 12091983 or monday12091983 or monday12091983davidfalken or davidfalken12091983.... or add up falken+david+1983...
Is there an online tool to try all those possibilities?

[edit] at least I found a hex-binary conversor that could deal with the whole text, instead of having to enter the numbers one by one and then copy them in a document... and it was so gentle as to translate into text, too... here is the result:
S,#\8+H!O
�jU%Sjj
U/Zj&S.OU?/OU/SA=�U�jL'
U+FZ2>
�