Update README.md

This commit is contained in:
yakamok 2018-07-04 21:35:15 +02:00 committed by GitHub
parent 65f6d59d39
commit 17473f78a5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -10,6 +10,22 @@ For example there is a copy of the GDPR uploaded to the key-servers, points if s
I wrote this because i think this charactaristic of key-servers is actually dangerous, for example someone could upload leaked data and it would be spread around the world and accessible by anyone and unstoppable. I wrote this because i think this charactaristic of key-servers is actually dangerous, for example someone could upload leaked data and it would be spread around the world and accessible by anyone and unstoppable.
### Which Parts of the GDPR this might be effected by:
I am not a lawyer and i advise always seeking legal advice as i am purly expressing my opinion of what i think and this maybe wrong.
__Article 17__ (Right to eraseure('right to be forgotten'))
sections 1(b)/2 - the data subject withdraws consent on which the processing is based according to point (a) of Article 6(1), or
point (a) of Article 9(2), and where there is no other legal ground for the processing;
1(d) -the personal data have been unlawfully processed;
__Article 7(3)__ (Conditions for consent)
[The data subject shall have the right to withdraw his or her consent at any time.....It shall be as easy to withdraw as to give consent.]
I think theres more in the GDPR that could apply to PGP key servers, but i don't have alot of time to look through it at the moment, i will add more when i can. Also suggestions and pull requests with more information is welcome.
__Notice:__ This Program is very slow to add data to the gpg pubkey so dont plan on super large files. __Notice:__ This Program is very slow to add data to the gpg pubkey so dont plan on super large files.
### upload-file.py ### upload-file.py