Even a disk drive with a startup file doesn't work for accessing your files if you use a modified version of the fs API that encrypts all files every time they're saved and requires the password on every launch. I will try making this but it will be more of a proof-of-concept than something really advanced.
Also you don't have to implement crypto algorithms yourself, just google for an implementation which already exists(for example google "Lua rsa" and you will find some implementations of rsa in Lua) and eventually you need to modify it a little bit to work with CCLua, but it's still a lot easier than implementing it yourself.
Inbuilt Encryption
Started by makerimages, Jan 27 2014 11:00 AM
46 replies to this topic
#41
Posted 29 January 2014 - 01:44 PM
#42
Posted 29 January 2014 - 02:06 PM
Problem with that, is a lot of those "boxed" implementations are based on C and thus, useless in CC.
#43
Posted 29 January 2014 - 10:24 PM
Static seed + transmission time skew of seed == generation of next seed which is not static.
Encryption is entirely possible, and unique seeds that others cannot possibly know is also possible, provided they are not there to eavesdrop the initial static handshake. I've written at least two encryption apis on these forums. But at the end of the day, there is no point in encryption or hashing in CC, that is without block protection. Because whatever you're protecting, can just be smashed down.
But it's always a fun game of skills to create a computer with security and battle your friends to hack it and re-secure it again.
Encryption is entirely possible, and unique seeds that others cannot possibly know is also possible, provided they are not there to eavesdrop the initial static handshake. I've written at least two encryption apis on these forums. But at the end of the day, there is no point in encryption or hashing in CC, that is without block protection. Because whatever you're protecting, can just be smashed down.
But it's always a fun game of skills to create a computer with security and battle your friends to hack it and re-secure it again.
#44
Posted 15 February 2014 - 04:38 PM
I support this suggestion, because CC is missing a lot of the essential components of an encryption algorithm without having to write horrifyingly slow implementations. A java-side implementation of at least one encryption algorithm would reduce the strain encryption can have on a server.
#45
Posted 15 February 2014 - 07:12 PM
Putting aside that inbuilt security of any sort would totally take the fun out of it, wouldn't it be easier to just throw in secure point-to-point communications - eg make it so that when you rednet.send() something to a given ID, only the computer with that ID gets it, while other computers listening on that channel either get nothing or an unrelated randomised string - rather then go to the trouble of actually encrypting and decrypting data using code the user's never going to see anyway?
#46
Posted 15 February 2014 - 08:42 PM
It is unlikely that rednet will be reverted to that behavior. Prior to the change to frequencies/channels, that is how rednet worked.
#47
Posted 17 February 2014 - 03:03 AM
Lyqyd, on 15 February 2014 - 08:42 PM, said:
It is unlikely that rednet will be reverted to that behavior. Prior to the change to frequencies/channels, that is how rednet worked.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











