| ▲ | milkshakes a day ago |
| maybe you should stop trusting random people on the internet making extraordinary claims without proof then? |
|
| ▲ | baby_souffle a day ago | parent | next [-] |
| Isn't "assume vulnerable" The only prudent thing to do here? |
| |
| ▲ | milkshakes a day ago | parent | next [-] | | everything is vulnerable. the question is, has this researcher demonstrated that they have discovered and successfully exploited such a vulnerability. what exactly in this post makes you believe that this is the case? | |
| ▲ | refulgentis a day ago | parent | prev [-] | | No? Yes? Mu? After some hemming and hawing, my most cromulent thought is, having good security posture isn't synonymous with accepting every claim you get from the firehose |
|
|
| ▲ | 999900000999 a day ago | parent | prev [-] |
| https://arstechnica.com/tech-policy/2025/07/nyt-to-start-sea... |
| |
| ▲ | ameliaquining a day ago | parent [-] | | This is going to be subject to the legal discovery process with the usual safeguards to prevent leaks; in particular, the judge will directly supervise the decision of who needs access to these logs, and if someone discloses information derived from them for an improper purpose, there's a very good chance they'll go to jail for contempt of court, which is much more stringent than you can usually expect for data privacy. You can still quite reasonably be against it, but you cannot reasonably call it "plain text logs available for everyone at the company to view". |
|