- the employee might not even work there, so the email not being valid anymore, the security argument looks lame
- contributions were used to be done by email, so the email address will be public anyway
11–20 of 21 posts
- the employee might not even work there, so the email not being valid anymore, the security argument looks lame
- contributions were used to be done by email, so the email address will be public anyway
This is exactly the level of competence I'd expect from "Telefónica Cybersecurity & Cloud Tech". The following comment is a good rebuttal to these idiots: https://github.com/steve-m/speedport_neo_source/issues/1#iss...
What does GDPR have to say here? Do maintainers have to rewrite git history if someone requests deleting their email from it?
I imagine this might fall under Art. 17 3. (Right to erasure), possibly (e) specifically.
> Paragraphs 1 and 2 shall not apply to the extent that processing is necessary:
> […]
> for the establishment, exercise or defence of legal claims.
> – https://gdpr-info.eu/art-17-gdpr/
Although I wonder how it works with Art. 16 (Right to rectification) which does not list such an exception.
I’m also not sure what constitutes a “personal activity” in Art. 2 2. (c) (Material scope), so it might just not apply depending on the project.
> This Regulation does not apply to the processing of personal data:
>[…]
> by a natural person in the course of a purely personal or household activity;
Link is down, archive.org copy: https://web.archive.org/web/20230109174817/https://github.co...
This is exactly the level of competence I'd expect from "Telefónica Cybersecurity & Cloud Tech". The following comment is a good rebuttal to these idiots: https://github.com/steve-m/speedport_neo_source/issues/1#iss...
Cesar Alierta wouldn't like your comment.
Can someone translate the title into English?
Link is down, archive.org copy: https://web.archive.org/web/20230109174817/https://github.co...
Why did it get removed? This kind of thing needs to be left up as evidence of their incompetence and as a warning to others that would follow in their footsteps.
The offending file is simply a DES speed benchmark submitted by this person: https://chromium.googlesource.com/chromium/deps/openssl/+/9c...