SecuriLogin Client - For Linux

Ok, ok, so SecuriLogin Client for Windows wasn’t that secure, but it had the right idea.

How it worked is that it was “supposed” to authenticate user programs on the insertion of existence of a device that matched a USB serial number. This, in concept, could be a USB thumbdrive. I in fact, used code similar to that to implement a screen login utility that prevented family from using my computer. It was, however, easy to get around.

One of the added features, which I toted with me to school, was the application of a desktop wallpaper. When I ran the client program, the insertion of my USB key would trigger the wallpaper to change. Authentication, in fact, could be used as an encrypted module that the key is the USB key. That, however, is not compatible with multiple keys. It would be inefficient to store a separate module for each key. The module could not be stored on the key, as that has distribution problems. The module cannot be stored on the network, for offline use. Perhaps the solution is to encrypt a key on the device, or locally, that contains the key for the module. The module could be encrypted, say with key ‘asdf’. The local computer could have a descriptor file, one encrypted key per line. An authentication algorithm could in fact then read a line, and try to decrypt it. If the first 4 letters, are say OKAY, the rest of the data is the encryption key to the module.

It’s important to understand the concept of module. In my example, a module is some executable file or code. It could be a script, a program, an executable, or anything. It’s a neat concept, but I think it will just stay like that, a concept.

That being said, I think I’ll see if I can tinker around and see what I can come up with in Linux.