You are giving all your bash history to a third party, that is incredibly scary and if you can't see the security implications then you need to rethink your product.
the problem is, theres a pretty good chance people will still send all sorts of passwords and access credentials. that's a big liability if you get exploited.
should you do this? no.. but people do, all the time.. take for example this MySQL bug report with many complaints that the command now issues a warning when you specify a password on the command line:
https://bugs.mysql.com/bug.php?id=66546
Seriously I don't think you really understand the implications here or you aren't taking them seriously, if you did you sure wouldn't be talking about this so nonchalantly. You should seriously shut this down before you get some young programmers/admins fired or worse.
Also from your FAQ what the hell is "strong level encryption", can you not name it? Can you go into the extreme technical details of what encryption you are using, how data is protected in memory and at rest?
rcaloras|10 years ago
lathiat|10 years ago
should you do this? no.. but people do, all the time.. take for example this MySQL bug report with many complaints that the command now issues a warning when you specify a password on the command line: https://bugs.mysql.com/bug.php?id=66546
nullrouted|10 years ago
Also from your FAQ what the hell is "strong level encryption", can you not name it? Can you go into the extreme technical details of what encryption you are using, how data is protected in memory and at rest?