Update GPG signature for Tor project's Debian packages #601

New Issue

greg · 2025-09-18T14:51:31Z

greg commented

2025-09-18 14:51:31 +00:00

No description provided.

greg added the

bug

label 2025-09-18 14:51:31 +00:00

greg added this to the Current operational issues project 2025-09-18 14:51:31 +00:00

greg commented

2025-09-18 15:16:02 +00:00

Actually, I think this might only be an issue on the ejabberd nodes, as the chef resource for a repo is supposed to take care of updating the GPG signature when given. Maybe tor used to be a dependency on ejabberd nodes but not anymore? That would explain why the tor code isn't being run in Chef but the repo has been set up

raucao commented

2025-09-19 13:28:10 +00:00

Yes, it's routing from the LBs: https://gitea.kosmos.org/kosmos/chef/src/branch/master/site-cookbooks/kosmos-base/recipes/tor_services.rb#L8-L17

I just manually changed it to point to ejabberd-4s private IP directly. Should be done automatically in the recipe, as per the open TODO. (Not sure if we can round-robin to multiple back-ends in a Tor service.)

Either way, we should probably remove Tor entirely from the ejabberd nodes.

Yes, it's routing from the LBs: https://gitea.kosmos.org/kosmos/chef/src/branch/master/site-cookbooks/kosmos-base/recipes/tor_services.rb#L8-L17 I just manually changed it to point to `ejabberd-4`s private IP directly. Should be done automatically in the recipe, as per the open TODO. (Not sure if we can round-robin to multiple back-ends in a Tor service.) Either way, we should probably remove Tor entirely from the ejabberd nodes.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#601