[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
hidden services spoof
- To: or-talk@xxxxxxxxxxxxx
- Subject: hidden services spoof
- From: Arrakistor <arrakistor@xxxxxxxxx>
- Date: Mon, 11 Sep 2006 16:10:27 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Mon, 11 Sep 2006 17:08:27 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:x-mailer:reply-to:organization:x-priority:message-id:to:subject:mime-version:content-type:content-transfer-encoding; b=o70tMQtkJWkslk1E10ku7JJ2YqkDaIfrRXFjehwbxoCCeLwWjvqo8bRLjLg1RzVPJ2IaUQCfBB43pp5b14I/grTtqFf6BVv9v03VwvdQjNMQpECYVQkMR2GIGmMrweZ0L6nVSotBoAl3EYSleQjB9ryIZ24F/e6neIxxhRZ52K4=
- Organization: Torpark
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
I am writing an updater for tor to automatically grab the latest
version. One problem I am coming across is where to host it so they
cannot be spoofed. I was thinking of putting it at a server in a
.onion address. How easily can a node in the tor network be spoofed?
Is there a better solution than hosting the tor updates inside a
.onion server?
Regards,
Arrakistor