The same executable ("or") functions as both client and server, depending
on which ports are specified in the configuration file. You can specify:
-* APPort: client applications (eg privoxy, Mozilla) can speak socks to
+* SocksPort: client applications (eg privoxy, Mozilla) can speak socks to
this port.
-* OPPort: onion proxies (client onion routers) connect to this port.
* ORPort: other onion routers connect to this port
* DirPort: onion proxies and onion routers speak http to this port, to
pull down a directory of which nodes are currently available.
(Unless otherwise noted, tokens on the same line are space-separated.)
Router ::= Router-Line Date-Line Onion-Key Link-Key Signing-Key Exit-Policy Router-Signature NL
-Router-Line ::= "router" nickname address ORPort APPort DirPort bandwidth NL
+Router-Line ::= "router" nickname address ORPort SocksPort DirPort bandwidth NL
Date-Line ::= "published" YYYY-MM-DD HH:MM:SS NL
Onion-key ::= "onion-key" NL a public key in PEM format NL
Link-key ::= "link-key" NL a public key in PEM format NL
Base-64-encoded-signature NL "-----END SIGNATURE-----" NL
ORport ::= port where the router listens for routers/proxies (speaking cells)
-APPort ::= where the router listens for applications (speaking socks)
+SocksPort ::= where the router listens for applications (speaking socks)
DirPort ::= where the router listens for directory download requests
bandwidth ::= maximum bandwidth, in bytes/s
# Ports for various services. Comment out or set to 0 if you're not
# offering that service.
ORPort 9004 # listening for cell-speaking connections
-APPort 9024 # listening for socks-speaking connections
+SocksPort 9024 # listening for socks-speaking connections
#DirPort 0
# Leave this set, or we'll be treated like a client.