hi guys, sorry for late reply, i am away from home atm - currently on 3G from Africa
Aswan - no, your privkey is not your wallet address, neither secret key used for encoding wallet (also sometimes called private key (as contrasted to public key)... So in this case privkey holds no DRKs, nor no pathway to it... Reread my guide from start, if you are still unsure of the procedure.
dotnetmin - hopefully this also answers your questions (but i saw, that you got indepth reply in other threads).
all +
bgaer - for updating the darkcoind see next post.
dotnetmin darklord1981 for ssh unlocked to one IP only use this below, just substitute the fictious 555.555.555.555 ip with your own. also note that port 22 is no longer on list of generally allowed ports:
-----
IIP=`/sbin/ifconfig eth0 |sed --silent 's/.*inet addr:\(.*\) \ Bcast.*/\1/p'`
IPTABLES="/sbin/iptables"
echo "Activating firewall for $IIP"
echo 0 > /proc/sys/net/ipv4/ip_forward
$IPTABLES -F
$IPTABLES -t nat -F
$IPTABLES -t mangle -F
$IPTABLES -X
$IPTABLES -t nat -X
$IPTABLES -t mangle -X
$IPTABLES -t nat -P POSTROUTING ACCEPT
$IPTABLES -t nat -P PREROUTING ACCEPT
$IPTABLES -t nat -P OUTPUT ACCEPT
$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT DROP
$IPTABLES -P FORWARD DROP
$IPTABLES -A INPUT -i lo -j ACCEPT
$IPTABLES -A OUTPUT -o lo -j ACCEPT
$IPTABLES -A INPUT -s $IIP/32 -j ACCEPT
$IPTABLES -A OUTPUT -s $IIP/32 -j ACCEPT
$IPTABLES -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
$IPTABLES -A INPUT -d $IIP/32 -s 555.555.555.555/32 -j ACCEPT
$IPTABLES -A OUTPUT -s $IIP/32 -d 555.555.555.555/32 -j ACCEPT
$IPTABLES -A INPUT -d $IIP/32 -m multiport -p tcp --ports "9999" -j ACCEPT
$IPTABLES -A OUTPUT -s $IIP/32 -m multiport -p tcp --ports "9999" -j ACCEPT
-----
