5 ms·
@dang, could the title be updated to indicate that this is another update to the existing blog post? Currently reads like it's a new incident, not the aug2022 i
by jackson1442 4y ago
@dang, could the title be updated to indicate that this is another update to the existing blog post? Currently reads like it's a new incident, not the aug2022 incident.
- dang 4y agoSure, I've added "[updated]" above.
- lyu07282 4y agotbh even "Notice of Recent Security Incident [updated]" instead of "LastPass User Vaults stolen in recent hack" or something feels like PR damage control in favor to LastPass
- dang 4y agoI agree that corporate press releases usually bury the lede and, in the case of negative stories, are often outright misleading. For that reason we often change them (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=press%20release%20by%3Adang&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...). I've used your suggestion above. Thanks! If anyone suggests a better title (i.e. more accurate and neutral), we can change it again, and if there's a better third-party article that covers whatever the latest news on this is, we could switch to it.
- iLoveOncall 4y agoIt absolutely is a new incident. LastPass is in PR damage control mode and trying to make it seem like accessing those backups was inevitable after their source code theft, but it's not the fucking case. This is yet another failure on LastPass' end. The only thing in common is the attacker, that's it.
- ghostpepper 4y agoThey updated the fifth paragraph down to mention that encrypted passwords and unencrypted metadata has been stolen - in my mind that practically qualifies as a new incident