Anothony,
If the Toolsack requirement is detrimental, you can instead use the
Microsoft Winsock Controls. They are installed by numerous Microsoft
products, such as Office and VB. I'm not sure it comes standard with
Windows, though. See my previous email with the original links for Toolsack
and MS Winsock Controls.
----- Original Message ----
From: Anothony Georgeo <anogeorgeo@xxxxxxxxx>
To: or-talk@xxxxxxxxxxxxx
Sent: Thursday, August 3, 2006 8:56:35 PM
Subject: Re: Re[4]: Using Tor signals on Win32 NT (eg. pseudo-signals)?
Hi clowndevil,
Your .vbs works very well, thanks alot.
I took the liberty of modifying your .vbs to use the
SHUTDOWN and NEWNYM pesudo-signals.
I am going to write a Wiki entry for installing
Toolsack and using these verions of your .vbs: HUP,
SHUTDOWN and NEWNYM.
Toolsack runs on all versions of Win32 from 98 to XP
so this should prove very usefull to many, many
Windows users.
The only downside I see to your method is the
requirment of Toolsack. Do you have any idea how
portable Toolsack is?
On second thought, I could just put Toolsack onto a
USB and create a .reg file of it's registry entries
(via. RegShot) to be executed on the local computer
(Win32 OS of course). This way I could have Tor,
Vidalia, Toolsack and your .vbs on my USB for complete
portablity ;-)...
The two .vbs files I modified (SHUTDOWN and NEWNYM)
are at the bottom of this email.
-------------------------------------------------
On a side note:
I plan on writing another Wiki entry for my FireFox
and Privoxy HTTP/S environmental variable scrubbing
template. IMO this template should be used by all Tor
users to create a large anonymity set.
Please see...
-Privoxy User.Actions file:
<http://archives.seul.org/or/talk/May-2006/msg00367.html>
In my yet to be released final update (#5) for the
User.Actions template I commented out the
"+limit-connect{443}" and "{+limit-connect{-1}" lines
as the Firefox hacks I propose can handle HTTPS
scrubbing. Also, disregard the info in that link
about 2 different anonymity sets due to HTTP vs. HTTPS
and compression vs. preventing compression. Now there
is only 1 anonymity set and it handles HTTP/S and
prevents compression (via. the FF hacks below).
-FireFox hacks:
<http://archives.seul.org/or/talk/May-2006/msg00365.html>
---------------------------------------------------
NewNym.vbs:
--
'Make torsock out socket name
set torsck = CreateObject("Toolsack.Socket")
'Connect to Tor's control port
torsck.Connect "localhost", 9051
'Auth so we can send commands
torsck.Write "AUTHENTICATE" & vbcrlf
'Read the buffer so we know what to do
chktxt = torsck.ReadLine
if (chktxt = "250 OK") then
'If we get an OK then send the reload signal
torsck.Write "SIGNAL NEWNYM" & vbcrlf
else
'Other wise goto a failed message box
call failed
end if
'Again read the buffer
chktxt = torsck.ReadLine
if (chktxt = "250 OK") then
'If we get an OK then Tor creates/uses new circuits
msgbox "All subseqent internet connetions will use a
different circuit (eg. chain) of Tor proxy servers.
This means all subseqent internet connections will use
a differnet Exit Node and have a different IP address
and than your previous interent connections."
else
'Other wise goto failed message box
call failed2
end if
'Everything went good so finish the connection
call finish
sub failed
'Message box for failed auth
msgbox "Failed to authenticate."
call finish
end sub
sub failed2
'Message box for failed reload signal
msgbox "Failed to send NEWNYM pseudo-signal."
call finish
end sub
sub finish
'Send a QUIT command to Tor and close the connection
torsck.Write "QUIT" & vbcrlf
'Again read the buffer
chktxt = torsck.ReadLine
if (chktxt = "250 closing connection") then
'Do nothing because the Tor closed the connection
for us
else
'Something happen when trying to clsoe the
connection so close it anyway
torsck.Close
end if
end sub
--
Shutdown.vbs
--
'Make torsock out socket name
set torsck = CreateObject("Toolsack.Socket")
'Connect to Tor's control port
torsck.Connect "localhost", 9051
'Auth so we can send commands
torsck.Write "AUTHENTICATE" & vbcrlf
'Read the buffer so we know what to do
chktxt = torsck.ReadLine
if (chktxt = "250 OK") then
'If we get an OK then send the reload signal
torsck.Write "SIGNAL SHUTDOWN" & vbcrlf
else
'Other wise goto a failed message box
call failed
end if
'Again read the buffer
chktxt = torsck.ReadLine
if (chktxt = "250 OK") then
'If we get an OK then Tor gracefully shutsdown
msgbox "Tor will now close. If you are operating a
server the server will gracefully shutdown (after 30
seconds) without unexpectedly dropping Tor client's
internet connections it is routing."
else
'Other wise goto failed message box
call failed2
end if
'Everything went good so finish the connection
call finish
sub failed
'Message box for failed auth
msgbox "Failed to authenticate."
call finish
end sub
sub failed2
'Message box for failed reload signal
msgbox "Failed to send SHUTDOWN pseudo-signal."
call finish
end sub
sub finish
'Send a QUIT command to Tor and close the connection
torsck.Write "QUIT" & vbcrlf
'Again read the buffer
chktxt = torsck.ReadLine
if (chktxt = "250 closing connection") then
'Do nothing because the Tor closed the connection
for us
else
'Something happen when trying to clsoe the
connection so close it anyway
torsck.Close
end if
end sub
--
Thank you very much, Anogerogeo
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com