Welcome Functions, one and all, to the wonderful world of the CyCon

[Drogue]

Ok, I'm almost always on MSN. I like the post on the forum

I have another idea for encryption. If you put binary into a english-binary translator, you get more longer binary out. Like

00110000001100010011000000110000001100000011000100 11000000110000001100000011000100110001001100010011 00000011000000110001001100000011000000110001001100 01001100000011000100110001001100010011000100110000 00110001001100010011000000110000001100010011000100 11000100110000001100010011000100110001001100000011 00010011000000110001001100000011000100110001001100 0000110000001100010011000000110001

for instance. That is Drogue, double translated. It works too

[Maniac]

I hadn't thought of that yet! Cool! Though a downside is it dramatically increased the number of digits required. Even single-encrypted, the binary message is already longer than the English message.

Edit: Oh btw, there's a spelling mistake in your signature. Consciousness written as Consciouness.

[Drogue]

Very true, and thanks, I missed that

[Method]

i like the first way better since it's easier, but just imagine what those universitians would think if they put that binary into the translator and got more binary out.

"WTF? so they can actually read binary afterall? "

[Drogue]

If you put the first, Maniac's way, you get characters out. If you double encrypt, the latter way, then you get binary out. I say use Maniac's for most, but on occasions, double may work better, if we need extra encryption, but for a small sentance.

[Maniac]

TKG, in the general forum, the third digit was a zero, but I had to remove five digits to get a sensical message. So if we follow the method I proposed, it should have been a 1.

[Drogue]

I sent that to him in code, in the forum, with only 4, and with a 0. See if it confuses him

[Method]

yeah, i didn't read carefully enough. i think i get it now

[Bookwyrm]

Therefore I'd suggest that we add a few ones and zeroes at the beginning of each encrypted message, let's say four or five random 0's and 1's. If the third digit is 0, you have to remove the first four digits before transforming the message to English. If the third digit is 1, you have to remove the first five digits before transforming to English. The first, second, fourth and possibly fifth digits should be random, to avoid the other from too easily noticing a system in our encryption.

11010101001101101111011101010110111001100100011100 11001000000110011101101111011011110110010000101110

[Drogue]

I see Function Book has got it too

Welcome to Corellion, who is also now authorised. Only waiting for DBTS, before all original members are authorised

[Maniac]

I don't know where to post this, so I'll just ask it in our first thread here:
Drogue, what is our faction password?

[Drogue]

it's byte. Sorry I forgot to tell you sooner.

[Corellion]

01010100011101110010011001010110010101110100011010 01011011100110011101110011001000000110011001100101 01101100011011000110111101110111011100110010111000 10000000100000010010010111010000100000011011000110 11110110111101101011011100110010000001101100011010 01011010110110010100100000011101000110100001101001 01110011001000000111000001110010011011110110011101 11001001100001011011010110110101100101001000000111 01000111001001110101011011010111000001110011001000 00011011010110100101101110011001010010111000100000 00100000010011110110100000100000011101110110010101 10110001101100001011000010000001110100011010000110 10010111001100100000011010010111001100100000011011 01011101010110001101101000001000000110001001100101 01110100011101000110010101110010001000000110000101 10111001111001011101110110000101111001011100110010 0001

[Corellion]

For the encryption, the methods so far are good, but they seem a little easy to crack. TKG's mistake illustrates how easily, if someone gets the idea in their head, one can decipher the encryption. All they need to do is delete a digit and try, delete another and try, and continue until the message makes sense. Putting binary in and getting it out is good, but it's a simple matter to translate it again if somebody can translate it initially. Plus, the length is incredible... you multiply the number of characters by 64 to get that! I would suggest something more along the lines of the following...

Choose a number and convert it to binary through straight number conversions, not the binary converter. Make it a number less than or equal to 7, and keep adding extra zeros to the beginning until it's three digits long. This means the first three digits of each message will be the binary equivilent of a decimal number between 1 and 7, and the binary converters won't work on it. Then add x random digits after the number, where x is the number you chose. Finally, add a random digit after the xth digit of the actual translation.

In order to decrypt, just figure out what number the first three digits represent. Then, figure out the number, delete it, and delete the first x digits of the message after that, where x was the number you just decoded. After that, delete the digit after the xth digit in the message. This should thwart the people who delete numbers progressively.

Here's an example... Let's choose the message akizeta. Choose a number between 1 and 7, like 5. In binary, this comes out as 101. akizeta in binary is 01100001011010110110100101111010011001010111010001 100001
So, add 101 plus five random digits after and it becomes
10110100011000010110101101101001011110100110010101 11010001100001.
Then, add another random digit after the fifth digit of akizeta normally, and you get

10110100011001001011010110110100101111010011001010 111010001100001

This comes out as complete garbage in any translator, and randomly deleting digits won't work. They won't get any sense out of it, and because the inserted random digit is less than 8, they won't get even a single proper character.

The only drawback is that it might be too complicated.

Am I paranoid?

[Drogue]

Of course you are incapable of paranoia but that is too complicated IMHO.

How about we modulate it by the day, but add to the front and the back. So for Monday, we add 1 digit at the front and back, turesday we add 2, and so on. That way it changes each day, and you cannot just delete ones at the front or the back. So if someone cracks it, they have it cracked for a day, and then get confused again the next day Besides, I'm not sure people will really care that much to try for that long. But we could alter the code completely once per month, in case someone does get the pattern, although it would take them a while.