Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Its possible to execute a MySQL file from the command line like so, mysql -u USER -pPASSWORD < FILENAME which triggers a warning, mysql: [Warning] Using a password on the command line int...
#2: Post edited
by
ghost-in-the-zsh
·
2020-12-20T19:37:40Z (almost 4 years ago)
Fix typo in title. Insecure = no confidence; Unsecure = no security
Is it insecure to use a password on the command line to run a MySQL script on Windows?
- Is it unsecure to use a password on the command line to run a MySQL script on Windows?
Its possible to execute a MySQL file from the command line like so, ``` mysql -u USER -pPASSWORD < FILENAME ``` which triggers a warning, ``` mysql: [Warning] Using a password on the command line interface can be insecure. ``` Given that its possible to go back through command line history on a Linux machine, I can see how that could be a security problem. However the Windows command line doesn't give one that ability, so would it still be a potential problem there?
#1: Initial revision
by
Charlie Brumbaugh
·
2020-08-26T14:58:57Z (about 4 years ago)
Is it insecure to use a password on the command line to run a MySQL script on Windows?
Its possible to execute a MySQL file from the command line like so, ``` mysql -u USER -pPASSWORD < FILENAME ``` which triggers a warning, ``` mysql: [Warning] Using a password on the command line interface can be insecure. ``` Given that its possible to go back through command line history on a Linux machine, I can see how that could be a security problem. However the Windows command line doesn't give one that ability, so would it still be a potential problem there?