svnserve, the standalone Subversion server behind svn:// URLs.
svnserve speaks Subversion's own custom protocol on TCP 3690, the transport behind svn:// and svn+ssh:// URLs, as an alternative to serving repositories through Apache and mod_dav_svn on HTTP. The server greets every connection with a plaintext capability list before authentication. It survives on internal build servers, legacy corporate repositories, and appliances that shipped with Subversion; svnserve's default authentication is CRAM-MD5 against a passwd file, with Cyrus SASL as an optional upgrade.
Do not expose
The svn:// protocol has no transport encryption — repository contents and CRAM-MD5 exchanges cross the wire in the clear. Use svn+ssh, or mod_dav_svn over HTTPS, for anything off the local network.
$ nc -w 3 TARGET 3690 | head -c 60; echoSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.