Feature #15348
openBlock out PSK when viewing Phase 1 IPsec configuration
0%
Description
When filling out a PSK in the phase 1 proposal section, the PSK really should be entered in obfuscated with the option in the WebUI to show the password.
Entering a password in clear text so anyone shoulder surfing can see it is a security issue.
Updated by Jim Pingle 9 months ago
If we do anything like this, it will need to have a visibility toggle and/or a button to copy the value to the clipboard. Being able to see the PSK is critical to troubleshooting the tunnel, and copy/paste is the best way to get a secure PSK from one system to another. It would also render the button to generate a PSK useless without a way to see/copy it.
If your PSK is weak enough someone could casually shoulder surf it, you should be using longer PSKs anyhow. Or ditch PSKs and use certificates which are much more secure.
Updated by Mike Moore 9 months ago
"If we do anything like this, it will need to have a visibility toggle and/or a button to copy the value to the clipboard"
This is my thought process and i did request that in the opening of this redmine.
Typically JunOS or PanOS obfuscate the PSK and there is usually some method to unhide it when required (at least on JunOS).
This isn't a question of whether a PSK is weak and what an alt solution should be. The PSKs should be hidden from view when not needed
Updated by Mike Moore 9 months ago
"It would also render the button to generate a PSK useless without a way to see/copy it."
Is render and copy to clipboard at the same time not an option?