4 ms·
I'm working on a project that aims to give a lot of freedom for user-generated content, and I've been wondering for a while how to protect from the picture-in-p
by Etherlord87 5y ago
I'm working on a project that aims to give a lot of freedom for user-generated content, and I've been wondering for a while how to protect from the picture-in-picture attacks.
One way is to ban an entire color region around a particular color you choose for fields requesting passwords or doing other sensitive data. The problem with it is of course that it's too big of a limitation.
But how about a pattern like yellow/black checkerboard or stripes? This would require the parent to be able to analyze the child's look, and whenever the security pattern would be detected, it would display some kind of a warning about the content being similar to a secured input without actually being the secured input...
- Cycl0ps 5y agoReminds me of EURion rings on banknotes. The issue is that this needs to be visible while unobstructive to the user. What about something pictographic, like HTTPS' padlock icon? Look for that in any user content with an input field and flag it when found. Of course, that still assumes users would check for the lock in the first place. https://en.m.wikipedia.org/wiki/EURion_constellation https://en.m.wikipedia.org/wiki/EURion_constellation