It looks like you're new here. If you want to get involved, click one of these buttons!
I'm not looking to compare an entered password to a saved one, just saving the one a server requires a client to enter, the secure login is already set up (it's an ssh server with password authentication). I just don't want users to have to enter the password every time they want to start the server.
I did a bit of research and used AES encryption.
I did a bit of research and used AES encryption.Interesting choice, but how are you generating the AES keys such that you're using the correct one when you need to retrieve the password?
I did a bit of research and used AES encryption.Not sure if you're in this boat, but just a heads up - generally you don't want to roll your own security. There's mathematicians whose whole job is to get this stuff right. And even then they don't always get it right.
That's what the AES block cipher is there for - as long as you're using a sufficiently unpredictable key and a well-tested algorithm for the calculations, it's not that feasible to break.
It's not particularly secure in that anybody who can read both files and the script can do it themselves
I didn't roll my own security, I used the standard of AES security.
You see, installing that just worked. Over the many attempts over many years, that's the first time I've ever seen a page that said "Paste that at a Terminal prompt" and, when I did, it actually worked. First time ever.So yes, I guess I now do have homebrew installed. However, I've no idea if I was meant to install it as a user (lukeburrage) or not. I have a feeling not knowing this will bite me in the ass later.