Sudden appearance of RSA signature error

[Phil]

> Hi
> 
> I have been happily using tor v0.1.2.18 (not as a
> server) since it was released with no errors in the
> log.
> 
> Today, however, the following warnings suddenly
> appeared out of nowhere:
> 
> Jan 25 02:47:20.795 [notice] Tor v0.1.2.18. This is
> experimental software. Do not rely on it for strong
> anonymity.
> Jan 25 02:47:20.796 [notice] Initialized libevent
> version 1.3e using method poll. Good.
> Jan 25 02:47:20.796 [notice] Opening Socks listener
> on
> 127.0.0.1:9050
> Jan 25 02:47:21.714 [warn] crypto error while
> checking
> RSA signature: block type is not 01 (in rsa
> routines:RSA_padding_check_PKCS1_type_1)
> Jan 25 02:47:21.714 [warn] crypto error while
> checking
> RSA signature: padding check failed (in rsa
> routines:RSA_EAY_PUBLIC_DECRYPT)
> Jan 25 02:47:21.715 [warn] Invalid signature -1
> Jan 25 02:47:21.715 [warn] Error reading router;
> skipping
> Jan 25 02:47:22.140 [notice] We now have enough
> directory information to build circuits.
> Jan 25 02:47:31.019 [notice] Tor has successfully
> opened a circuit. Looks like client functionality is
> working.
> 
> What is this and why has this warning appeared all
> of
> a sudden?
> 
> Is this a problem?  Should I stop using tor?
> 
> Does it mean there is a bad node?  If so, is it
> skipping that node?
> 
> Is it to do with the release of v0.1.2.19?
> 
> Thanks.
> 
> 
UPDATE:  The warning dissappeared after posting this
message and restarting tor.


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