LastPass claims that it will encrypt URLs in their users’ vaults next month. Yes, that’s addressing the issue they’ve first been warned about back in 2015 to my knowledge. Yes, they plan to fix it for existing password entries as well. Maybe worth checking whether they’ll actually deliver.
They plan to start encrypting things like “equivalent domains” later this year. That’s an issue I received a bug bounty for in 2018 (this isn’t merely a privacy but also a “what if the server turns malicious” issue), good to know they finally want to do something about it.
This part sounds strange:
“LastPass says that due to restrictions in processing power in 2008, when that system was created, its engineers decided to leave those URLs unencrypted, lessening the strain on CPUs and minimizing the software's energy consumption footprint.”
That’s about mobile CPUs. And probably also about JS-based encryption implementations before WebCrypto or WebAssembly. And still: is it plausible that not encrypting a little bit of text (we are talking about 64 kB max even for heavy users) made any difference in 2008? Even considering that their “key derivation” back then was merely SHA256, I have a hard time believing that encryption was in any way significant for their CPU usage.