[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
[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets
Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209 rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few hours ago. I updated using update.cmd because the built-in update wasn't working. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list support at freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 122.100.218.13:41232
[freenet-support] Bug report: 1 peers forcibly disconnected due to not acknowledging packets
Freenet asked me to report this bug to you. I'm on Freenet 0.7 Build #1209 rbuild01209-real, Freenet-ext Build #26 r23771. I just updated to 1209 a few hours ago. I updated using update.cmd because the built-in update wasn't working. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list supp...@freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 122.100.218.13:41232 ___ 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] Bug report - 1 peers forcibly disconnected due to not acknowledging packets
Freenet told me to report this to you. I'm on Freenet 0.7 Build #1204 r25209, Freenet-ext Build #26 r23771. I run only on the Opennet; I have no Darknet peers. I can answer any questions you have. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list supp...@freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 84.181.222.55:59685 ___ 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] Bug report - 1 peers forcibly disconnected due to not acknowledging packets
Freenet told me to report this to you. I'm on Freenet 0.7 Build #1204 r25209, Freenet-ext Build #26 r23771. I run only on the Opennet; I have no Darknet peers. I can answer any questions you have. Probably a bug: please report: 1 peers forcibly disconnected due to not acknowledging packets. 1 of your peers are having severe problems (not acknowledging packets even after 10 minutes). This is probably due to a bug in the code. Please report it to us at the bug tracker at https://bugs.freenetproject.org/ or to the support mailing list support at freenetproject.org. Please include this message and what version of the node you are running. The affected peers (you may not want to include this in your bug report if they are darknet peers) are: * 84.181.222.55:59685
