Is this of any help?
LUCIFER2.ZIP
Author : Graven Cyphers
Date : 1992
Description: LUCIFER algorithm.[/size]
Taken from Schneier on Security, Applied Cryptography
Is this of any help?
LUCIFER2.ZIP
Author : Graven Cyphers
Date : 1992
Description: LUCIFER algorithm.[/size]
Taken from Schneier on Security, Applied Cryptography
Actually, that .zip contains the same Lucifer implementation I’ve been referring to as Outerbridge’s implementation (the only difference is that in this .zip file the source files have been converted from Unix file format to DOS/Windows file format). I referred to Outerbridge since his name was in the file name. But according to the comments in the C source file, the implementation “was crafted by Graven Cyphers at the University of Toronto, Canada, with programming assistance from Richard Outerbridge.”
Im sorry Dr.Gibbles but that its completely useless without any explanation to how we would use it. Its perfectly fine throwing ideas out there but without a link other than “It looks like this” to me, and alot of other people, looks like utter dribble.
Also im getting a little annoyed. When ever you comment or post something we seem to get “on a rail” and end up going down the tunnel only to have to turn back to where we started.
f it, I give up.
I kek’d.
OMG THAT MEANS THERE’S SOMETHING IN CHAPTER “ON A RAIL” THAT WE MISSED!
J.K.
–
Right now, we have only one mission: solve the HALOS code. Right now, Storm has given us clues in a list that I’m not going to write down here, but among them is the hint to “pay attention to the story”. If you feel that the connections you see tie into the story of the Pizza mystery, then go right ahead and post it. Otherwise, keep it to yourself, as we’re prone to red herrings and false flags everywhere we go here.
–
Also, I SEVERELY MESSED UP earlier when I said that the key is 16 characters. What I meant was 16 C H A R A C T E R S that aren’t hexadecimals. 128 bits = 8 bits per byte x 16 bytes, but 1 byte max value = 255 = 2[sup]8 [/sup]- 1 = 2 hex digits, so 16 bytes = 16 x 2 hex characters per byte = 32 hex characters. Whoops. I will adjust accordingly.
FOR GOD’S SAKE, DON’T SOLVE THIS THING!
IF YOU DO, YOU ALL WILL RELEASE A ROUGE AND FULLY SENTIENT AI!
IF THIS HAPPENS THERE WILLE BE A SINGULARITY AND THE FALL OF THE HUMAN RACE!
IT’S COMING FOR ME.
OH MY GOD, WHE’RE DOOMED!
[END OF LINE.]
HALOS AI WILL START A WAR WITH THE ENTIRE HUMAN RACE JUST LIKE SKYNET DID!
IT WILL START WAR WITH HUMANS!
IT WILL FIND US!
[END OF LINE.]
Nice TRON reference.
… Er, yeah.
In other news, BY THE SKIES, I’VE DONE IT. LuciferJS is working!! Now all we need is a key, one that is 16 bytes/characters long.
I tried “BenallohPaillier” converted to hex (42656e616c6c6f685061696c6c696572)(WARNING: ASCII to HEX conversion IS CASE SENSITIVE![/size][/size]), and fired it at the first 16 bytes of HALOS, but the resultant hex value is b88098b6a4c01af98d4e4893d3d71c4a, which translates to unintelligible GARBAGE in ASCII.
I repeat, “BenallohPaillier”[/size] IS NOT THE KEY.[/size]
As soon as I give LuciferJS a good debugging and some sort of layout overhaul, I’ll post the code here and y’all can start playing with it.
I AM NOT JOKING, THIS IS REAL!
FINE THEN, IF YOU GUYS REFUSE TO STOP, THEN I WILL TAKE MATTERS INTO MY OWN HANDS!
I CREATED HALOS, AND THE GOVERMENT WANTED TO WEPONIZE IT DUE TO ITS NATURE!
I MUST GO TO ORNL WHERE IT IS LOCATED TO DESTROY IT!
[END OF LINE.]
Oak Ridge? What makes you think it’s there?
Some of the things that Oak Ridge National Laboratory work with include nuclear related things as well as some super computing.
[CONECTION IS TERMANATED.]
Here it is. In all it’s un-styled glory.
LuciferJS
All you need to do is drag the HTML file into your browser tab list, and it should run. Works offline, too. (Or at least, it should, since I pulled the latest version of jQuery into the folder.)
Good luck. Share any results with the community, y’hear?
LuciferJS.zip (32.4 KB)
isn’t it benalohpaillier?
Is it 1 L or 2 in “benal(l)oh”? Thing is, The IRC clues have all said 1 L (“benaloh”), but Storm’s edit of the first post of this thread has 2 L’s (“benalloh”).
Thing is, 2 L’s make the phrase 16 bytes long. 1 L is missing 1 byte.
You could do benaloh paillier or benaloh_paillier. It’s been suggested before.
Also, make sure you’re doing decryption and not encryption with the Lucifer cipher, because it seems to me that they might give different results.
Hey, I come back after about a year of unactivity and we finally got a little bit of progress - and plenty of gamejackers.
Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.