Can't upload public PGP/GPG key to OpenSKS server












0















So I have an Intranet that won't be connected to the Internet when in use, and one of the functionalities I need is the ability to send and receive encrypted emails.
I chose to use an OpenSKS server for easier exchange of public keys, which i run on Ubuntu 18.04. I set it up using the following commands I found online:



sudo apt-get install sks
sudo sks build
sudo chown -Rc debian-sks:debian-sks /var/lib/sks/DB
sudo /etc/init.d/sks start


After that the system tells me:



[ ok ] Starting sks (via systemctl): sks.service.


So I assume that it's properly set up.



The clients that'll be connected to the network run Win10 Home and use ThunderBird with the Enigmail extension. During Setup, I put in the IP of the OpenSKS server and tried uploading my key to it. After that didn't work I added a AAAA-entry for this server on my WinServer which functions as the DNS-server on my network so that i could enter "keys.local" as the server address in Thunderbird/Enigmail. I thought this would solve my problem because every tutorial I found online also had a proper URL for the keyserver instead of its IP-address.



But that didn't change anything, I still get an error telling me the upload failed.



If anyone has encountered a similar problem and has a solution for this, I'd be very grateful. I hope I provided all of the needed information about my situation, if not, just tell me and I'll try to provide it.










share|improve this question

























  • Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

    – grawity
    Jan 7 at 8:50











  • Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

    – cybergwd
    Jan 7 at 9:02








  • 1





    Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

    – grawity
    Jan 7 at 9:05













  • I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

    – cybergwd
    Jan 7 at 9:07











  • Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

    – grawity
    Jan 7 at 9:57
















0















So I have an Intranet that won't be connected to the Internet when in use, and one of the functionalities I need is the ability to send and receive encrypted emails.
I chose to use an OpenSKS server for easier exchange of public keys, which i run on Ubuntu 18.04. I set it up using the following commands I found online:



sudo apt-get install sks
sudo sks build
sudo chown -Rc debian-sks:debian-sks /var/lib/sks/DB
sudo /etc/init.d/sks start


After that the system tells me:



[ ok ] Starting sks (via systemctl): sks.service.


So I assume that it's properly set up.



The clients that'll be connected to the network run Win10 Home and use ThunderBird with the Enigmail extension. During Setup, I put in the IP of the OpenSKS server and tried uploading my key to it. After that didn't work I added a AAAA-entry for this server on my WinServer which functions as the DNS-server on my network so that i could enter "keys.local" as the server address in Thunderbird/Enigmail. I thought this would solve my problem because every tutorial I found online also had a proper URL for the keyserver instead of its IP-address.



But that didn't change anything, I still get an error telling me the upload failed.



If anyone has encountered a similar problem and has a solution for this, I'd be very grateful. I hope I provided all of the needed information about my situation, if not, just tell me and I'll try to provide it.










share|improve this question

























  • Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

    – grawity
    Jan 7 at 8:50











  • Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

    – cybergwd
    Jan 7 at 9:02








  • 1





    Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

    – grawity
    Jan 7 at 9:05













  • I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

    – cybergwd
    Jan 7 at 9:07











  • Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

    – grawity
    Jan 7 at 9:57














0












0








0








So I have an Intranet that won't be connected to the Internet when in use, and one of the functionalities I need is the ability to send and receive encrypted emails.
I chose to use an OpenSKS server for easier exchange of public keys, which i run on Ubuntu 18.04. I set it up using the following commands I found online:



sudo apt-get install sks
sudo sks build
sudo chown -Rc debian-sks:debian-sks /var/lib/sks/DB
sudo /etc/init.d/sks start


After that the system tells me:



[ ok ] Starting sks (via systemctl): sks.service.


So I assume that it's properly set up.



