> -----Original Message----- > From: larry a price [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 13, 2001 11:37 AM > To: '[EMAIL PROTECTED]' > Subject: [EUG-LUG:560] RE: variations on a theme > > > On Thu, 13 Dec 2001, Justin Bengtson wrote: > > > but i have to ask : why have it run hourly or daily? you > aren't exactly > > asking it any questions... > > No, I just meant that it would update a stored copy, and then > use that to > respond to xmlrpc requests for the next hour or so, although there are > other reasons...
uhm... okay. > for instance alice and bob want to share secrets, so they > agree that they > will use the output of karen's key server for a specific hour > or minute > as the input for a key-stream generating algorithm, given > that eve has to > catch the output of not only karen's key server but also that > of all her > kousins (karl,kari,kevin....) it does become practically difficult for > eve to find the keys, not impossible, merely improbable. wtf? from what i can tell, you're going to use the hexagrams as a private key generator? the "i ching" security method? so, we have eight trigrams, combinations of which can make 64 hexagrams, what's next? do you combine two, four, eight or more hexagrams to make a key? since each trigram can be represented as a bit sequence, you can use them to create a key example : 010 110 and 110 111 and 101 000 and 011 001 ####### ### ### ### ### ####### ### ### ### ### ####### ### ### ####### ####### ### ### ####### ### ### ### ### ####### ####### ### ### ### ### ####### ####### ####### ### ### ####### ### ### 24 bits comes out to three bytes. if we add one more hexagram, we come out two bits shy of four bytes (i'm not a security expert, so i don't know how secure that would be...) once you get this implemented, you then have to worry about inauspicious keys (making bad combinations of hexagrams... the C.J. Cheryh novel "Foreigner" has an example of a society based on whether numbers are auspicious or not.) maybe it'd just be better to translate a current security key into hexagrams and read them as given... even better, make an i ching program that uses incoming tcp/ip packet headers to generate a sequence of hexagrams for a reading... actually, that might come up with the same reading alot. use the first two bytes of packet data (dropping the last four bits, of course...) to generate a proper i ching reading. nevermind...
