Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
Peter J. wrote: On Monday 25 May 2009 07:28:33 3BUIb3S50i 3BUIb3S50i wrote: I also have the same message with another IP. On Mon, May 25, 2009 at 1:26 AM, SmallSister development smallsis...@xs4all.nl wrote: theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! snip Yeah got the same message, 1 ip reports that the auto-update key is blown. Ip is in the range of 193.11.208.0/24. Some Student network in Goteborg. Freenet 0.7 Build #1210 build01210 Freenet-ext Build #26 r23771 wild guess: someone played with his node to make it send that announcement but the key was wrong because he didnt actually have it. now why would anyone do something like this? to see where the reports come from? ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
On Tuesday 26 May 2009 07:26:05 Luke771 wrote: Peter J. wrote: On Monday 25 May 2009 07:28:33 3BUIb3S50i 3BUIb3S50i wrote: I also have the same message with another IP. On Mon, May 25, 2009 at 1:26 AM, SmallSister development smallsis...@xs4all.nl wrote: theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! snip Yeah got the same message, 1 ip reports that the auto-update key is blown. Ip is in the range of 193.11.208.0/24. Some Student network in Goteborg. Freenet 0.7 Build #1210 build01210 Freenet-ext Build #26 r23771 wild guess: someone played with his node to make it send that announcement but the key was wrong because he didnt actually have it. now why would anyone do something like this? to see where the reports come from? Well he already knows their IPs so it doesn't do much good to have their email addresses. This should be fixed by 1212. We will give the peer a reasonable time to start transferring the data, and if they don't, we stop worrying about them. signature.asc Description: This is a digitally signed message part. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
On Monday 25 May 2009 07:28:33 3BUIb3S50i 3BUIb3S50i wrote: I also have the same message with another IP. On Mon, May 25, 2009 at 1:26 AM, SmallSister development smallsis...@xs4all.nl wrote: theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! snip Yeah got the same message, 1 ip reports that the auto-update key is blown. Ip is in the range of 193.11.208.0/24. Some Student network in Goteborg. Freenet 0.7 Build #1210 build01210 Freenet-ext Build #26 r23771 ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Auto-update key blown according to 1 peer(s)!
I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. These nodes told us that the key has been blown, but then disconnected, so we could not fetch the revocation certificate: * 213.112.69.244:9133 (213.112.69.244:9133) ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. I got the message too (from another IP) and they told me that it wasn't serious... Peter. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
I also have the same message with another IP. On Mon, May 25, 2009 at 1:26 AM, SmallSister development smallsis...@xs4all.nl wrote: theymos wrote: I just got this message. What do I do? Auto-update key blown according to 1 peer(s)! One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. I got the message too (from another IP) and they told me that it wasn't serious... Peter. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
On Saturday 23 May 2009 00:13:44 Juiceman wrote: On Fri, May 22, 2009 at 5:25 PM, SmallSister development smallsis...@xs4all.nl wrote: One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. Is this serious, someone attempting a sick joke or a developer hitting some wrong keys on his keyboard? Peter. I would assume someone is running a rogue node that they edited the code to that is exploiting the node2node fast warning system. It was only a matter of time before someone tried this. If you see more than one or if your node sees it for itself then you might worry. Agreed, it's probably not a problem. I certainly haven't blown the key. signature.asc Description: This is a digitally signed message part. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Auto-update key blown according to 1 peer(s)!
One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. Is this serious, someone attempting a sick joke or a developer hitting some wrong keys on his keyboard? Peter. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Auto-update key blown according to 1 peer(s)!
On Fri, May 22, 2009 at 5:25 PM, SmallSister development smallsis...@xs4all.nl wrote: One or more of your peers says that the auto-update key is blown! This means that an attacker may know the private key for the auto-update system and can therefore cause your node to run code of his choice (if you update)! The auto-update system has been disabled. It is also possible that your peers are deliberately lying about it. Your node has been unable to download the revocation certificate. Possible causes include an attack on your node to try to get you to update despite the key being blown, or your nodes lying about the key being blown. Please contact the developers or other Freenet users to sort out this mess. Is this serious, someone attempting a sick joke or a developer hitting some wrong keys on his keyboard? Peter. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe I would assume someone is running a rogue node that they edited the code to that is exploiting the node2node fast warning system. It was only a matter of time before someone tried this. If you see more than one or if your node sees it for itself then you might worry. -- I may disagree with what you have to say, but I shall defend, to the death, your right to say it. - Voltaire Those who would give up Liberty, to purchase temporary Safety, deserve neither Liberty nor Safety. - Ben Franklin ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
