Hello, I've found no information - after short googling - if I should take some action after an exit node got seized. Like marking the fingerprint as compromised or something like that. I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this. Node in question: https://metrics.torproject.org/rs.html#details/AF8A3EE078EB81338461F178DBE5C... And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ? Cheers Michael
Michael, Why was it seized? If you're wanting to put a new node up I would start from scratch. John
On Sep 12, 2018, at 09:42, "tor-relays@geek1.de" <tor-relays@geek1.de> wrote:
Hello,
I've found no information - after short googling - if I should take some action after an exit node got seized. Like marking the fingerprint as compromised or something like that.
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
Node in question: https://metrics.torproject.org/rs.html#details/AF8A3EE078EB81338461F178DBE5C...
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
Cheers Michael _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hy, the exit node is just collateral damage. It has nothing to do with it's single purpose role as an exit node. Cheers On 12.09.18 17:03, John Ricketts wrote:
Michael,
Why was it seized?
If you're wanting to put a new node up I would start from scratch.
John
On Sep 12, 2018, at 09:42, "tor-relays@geek1.de" <tor-relays@geek1.de> wrote:
Hello,
I've found no information - after short googling - if I should take some action after an exit node got seized. Like marking the fingerprint as compromised or something like that.
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
Node in question: https://metrics.torproject.org/rs.html#details/AF8A3EE078EB81338461F178DBE5C...
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
Cheers Michael _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Wed, 12 Sep 2018 16:34:48 +0200 tor-relays@geek1.de wrote:
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
I find it surprising that you are able to do that, is the provider not mad at you for having one of their servers seized? Or even if yours, for causing a commotion and ruckus in their datacenter.
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
It is certainly not okay to run a node keeping the same private key that the police now has. You should start from scratch, and I think the procedure is actually such that the Tor project will blacklist the affected fingerprint. -- With respect, Roman
The hoster handled this case quiet professionally, I guess it's a standardized process for most hosting operators. As far as I know the police just seizes the disks and the hoster just adds new ones. On 12.09.18 17:08, Roman Mamedov wrote:
On Wed, 12 Sep 2018 16:34:48 +0200 tor-relays@geek1.de wrote:
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
I find it surprising that you are able to do that, is the provider not mad at you for having one of their servers seized? Or even if yours, for causing a commotion and ruckus in their datacenter.
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
It is certainly not okay to run a node keeping the same private key that the police now has. You should start from scratch, and I think the procedure is actually such that the Tor project will blacklist the affected fingerprint.
Hi, I'm sorry to hear your exit node got seized, thanks for sharing that information. tor-relays@geek1.de:
I've found no information - after short googling - if I should take some action after an exit node got seized. Like marking the fingerprint as compromised or something like that.
you can send an email to bad-relays@lists.torproject.org ideally from the email address given in your relays ContactInfo https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
Node in question: https://metrics.torproject.org/rs.html#details/AF8A3EE078EB81338461F178DBE5C...
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
It is better to create new keys and not to restore the old once. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
Hy, thanks for the link and email, I've informed the tor project about it. I'll bring it back online as a new node from scratch. Cheers On 12.09.18 17:12, nusenu wrote:
Hi,
I'm sorry to hear your exit node got seized, thanks for sharing that information.
tor-relays@geek1.de:
I've found no information - after short googling - if I should take some action after an exit node got seized. Like marking the fingerprint as compromised or something like that.
you can send an email to bad-relays@lists.torproject.org
ideally from the email address given in your relays ContactInfo
https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
I'd guess it's ok to just set up a new exit node on the same IP and everything should be fine but I'm not quite 100% sure on this.
Node in question: https://metrics.torproject.org/rs.html#details/AF8A3EE078EB81338461F178DBE5C...
And another question about this topic: Would it be better to create a new exit from scratch or is it ok to restore the latest backup with all keys, etc. ?
It is better to create new keys and not to restore the old once.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (4)
-
John Ricketts -
nusenu -
Roman Mamedov -
tor-relays＠geek1.de