Bypassing Browser Security Warnings with Pseudo Password Fields

Re:Bypassing Browser Security Warnings with Pseudo Password ... by gruez on Thursday November 02, 2017 @07:54AM (#15609522)

What's easier for a dev: inserting a few lines of code, or getting access to the production server, setting up letsencrypt (or getting a budget approval for the $10/year certificate)?

[ Parent | on HN ]

Re:Bypassing Browser Security Warnings with Pseudo Password ... by robteix on Thursday November 02, 2017 @07:59AM (#15609554)

Code is rarely the same as "inserting a few lines of code" though. They presumably had to think about how to work around the problem, look for an appropriate font, etc. All for the purpose of hiding a symptom of an underlying problem.

[ Parent | on HN ]

Re:Bypassing Browser Security Warnings with Pseudo Password ... by kgbme on Thursday November 02, 2017 @08:44AM (#15609846)

Yes, exactly - there's a framework in place, which allows for the bullchit. :/

[ Parent | on HN ]