test proxy dante
ho fatto una prova sul mio pc
- configurato sockd.conf
- avviato il server socksd
- configurato socks.conf
- avviato un :
socksify telnet pop.tiscali.it 110
dopo alcuni messaggi ...
(telnet[19447]: socketoptdup(): setsockopt(0, 32): Invalid argument (errno = 22))
accedo tranquillamente al server di posta
ecco i file di configurazione:
sockd.conf:
# A sample sockd.conf that I use for demonstrating SOCKS
#
# See the actual file /etc/sockd.conf in your own installation of
# Dante for further details.
####################### ServerSettings ##########################
# the server will log both via syslog, to stdout and to /var/log/sockd
logoutput: syslog stdout /var/log/sockd
internal: 127.0.0.1 port = 1080
# all outgoing connections from the server will use the IP address
# 195.168.1.1
external: eth0 # See my Slide 23 for what it means to
# to run a SOCKS server behind a home router
# list over acceptable methods, order of preference. A method not set
# here will never be selected. If the method field is not set in a
# rule, the global method is filled in for that rule. Client
# authentication method:
method: username none
# The following is unnecessary if not doing authentication. When doing
# something that can require privilege, it will use the userid "sockd".
#user.privileged: sockd
# When running as usual, it will use the unprivileged userid of "sockd".
#user.notprivileged: sockd
user.notprivileged: nobody
# do you want to accept connections from addresses without dns info?
# what about addresses having a mismatch in dnsinfo?
# srchost: nounknown nomismatch
# 26
############################ RULES ############################
# There are two kinds and they work at different levels. (See Slides 24)
#
#===================== rules checked first ===========================
# Allow our clients, also provides an example of the port range command.
#client pass {
# from: 10.0.0.0/8 port 1-65535 to: 0.0.0.0/0
# method: rfc931 # match all idented users that also are in passwordfile
#}
client pass {
from: 192.168.1.0/24 port 1-65535 to: 0.0.0.0/0
}
client pass {
from: 127.0.0.0/8 port 1-65535 to: 0.0.0.0/0
}
client block {
from: 0.0.0.0/0 to: 0.0.0.0/0
log: connect error
}
#========================== the rules checked next ================
#block {
# from: 0.0.0.0/0 to: 127.0.0.0/8
# log: connect error
#}
pass {
from: 192.168.1.0/24 to: 0.0.0.0/0
protocol: tcp udp
}
pass {
from: 127.0.0.0/8 to: 0.0.0.0/0
protocol: tcp udp
}
block {
from: 0.0.0.0/0 to: 0.0.0.0/0
log: connect error
}
# See /etc/sockd.conf of your installation for additional examples
# of such rules.
socks.conf:
# A sample socks.conf that I use for demonstrating SOCKS clients
#
# See the actual file /etc/socks.conf in your own installation of
# Dante for further details.
#debug: 1
logoutput: stdout /var/log/socks
# Send the dns lookups to the proxy server:
route {
from: 0.0.0.0/0 to: 0.0.0.0/0 via: 127.0.0.1 port = 1080
command: bind
}
# Send client requests to the proxy server at the address shown:
route {
from: 0.0.0.0/0 to: 0.0.0.0/0 via: 127.0.0.1 port = 1080
protocol: tcp udp # server supports tcp and udp.
proxyprotocol: socks_v4 socks_v5 # server supports socks v4 and v5.
method: none #username # we are willing to authenticate via
# method "none", not "username".
}
# Same as above except that the remote services may now be named
# by symbolic hostnames:
route {
from: 0.0.0.0/0 to: . via: 127.0.0.1 port = 1080
protocol: tcp udp
proxyprotocol: socks_v4 socks_v5
method: none #username
}