Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chained container proxies can't work #8157

Closed
cbosdo opened this issue Jan 12, 2024 · 0 comments
Closed

Chained container proxies can't work #8157

cbosdo opened this issue Jan 12, 2024 · 0 comments
Assignees
Labels
bug Something isn't working containerize P2 proxy

Comments

@cbosdo
Copy link
Contributor

cbosdo commented Jan 12, 2024

All container proxies configurations have the server public SSH key to use as authorized key. This is fine for the first proxy in a chain but not the others.

Here is the setup that is expected:

  • Proxy 0:

    • Proxy 0 SSH key pair
    • Server public key
  • Proxy 1:

    • Proxy 1 SSH key pair
    • Proxy 0 public key

Each proxy should expose his own public key in apache's /pub directory to let the next proxy use it or this key needs to be copied in the ssh.yaml's server_ssh_push_pub field of the next proxy.

This also raises the question of rotation of those keys: we probably want to provide some helper tool for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working containerize P2 proxy
Projects
None yet
Development

No branches or pull requests

2 participants