Closed (works as designed)
Project:
SMTP Authentication Support
Version:
6.x-1.0-beta5
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
17 Aug 2012 at 14:37 UTC
Updated:
26 Apr 2016 at 23:22 UTC
Jump to comment: Most recent
Comments
Comment #1
nikolaosinlight commentedI noticed this as well and agree.
Although nothing is full proof when it comes to encryption/decryption a simple/rudimentary cypher would be nice.
Comment #2
iamcarrico commentedI would recommend two things.
1) Don't use your personal Gmail account then.
2) Store the user/pass as a $conf variable in the settings.php file. Then you can delete those db entries. The settings.php will be the only way to view it, which should be secure from the outside world. And if you server gets hacked, well that sucks. The code is below.
Comment #3
josesanmartin commented1) Creating a separated GMail account for sending purposes only is also a good practise.
2) ChinggizKhan's advice about settings.php is wonderful, I fully endorse it.
A little obfuscation seems more comfortable but it doesn't provide real security. Moving to settings.php, however, is certainly safer. I'm marking this as a fixed support request.
Comment #5
skaughtthe admin control panel needs to reprocess the submission in smtp_admin_settings_form_submit() ...and all outputs of var needs decode routine to address this concern.
Comment #6
skaughtComment #7
wundo commentedClosing very old (dead) issues, if you think this is still relevant please re-open.