Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Own sks import #85

Open
ghost opened this issue Jul 19, 2013 · 4 comments
Open

Own sks import #85

ghost opened this issue Jul 19, 2013 · 4 comments
Milestone

Comments

@ghost
Copy link

ghost commented Jul 19, 2013

Hello, I linked this plugin with my own sks.

When I look for a key with the key manager:

If the key is not present in the sks, it shows "Please create or import a key"
If the key is prsent, it doesn't show anything but the key is not displayed in the key manager.

Is that an intended behavior ?

Thanks.

@ghost
Copy link
Author

ghost commented Jul 19, 2013

I see on my sks server that the lookup is done correctly but nothing is imported locally.

@niklasfemerstrand
Copy link
Owner

Hi,

Is your SKS server publicly available so I could have a look? Perhaps there's some form of mismatch in the way that the backend is speaking to it.

@quemquis
Copy link

quemquis commented Aug 4, 2013

Hi,
I also have my own private SKS server and searching and importing works fine for me. (Chrome on win7).
I changed your code to only point to my own SKS server instead of the public MIT one.
What I'd like to look into is to have generated public keys automatically uploaded to my sks server. Anyone done this yet?

@niklasfemerstrand
Copy link
Owner

There will be a keyserver built into the plugin as soon as #65 is finished, basically the backend needs an add method and somewhere to add public keys to and then query that local storage before querying the remote storage.

I don't like the idea of uploading to anything except the local Roundcube DB storage which the admin can control. The problem with syncing with upstream key servers is that the protocol is broken because it doesn't have a way of revoking keys. Also there is missing validation, meaning anyone can upload any public key with any identifier. I consider this harmful.

Problems like these emerge when public keys are synced with upstream key servers:

http://cryptome.org/2013/07/assange-pk-19days.htm
http://cryptome.org/2013/07/mining-pgp-keyservers.htm

The designers of key servers didn't add any key verification even though each key is bound to an e-mail address. Shame, really, and unfortunately the only fix is to not sync upstream and being cautious with keys stored on them.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants