Post #2743725
2026-05-06 15:25 UTC
True, but there's a big fucking difference between handing over the keys without being asked, and doing basic fucking due diligence and not loading all your passwords in plain text into memory by default.
([@iglou@programming.dev](https://programming.dev/u/iglou) ) I can't defend MicroSlop because that mentality is pants on head stupid and is directly in opposition to any statement that they care about security. Because, again, they made their browser behave this way for no real reason besides blowing smoke up our ass. Chromium handles passwords properly, MicroSlop chose to do it insecurely and is hiding behind the dumbest defense. Because their OS has more holes than Swiss cheese and they refuse to plug a basic security hole that they put there intentionally.
Replies (1)
-
@iglou@programming.dev 2026-05-06 15:53
Chrome's handling is barely more secure. A compromised device will have a much easier time reading Chrome's encrypted store than scanning your RAM to find passwords. Remember that if you don't need to input a password to open the store, then anything with access to your device can also read it. Wether it's encrypted in your RAM or not barely makes any difference in how difficult the task is. The only solution is: Browsers should require a password. Or even better: Use a dedicated, properly secured password manager.