Post AT8vJ1cMpAbfhHEE3E by SeaRyanC@fosstodon.org
 (DIR) More posts by SeaRyanC@fosstodon.org
 (DIR) Post #AT8iu4ePDDaQPiWAmO by seldo@alpaca.gold
       2023-02-28T13:33:09Z
       
       0 likes, 0 repeats
       
       It has been [0] days since LastPass announced another apocalyptic data breach: https://infosec.exchange/@dangoodin/109939997666460592
       
 (DIR) Post #AT8krCarQN3s5UcNu4 by owenblacker@dataare.cool
       2023-02-28T13:55:01Z
       
       0 likes, 0 repeats
       
       @seldo I've actually got round to installing an alternative at last
       
 (DIR) Post #AT8vJ1cMpAbfhHEE3E by SeaRyanC@fosstodon.org
       2023-02-28T15:52:31Z
       
       0 likes, 0 repeats
       
       @seldo last time this happened we finally convinced my friend who kept saying "eh doesn't everyone have breaches from time to time?" to switch
       
 (DIR) Post #ATAgewShZ3Sb54cVO4 by akos@mas.to
       2023-03-01T12:17:46Z
       
       0 likes, 0 repeats
       
       @seldo this is not a new breach. LastPass provided new technical details about how the last one was executed.
       
 (DIR) Post #ATArFRbaFcZjdWopiy by seldo@alpaca.gold
       2023-03-01T14:16:32Z
       
       0 likes, 0 repeats
       
       @akos does that make it better or worse that they're still figuring out what happened 6 months ago?
       
 (DIR) Post #ATAsOFOF8UMiJQLAPo by akos@mas.to
       2023-03-01T14:29:11Z
       
       0 likes, 0 repeats
       
       @seldo Well, that's a different question. I just pointed out that people misunderstood this new reporting. But to answer this: investigations like this take time. The tricky part is not finding a particular attack, but making sure that there was (is) nothing else. I'm less sympathetic about the _way_ they communicate, this time they put the update on the support site instead of following up on the blog.