signal service security? #2002

Open
opened 2025-11-20 06:11:01 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @Silex on GitHub (Jun 23, 2025).

Hello,

https://github.com/netbirdio/netbird/tree/main/signal

Flags:
  -h, --help                        help for run
      --letsencrypt-domain string   a domain to issue Let's Encrypt certificate for. Enables TLS using Let's Encrypt. Will fetch and renew certificate, and run the server with TLS
      --port int                    Server port to listen on (e.g. 10000) (default 10000)
      --ssl-dir string              server ssl directory location. *Required only for Let's Encrypt certificates. (default "/var/lib/netbird/")
      --cert-file string            Location of your SSL certificate. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect
      --cert-key string             Location of your SSL certificate private key. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect

Global Flags:
      --log-file string    sets Netbird log path. If console is specified the the log will be output to stdout (default "/var/log/netbird/signal.log")
      --log-level string    (default "info")

When running this standalone, I don't get how it is secured, it looks like anyone could use it?

I don't see a key that only the management would know about or some secret, it looks like the signal service is open on the internet and anyone would be free to use it in their netbird self hosted installation.

And given peers have to connect to it, I don't see a way to restrict by IP either.

Originally created by @Silex on GitHub (Jun 23, 2025). Hello, https://github.com/netbirdio/netbird/tree/main/signal ``` Flags: -h, --help help for run --letsencrypt-domain string a domain to issue Let's Encrypt certificate for. Enables TLS using Let's Encrypt. Will fetch and renew certificate, and run the server with TLS --port int Server port to listen on (e.g. 10000) (default 10000) --ssl-dir string server ssl directory location. *Required only for Let's Encrypt certificates. (default "/var/lib/netbird/") --cert-file string Location of your SSL certificate. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect --cert-key string Location of your SSL certificate private key. Can be used when you have an existing certificate and don't want a new certificate be generated automatically. If letsencrypt-domain is specified this property has no effect Global Flags: --log-file string sets Netbird log path. If console is specified the the log will be output to stdout (default "/var/log/netbird/signal.log") --log-level string (default "info") ``` When running this standalone, I don't get how it is secured, it looks like anyone could use it? I don't see a key that only the management would know about or some secret, it looks like the signal service is open on the internet and anyone would be free to use it in their netbird self hosted installation. And given peers have to connect to it, I don't see a way to restrict by IP either.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2002