222 posts
Location
Canada
Posted 03 October 2012 - 01:48 AM
Error is now fixed.
Basically, This is my second script on here from me. Its very basic.
What it does is passwords on the startup, but with a more secure base.
So here's the code:
os.pullEvent = os.pullEventRaw
user = default -- Your username.
pass = default -- Your password.
print "MasterLock V1.3"
print "Made by Rhyleymaster"
print " "
sleep(3)
while true do
term.clear()
term.setCursorPos(1,1)
write("Username:")
u = read()
if u == user
then
write("Password:")
p = read("*")
if p == pass
then
print("Logging in...")
sleep(3)
shell.run("unlock") -- Must exist for it to be unlocked.
else
print("Wrong Password.")
sleep(3)
end
else
write("Password:")
f = read("*")
if f == ("")
then
print("Wrong Password.")
sleep(3)
else
print("Wrong Password.")
sleep(3)
end
end
end
And I'll upload it to pastebin for you guys:
pastebin get kGzPwpsa startup
Also, You can rename it from startup to anything, but its best to have it as startup.
Also note: This is only my third attempt at this. Please let me know if theres any bugs. I WILL FIX IT ASAP.
222 posts
Location
Canada
Posted 03 October 2012 - 01:51 AM
Yes, I know its code in the post is broken. I fixed the Pastebin link though.
2 posts
Location
England
Posted 03 October 2012 - 01:54 AM
You should of used functions with your work, it makes things allot more neater and organized.
:(/>/>
222 posts
Location
Canada
Posted 03 October 2012 - 01:55 AM
Sorry, Another error. FIXING RIGHT NOW.
222 posts
Location
Canada
Posted 03 October 2012 - 01:57 AM
Its fixed now
2 posts
Posted 03 October 2012 - 05:20 AM
Just as an FYI, all local startup file based security measures are moot if someone creates a startup file on a disk. Floppy startup files will always take precedence over local security policies unless the core OS is modified otherwise.
222 posts
Location
Canada
Posted 04 October 2012 - 12:15 AM
Just as an FYI, all local startup file based security measures are moot if someone creates a startup file on a disk. Floppy startup files will always take precedence over local security policies unless the core OS is modified otherwise.
I will add a disk.eject() to it.
3790 posts
Location
Lincoln, Nebraska
Posted 04 October 2012 - 12:19 AM
Does not stop the user from doing Ctrl + S, then inserting the startup disk, then rebooting the computer. There really is no such thing as a completely secure system, without editing the BIOS or using plugins.
222 posts
Location
Canada
Posted 04 October 2012 - 12:27 AM
Does not stop the user from doing Ctrl + S, then inserting the startup disk, then rebooting the computer. There really is no such thing as a completely secure system, without editing the BIOS or using plugins.
Alright, Thanks cranium. I'll work on buffing it out to the maximum security though. That should be good