i was just thinking that encrypted s2s seems to require a valid certificate on the remote server, not on the server initiating the connection, so i think it'd be possible to completely disable certificates on snikket's side and let traefik manage tls termination from incoming connections?
i'll have to run some tests only running prosody so i don't have to mess with anything else...
i was just thinking that encrypted s2s seems to require a valid certificate on the remote server, not on the server initiating the connection, so i think it'd be possible to completely disable certificates on snikket's side and let traefik manage tls termination from incoming connections?
i'll have to run some tests only running prosody so i don't have to mess with anything else...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We can't go mainline proper until this one is solved:
I was looking into snikket-web-proxy, I think it's possible to fork it to disable HTTPS entirely and let traefik/caddy manage the TLS termination.
i was just thinking that encrypted s2s seems to require a valid certificate on the remote server, not on the server initiating the connection, so i think it'd be possible to completely disable certificates on snikket's side and let traefik manage tls termination from incoming connections?
i'll have to run some tests only running prosody so i don't have to mess with anything else...