Bug 293239 - security/snowflake-tor: package ships with outdated default STUN server
Summary: security/snowflake-tor: package ships with outdated default STUN server
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Vinícius Zavam
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-17 14:49 UTC by Franciszek Koprowski
Modified: 2026-02-17 14:57 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (egypcio)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Franciszek Koprowski 2026-02-17 14:49:18 UTC 
After installing the latest version of snowflake-tor and leaving it running for 24h I noticed I wasn't getting any traffic. I noticed a lot of DNS queries on my local DNS going to stun.stunprotocol.org, a nxdomain. 

I found a commit from Jan 2023 here:
https://lists.torproject.org/mailman3/hyperkitty/list/tor-commits%40lists.torproject.org/message/OPHZRXAF2CQB6SY6KNOTDTKWRPAII6U6/?utm_source=

Where the default STUN server was changed from:

-stun URL (default "stun:stun.stunprotocol.org:3478")

To: 

+stun URL (default "stun:stun.l.google.com:19302")

This is a simple fix that might prevent user confusion as to why their snowflake proxy isnt working after following steps on https://community.torproject.org/relay/setup/snowflake/standalone/freebsd/
Comment 1 Franciszek Koprowski 2026-02-17 14:57:13 UTC 
Just to clarify, I'm referring to the STUN server specified by default in /usr/local/etc/rc.d/snowflake which is created when the package is installed.