The clients that'll be connected to the network run Win10 Home and use ThunderBird with the Enigmail extension. During Setup, I put in the IP of the OpenSKS server and tried uploading my key to it. After that didn't work I added a AAAA-entry for this server on my WinServer which functions as the DNS-server on my network so that i could enter "keys.local" as the server address in Thunderbird/Enigmail. I thought this would solve my problem because every tutorial I found online also had a proper URL for the keyserver instead of its IP-address.



But that didn't change anything, I still get an error telling me the upload failed.



If anyone has encountered a similar problem and has a solution for this, I'd be very grateful. I hope I provided all of the needed information about my situation, if not, just tell me and I'll try to provide it.










share|improve this question
















So I have an Intranet that won't be connected to the Internet when in use, and one of the functionalities I need is the ability to send and receive encrypted emails.
I chose to use an OpenSKS server for easier exchange of public keys, which i run on Ubuntu 18.04. I set it up using the following commands I found online:



sudo apt-get install sks
sudo sks build
sudo chown -Rc debian-sks:debian-sks /var/lib/sks/DB
sudo /etc/init.d/sks start


After that the system tells me:



[ ok ] Starting sks (via systemctl): sks.service.


So I assume that it's properly set up.



The clients that'll be connected to the network run Win10 Home and use ThunderBird with the Enigmail extension. During Setup, I put in the IP of the OpenSKS server and tried uploading my key to it. After that didn't work I added a AAAA-entry for this server on my WinServer which functions as the DNS-server on my network so that i could enter "keys.local" as the server address in Thunderbird/Enigmail. I thought this would solve my problem because every tutorial I found online also had a proper URL for the keyserver instead of its IP-address.



But that didn't change anything, I still get an error telling me the upload failed.



If anyone has encountered a similar problem and has a solution for this, I'd be very grateful. I hope I provided all of the needed information about my situation, if not, just tell me and I'll try to provide it.







email encryption thunderbird ubuntu-18.04 enigmail






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 7 at 9:05







cybergwd

















asked Jan 7 at 8:44









cybergwdcybergwd

11




11













  • Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

    – grawity
    Jan 7 at 8:50











  • Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

    – cybergwd
    Jan 7 at 9:02








  • 1





    Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

    – grawity
    Jan 7 at 9:05













  • I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

    – cybergwd
    Jan 7 at 9:07











  • Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

    – grawity
    Jan 7 at 9:57



















  • Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

    – grawity
    Jan 7 at 8:50











  • Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

    – cybergwd
    Jan 7 at 9:02








  • 1





    Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

    – grawity
    Jan 7 at 9:05













  • I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

    – cybergwd
    Jan 7 at 9:07











  • Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

    – grawity
    Jan 7 at 9:57

















Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

– grawity
Jan 7 at 8:50





Does the SKS server have any logfiles in /var/log, or messages in journalctl -b? Also, CNAME entry to what? CNAMEs point to an existing name. If all you had was an IP address, you needed an A/AAAA record.

– grawity
Jan 7 at 8:50













Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

– cybergwd
Jan 7 at 9:02







Oh yeah, I meant to write AAAA, my bad. Still pretty early around here. Using journalctl -b, it tells me about 20 times "ubuntu sks[1811]: 2019-01-07 00:58:05 <recon as client> error in callback.: Failure("No gossip partners available")"

– cybergwd
Jan 7 at 9:02






1




1





Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

– grawity
Jan 7 at 9:05







Finally, are you able to connect to the keyserver through a web browser (via http://keys.local:11371)?

– grawity
Jan 7 at 9:05















I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

– cybergwd
Jan 7 at 9:07





I can't connect to the server on port 11371, however I'm able to reach the regular apache default page I set up on the server because i was also planning on offering a webinterface to upload keys

– cybergwd
Jan 7 at 9:07













Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

– grawity
Jan 7 at 9:57





Apache is not relevant; if you can't connect to SKS directly, figure out why it isn't running. (It has a barebones web-ui built in.)

– grawity
Jan 7 at 9:57










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391401%2fcant-upload-public-pgp-gpg-key-to-opensks-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391401%2fcant-upload-public-pgp-gpg-key-to-opensks-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown