One option for providing feedback on the health of the relay would be arm (<a href="http://www.atagar.com/arm">www.atagar.com/arm</a>) with the following config changes to keep with the aims of tor-ramdisk:<br># would prevent any connection related information from being queried<br>
startup.blindModeEnabled true<br><br># crops log messages after a day<br>
features.log.entryDuration 1<br><br>This would provide the user with:<br>- ps information (cpu/mem usage, uptime)<br>- basic relay information (fingerprint, flags held, version, etc)<br>- config (currently loaded torrc)<br>
- the last day's worth of logs<br>- graph of the bandwidth usage<br><br>The last two give a very good indication for if the relay's working right or not. If this is too much information then I'd be happy to augment arm to meet your needs. Cheers! -Damian<br>
<br><div class="gmail_quote">On Mon, Oct 11, 2010 at 8:25 PM, Anders Andersson <span dir="ltr"><<a href="mailto:pipatron@gmail.com">pipatron@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Mon, Oct 11, 2010 at 11:16 PM, Jacob Appelbaum <<a href="mailto:jacob@appelbaum.net">jacob@appelbaum.net</a>> wrote:<br>
> On 10/11/2010 10:52 AM, Anthony G. Basile wrote:<br>
>><br>
>> Hi everyone<br>
>><br>
>> I want to announce to the list that a new release of tor-ramdisk is out.<br>
>> Tor-ramdisk is an i686, x86_64 or MIPS uClibc-based micro Linux<br>
>> distribution whose only purpose is to host a Tor server in an<br>
>> environment that maximizes security and privacy. Security is enhenced by<br>
>> hardening the kernel and binaries, and privacy is enhanced by forcing<br>
>> logging to be off at all levels so that even the Tor operator only has<br>
>> access to minimal information. Finally, since everything runs in<br>
>> ephemeral memory, no information survives a reboot, except for the Tor<br>
>> configuration file and the private RSA key, which may be<br>
>> exported/imported by FTP.<br>
>><br>
><br>
> Via FTP? It's probably not a good idea to export a private key without<br>
> using encryption...<br>
><br>
> All the best,<br>
> Jake<br>
<br>
</div>My first thought as well. Pretty much every protocol invented is<br>
better than FTP, in this case and most other cases.<br>
<br>
Another question regarding the logging: I hope you include enough to<br>
know if the node is working correctly or not. The logs that are<br>
generated could also be deleted after a couple of minutes or an hour<br>
as well, which might make it possible to log some more information if<br>
necessary to verify functionality.<br>
<br>
Great project though, a lot of people request this.<br>
<div><div></div><div class="h5">***********************************************************************<br>
To unsubscribe, send an e-mail to <a href="mailto:majordomo@torproject.org">majordomo@torproject.org</a> with<br>
unsubscribe or-talk in the body. <a href="http://archives.seul.org/or/talk/" target="_blank">http://archives.seul.org/or/talk/</a><br>
</div></div></blockquote></div><br>