4 ms·

> "If it helps, you including user ids like this violates GDPR... so this should be addressed by the rust team." This smells like bullshit to me, but I don't k

> "If it helps, you including user ids like this violates GDPR... so this should be addressed by the rust team." This smells like bullshit to me, but I don't know enough about GDPR to say for sure. Can anyone comment? edit: more broadly, can free software (ie: rustc), run on individual developer machines, actually run afoul of the GDPR somehow?

khimaros 6y ago
while it seems like an issue worth fixing, i doubt that GDPR applies here. the Rust foundation is not providing a service to the end users of any of these binaries, and it is at the developers own discretion whether to distribute the binaries rustc produces. it's equivalent to saying that your self-hosted Postfix servers are violating GDPR because they includes information about which devices your message passed through on your local network during delivery in the header.
thrower123 6y ago
I really, really enjoy how even after all these years, still almost nobody knows what GDPR actually entails and how to actually be in compliance with it. Great work, Brussels, great work.
lupire 6y ago
It's not a violation at all.
carols10cents 6y ago
Yeah, there's no way this is a violation of GDPR. There's a trivial workaround, build in a container. The article is being overly sensational and should have fact checked the commenter's statement.
- alpaca128 6y ago
  > There's a trivial workaround, build in a container. The difficulty of a workaround is irrelevant for the nature of the problem. Also as the article mentions this is undocumented behaviour, so unless rustc/cargo builds everything in containers by default this workaround should not be required. And while I'm not an expert in GDPR details it is still very problematic as the file path to the compiled project could contain an arbitrary selection of very personal information that would then be leaked. Sure you can build it in a container, you could also run a car assembly line in a cleanroom. It's just ridiculous to have that as requirement to not secretly leak paths.
  - carols10cents 6y ago
    If the GDPR even applies, your mechanism for requesting that your personal information be removed is to build your code in a container. But in any case, it wouldn't be rustc distributing your built code.

khimaros 6y ago

while it seems like an issue worth fixing, i doubt that GDPR applies here. the Rust foundation is not providing a service to the end users of any of these binaries, and it is at the developers own discretion whether to distribute the binaries rustc produces. it's equivalent to saying that your self-hosted Postfix servers are violating GDPR because they includes information about which devices your message passed through on your local network during delivery in the header.

thrower123 6y ago

I really, really enjoy how even after all these years, still almost nobody knows what GDPR actually entails and how to actually be in compliance with it. Great work, Brussels, great work.

lupire 6y ago

It's not a violation at all.

carols10cents 6y ago

Yeah, there's no way this is a violation of GDPR. There's a trivial workaround, build in a container. The article is being overly sensational and should have fact checked the commenter's statement.

alpaca128 6y ago
> There's a trivial workaround, build in a container. The difficulty of a workaround is irrelevant for the nature of the problem. Also as the article mentions this is undocumented behaviour, so unless rustc/cargo builds everything in containers by default this workaround should not be required. And while I'm not an expert in GDPR details it is still very problematic as the file path to the compiled project could contain an arbitrary selection of very personal information that would then be leaked. Sure you can build it in a container, you could also run a car assembly line in a cleanroom. It's just ridiculous to have that as requirement to not secretly leak paths.
- carols10cents 6y ago
  If the GDPR even applies, your mechanism for requesting that your personal information be removed is to build your code in a container. But in any case, it wouldn't be rustc distributing your built code.