kosmos/chef
8
3
Fork 0
Code Issues 39 Pull Requests Projects 2 Activity

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

New Issue
Open
opened 2025-09-18 14:51:31 +00:00 by greg · 2 comments
greg commented 2025-09-18 14:51:31 +00:00
Owner
Copy Link
Copy Source
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
Author
Owner
Copy Link
Copy Source

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

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
Owner
Copy Link
Copy Source

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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
service
discourse
Kosmos Community Forums
monitoring
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
lightning
Lightning address, lndhub, etc.
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
 design
Graphic/visual design
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 good first issue
Dive in, and start contributing
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 on hold
Currently not actionable
 ops
Manual IT ops activities
 question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Current operational issues
Uncategorized
Assignees
Clear assignees
bkero (bkero) bumi (bumi) fsmanuel (fsmanuel) galfert (galfert) greg (Greg) hueso (hueso) raucao (Râu Cao) slvrbckt (Nick Jennings)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#601