Search the Community
Showing results for tags 'private keys'.
Found 1 result
Minimum search term is 4 characters long. Can't find what you want? Click here for the custom google search instead.
-
Just looking for some devs or advanced users to chime in on some best practices for general private key security while using RippleAPI on a local server. Was going through xrpl.org docs and it's in there that commandline is less secure than, say, JSON-RPC because of things like shell histories and maybe process logging, etc., which I agree with generally. Trying to avoid things like cutting and pasting private keys into commandline scripts to mitigate things like keyboard/clipboard/history loggers, even if just a little. I've been using Linux bash and piping things into jq to process JSON in order to sign and submit transactions; are devs hardcoding private keys into JavaScripts and then just encrypting those files? Pretty sure hard-coding private keys in anything like a script is a no-no, but I could be missing something. In terms of eventually automating my transactions, I could think of a couple ways, like referencing decrypted private key files, running your scripts then deleting/re-encrypting your private keys. I'm picking up javascript at the moment and guess I'll end up switching over to node.js to do transactions instead of through bash and bash scripts; seems like the Ripple API was designed with that in mind. I'm just using Linux command-line now cause I'm already familiar with bash and jq. Generally speaking, how are y'all managing private keys while using commandline/JSON-RPC/Websocket?
