Advanced Password Utility

• If an invalid command is entered, it will display "Unknown command. Type 'help' for a list of commands" in red for 2 seconds before rebooting back to the utility
• Working installer
• Commands (shutdown, edit, about, help and unlock)
• Unable to be terminated
• Compatibility with black and white terminals

• Normal or advanced computer
• Running the program on a pocket computer will graphically glitch most things

• Type this command into the terminal:

  pastebin run JSkhhZpg

• Read the on-screen instructions and then press Enter/Return to begin setup or F1 to quit
• Enter your password into the black box and press Enter
• Restart the computer (reboot command)

• Make the utility act more like the shell where when a command is entered, instead of clearing the screen, it simply scrolls down like the original shell
• Pocket computer compatibility

local temp = os.pullEvent
os.pullEvent = os.pullEventRaw

os.pullEvent = temp

Yarillo, on 23 August 2015 - 09:00 AM said:

It's very nice looking. I think this is the best looking implementation of a password system I've ever seen yet. I find it sad that you didn't implement encryption and prevented terminating the program though. It renders it useless !

You can use this api to hash passwords: http://regex.info/code/sha1.lua
(Don't forget to use a salt)

And simply doing this:

local temp = os.pullEvent
os.pullEvent = os.pullEventRaw

Will fuck up the OS enough that it won't be able to register ctrl+T calls.
And of course to revert it you can do

os.pullEvent = temp

once the access has been granted.

Yarillo, on 23 August 2015 - 11:03 PM said:

I don't get it. Isn't the OS is responsible for the termination of running programs with CTRL+T ?
Changing the pointer to the pullEvent function to something else looks like the only way to do it to me since it seems to use that

• Ctrl+T will no longer work
• SHA1 enryption with some salt (Mm.. finger lickin' good)
• AES Encryption by SquidDev will be used for encryption
• Patch setup bugs
• Setup doesn't reboot or clear screen once done
• Setup installs the program before the user decides to install it
• "Note: Press Enter to continue" is false and comes up after the password is already entered

• You have asked me about it either through Reddit (reddit.com/u/Djinnibone) or through this thread
• You credit me either in your operating system thread or in the OS itself.
• You don't alter the code in any way, shape or form

• Fixed a bug allowing the program to be terminated, rendering it useless (thanks @Yarillo)
• Fixed some setup bugs including not clearing the screen or restarting once complete, "Press Enter to continue" message coming up too late and a few more
• Fixed an annoying feature where the computer would reboot after most commands were entered (excluding reboot)

H4X0RZ, on 23 August 2015 - 11:24 PM said:

Nope. pullEvent is a wrapper for pullEventRaw (wrapper for coroutine.yield) which just adds termination. If you don't use it in your script, it is not able to terminate it. Changing os.pullEvent just makes it more convenient because you don't have to change anything in your code to prevent termination.

while true do
  sleep()
end

If you don't use it in your script, it is not able to terminate it.

KingofGamesYami, on 27 August 2015 - 07:12 PM said:

If you don't use os.pullEvent or any function that calls os.pullEvent (sleep is one of them), the script can't be terminated. The os.pullEvent function is responsible for terminating the script. Other functions can call os.pullEvent, which will make the script terminatable, but os.pullEvent is the culprit.

From bios.lua

function os.pullEvent( sFilter )
    local eventData = { os.pullEventRaw( sFilter ) }
    if eventData[1] == "terminate" then
        error( "Terminated", 0 )
    end
    return table.unpack( eventData )
end

KingofGamesYami, on 27 August 2015 - 07:12 PM said:

If you don't use os.pullEvent or any function that calls os.pullEvent (sleep is one of them)

PokeAcer, on 31 August 2015 - 01:09 PM said:

Umm, AES encryption?
That's WILDLY insecure for passwords - you HASH a password, not encrypt it. Use SHA256 (I have the API in my program - http://pastebin.com/8fyFyw3B line 15-197) and a salt.

• Fixed a few bugs
• Messages no longer display one line under where they should be
• And more.
• Reduced all the times for displaying messages
• Implemented compatibility for black and white terminals
• (Half) implemented a confirm password system
• Only works on black and white terminals
• "For now"
• Changed how logging in works slightly
• May revert back in the future