#1
Posted 06 May 2014 - 07:23 PM
Side note : I use a printer to make the ticket(s).
#2
Posted 06 May 2014 - 08:39 PM
#3
Posted 06 May 2014 - 08:43 PM
CometWolf, on 06 May 2014 - 08:39 PM, said:
#4
Posted 06 May 2014 - 08:56 PM
#5
Posted 06 May 2014 - 09:43 PM
Agent Silence, on 06 May 2014 - 08:43 PM, said:
local creditInfo = "IDK 200?" --lol local file = fs.open("/disk/creditInfo","w") file.writeLine(creditInfo) file.close()
local file = fs.open("/disk/creditInfo","r") local creditInfo = file.readAll() file.close()You get the idea. Though for this stuff to be secure, you'd probably need to use a central server computer communicating via rednet to the drive computers, with encoded transmissions. And that's not even touching on the whole fake disc issue.
Edit: actually come to think of it... Each disk has it's own unique ID, which i don't believe can be spoofed. The disk API's getID will return this value, which could easily be used to know wether the disc is legit or not.
Edited by CometWolf, 06 May 2014 - 09:46 PM.
#6
Posted 06 May 2014 - 10:55 PM
#7
Posted 06 May 2014 - 10:58 PM
#8
Posted 06 May 2014 - 11:02 PM
Agent Silence, on 06 May 2014 - 08:43 PM, said:
CometWolf, on 06 May 2014 - 08:39 PM, said:
TheOddByte, on 06 May 2014 - 08:56 PM, said:
You can actually use disks as tickets since you can automatically delete the ticket info, however, it would cause an issue anyways because any could hack into the computer and use an unused ticket number. But if you keep it in a secured place and made a peripheral to a drive from that location then that would work. (also some monitors to see if the ticket is correct. )
But you cant have a computer read paper unless someone made an addon like a scanner or something.
Edited by cptdeath58, 06 May 2014 - 11:04 PM.
#9
Posted 06 May 2014 - 11:03 PM
And you can do a basic, secure encryption as long as you know no one will access that computer (with the scan and eject) since you are using a monitor.
#10
Posted 06 May 2014 - 11:07 PM
HometownPotato, on 06 May 2014 - 11:03 PM, said:
And you can do a basic, secure encryption as long as you know no one will access that computer (with the scan and eject) since you are using a monitor.
Ik you can make a peripheral using wired modems to connect the two.
Edit: Plus they can't access the programming without the actual computer. correct if i'm wrong there
Edited by cptdeath58, 06 May 2014 - 11:08 PM.
#11
Posted 06 May 2014 - 11:23 PM
Assuming a securely-placed server, properly done wireless encyption has always been viable - even if your methods are known, so long as your keys are never revealed to those who shouldn't have them that's fine.
In this case, I'd have a remote server that generates a random key for each user. That key is stored on the disk along with the ATM client software - you have no dedicated ATM machines, you instead rig things so that users can boot their own secure copies of your ATM software via their own personal disks (shutting down the computer, inserting the disk, then booting back up (in that order) should prevent malicious copying by third parties).
When they use the disk, any transmissions between the client computer and server computers would be encrypted with the key in concern. In this manner, the only weak points should be users sharing their disk contents with other users (in which case all that could be broken into would be their own accounts - tell 'em to hang on to those charms of keeping!), or the server itself (which you'd want to lock behind warded blocks or whatever).
Not to go off on too much of a tangent, but it occured to me the other day that there's a much easier way to authenticate some systems - a reverse GPS lookup. No good on its own for hiding transmission contents, but great if you want to be sure a transmission came from a system at a certain location.
#12
Posted 06 May 2014 - 11:25 PM
#13
Posted 06 May 2014 - 11:32 PM
HometownPotato, on 06 May 2014 - 11:25 PM, said:
Bomb Bloke, on 06 May 2014 - 11:23 PM, said:
Assuming a securely-placed server, properly done wireless encyption has always been viable - even if your methods are known, so long as your keys are never revealed to those who shouldn't have them that's fine.
In this case, I'd have a remote server that generates a random key for each user. That key is stored on the disk along with the ATM client software - you have no dedicated ATM machines, you instead rig things so that users can boot their own secure copies of your ATM software via their own personal disks (shutting down the computer, inserting the disk, then booting back up (in that order) should prevent malicious copying by third parties).
When they use the disk, any transmissions between the client computer and server computers would be encrypted with the key in concern. In this manner, the only weak points should be users sharing their disk contents with other users (in which case all that could be broken into would be their own accounts - tell 'em to hang on to those charms of keeping!), or the server itself (which you'd want to lock behind warded blocks or whatever).
Not to go off on too much of a tangent, but it occured to me the other day that there's a much easier way to authenticate some systems - a reverse GPS lookup. No good on its own for hiding transmission contents, but great if you want to be sure a transmission came from a system at a certain location.
Bomb Bloke: True, security does suck without any other mods ,but this is a ticket machine so I don't see any needs for a server unless you ran mutliple machines then that wouldn't be a problem because people on those ticket machines are the ones getting it, so they cant do so. though, it would work great as a program that needs to be payed in-game, such as an os or security feature.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users