4 ms·
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 fa
by 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 agoIf 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.