Decode this!

Are you bitwise? If you think so, decode this string!

^lee)mfgl()Pf|)~lg})}f)ef}z)fo)loof{})of{)}a`z)|zlelz)dlzzhnl(

Beleive it or not, it does actually have a logical message behind it, although it is completely boring and useless.

Hint ^9

First one to post the decoded message wins... Nothing!!!

Gf%)@)~{f}l)h)}a{ll)e`gl)zbl}ja

Ts{#pmot(fdn, .ao!aoqu)(@*~hj/tikp$qcdgczyh.{o!ffgjbb(}bn,~mrhld$jh'|ao+NOM/Mhaqk%afel*Ndzj

Decoded:

Well done! You went to lots of effort for this useles message

Used this to solve:

//Compile using gcc in my case gcc decode.c
#include "stdio.h"
#include "stdlib.h"
#include "stdint.h"

int main(void){
        char string[] = "^lee)mfgl()Pf|)~lg})}f)ef}z)fo)loof{})of{)}a`z)|zlelz)dlzzhnl(";
        //uint8_t len=strlen(*string);
        uint8_t i=0;
        for(i=0;i<61;i++){
                char a=string[i];
                char b=a^9;
                printf("%c",b);
        }
        printf("\n");
        return 1;
}

useles

Beleive

Sometimes I wonder if the boys and girls at Bletchley Park would have been so successful, had the Germans been less precise and fastidious.

Anyone remember rot13? I had a co-worker who wrote a program that would automatically decode rot-x encoded text by checking the letter frequency of the attempted decode to see if it matched standardized samples of "english."

Well done! Now for a harder one...

Xnt!loofde-!nobd!fho !Viu!vr!uiu!cntu!snu,02>!H&l!houshftde///

hint: origional program: _2-!2!,,
hint for finding hint: ^1

origional

Is that part of the hint?

Xnt!loofde-!nobd!fho !Viu!vr!uiu!cntu!snu,02>!H&l!houshftde///

Bit of a hint there. Tut-tut.

I forgot to give a hint to my clue in reply#1

_nlgl{l)jyal{)9)}f)8<

the /// were just what the output of the program came up with.

hint: origional program: _2-!2!,,
hint for finding hint: ^1

means use the origional program with a key of one to find out the
hint for the new code...

Answer: You mannaged, once again! What was that about rot-13? I'm intrigued...

Mannaged???

Back in the days of Usenet "maroons" were kept from directly reading potentially
offensive humor by "encrypting" the joke with rot13. Rot13 is a simple Caesar
substitution cipher -- only letters were shifted by 13. Decryption and encryption
used the same program. See rot-13 on Wikipedia.

"maroons", as I call them, were people easily offended by some pieces of humor
and would try to sue a company or educational institution for distributing said
humor. Encrypting, no matter how trivial, kept such people from reading the
message without them making the effort to decrypt it after a fair warning that
the content might be offensive.

-Rusty-

the ///

is what makes this code so simple to crack.

Though I have to admit, the eccentric spelling makes things a little more challenging.

Cracked mine yet?

Hint: Manchester Bluffs

Still trying to get yours, but I will have it soon (hopefully!).

Or maybe not...
Your code has done a good job of confusing me, even with the arduino doing the work!
After researching, it would appear that manchester bluffs means it is a Vigenère cipher.
I don't know how I can decode it though... Judging by the code I would guess that the ^
operator comes into play somewhere. Decoding the origional code with a Vigenere cypher
key of manchester bluffs gives Qocw tjl wwbst ejpz dlnggpmep qdgk. A frequency analysis
of that gives the following results:
G 3
P 3
W 3
D 2
E 2
J 2
L 2
Q 2
T 2
B 1
C 1
K 1
M 1
N 1
O 1
S 1
Z 1
This gives a total of 29 letters. With that we can work out what percentage of
the code each letter accounts for, then by maching that to the standard ammount
for the english language we can get an estimation of what each letter could be.
(Note that I used a program on the internet for the frequency analysis, and decoder).

Correct, it is a type of Vigenere - that was the Manchester Bluffs reference part of the clue.
The other part of the key clue is 'hex digit' - see the clue in reply #7

So the decryption of the code will be something like the output from
Qocw tjl wwbst ejpz dlnggpmep qdgk ^ hex key.
The hex key is obviously a decryption of _nlgl{l)jyal{)9)}f)8< .
Give me a while and I'll have it...

_ is an ascii number 95. Does that have anything to do with it I wonder?

Or maybe not... Just tried that as the encryptkey. Does nothing. Or
maybe I just did it wrong?

Tried the hex hint in the decoder with manchester bluffs. It came up with
exactly the same as the origional code. Now this has got me thinking...

Using the output of the decoder in the key gives a strange message:
Manc hes terbl uffs mancheste rblu.

Nothing to do with _ .
The clue in reply 7 is in your own code.
The message can be decoded by use of the '^' and '%' operators.
Seriously, it's a three line decode.
Two if you ignore the "Serial.begin".

I am so dumb! I tried the clue in my code with an encrypt key of 2.
Now I realised that with 9 it will give 'Vigenere cipher 0 to 15'.

So the key is Vigenere cipher 0 to 15. 0-15 is the hex range, and you
said the key was a hex number.

I forgot to give a hint to my clue in reply#1

_nlgl{l)jyal{)9)}f)8<

suggests that there was a clue hidden in the origional code.
Gf%)@)~{f}l)h)}a{ll)e`gl)zbl}ja possibly?

When put into my program with an encrypt key of 9 it gives
No, I wrote a three line sketch

So:
You wrote a 3 line program;
it has something to do with a vingerene code 0 - 15;
and it takes a hexadecimal code... :o

Confused...