@Rroff
spoiler 1 : why not `cat xml | nc host port` instead ?
spoiler 2 : slap across your wrists for storing passwords in a file and having them visible under running process lists
.... yes knowing this stuff doesn't give employability. Years of experience with some of the quirks in the trade helps a lot.
Funny thing is that once you've got in you'll find that all you'll be doing is noddy stuff like this.
Didn't know netcat existed at the time - I can script stuff like that in my sleep but there is always someone with better actual Linux knowledge hence my point heh.
Was actually wrapped in another system (virtualisation plus no end user had access outside of a locked down webmin based control panel) so if they could actually see the password either plaintext in file or passed on the command line in processes that was the least of security worries - but you are right that is a very bad technique to use and best avoided as a practise - it would be very easy for it to slip the mind and deploy something in that manner on a critical system.
EDIT: That is a good consideration to have in mind though as a good security practise - that passwords should never be passed along but read and checked by the final module - didn't occur to me at the time as I saw it all as one system protected by the whole rather than as separate components.
(That was bog standard game server stuff where the remote console password is stored in a plaintext config file anyhow - can't actually remember that far back but it may have been the game server itself wrote that password file)
Last edited:
