Re: Authentication for web interface

On Sun, 10 Mar 2013 00:31:48 -0800, Robert Connolly wrote:
> Hello.
> 
> I am running Freenet on a remote server. This server allows me to use 
> 1TiB of traffic per month, 100GB of storage, 10MiB per second
> internet connection, is reliable and stable. This is helpful to
> opennet, because it is able to relay a lot of traffic. It also makes
> it easy to use Freenet from my mobile phone. I am using SSH to tunnel
> between localhost ports.
> 
> If I run Freenet on my laptop, I would have to limit the traffic to 5
> or 10 KiB per second, because this adds up after a month. It would be
> less stable for opennet because it has less uptime. It would be more 
> complicated to use with my mobile phone, because I would need to use 
> dynamic dns and port forwarding with my home router. I also avoid
> using my laptop as a server as much as possible.
> 
> I imagine that everyone will agree that running Freenet remotely, in
> my situation, is more ideal.
> 
> The major issue I have with running Freenet on a remote system is
> that any user on that system can root my Freenet account by pointing
> their web browser at the open port (on localhost). This is a serious
> problem.
> 
> Please add password authentication to the web interface. If crypto is
> a problem, then put the password in a plain text file and use strict 
> permissions on the file, because this is better than nothing.
> 
> I am not subscribed to this mailing list. Please CC me if you reply
> to this message.
> 
> Thank you

In the meantime, you could use iptables' owner module to do per-user or
per-group filtering.
_______________________________________________
Support mailing list
[email protected]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-request-RdDMkVZAZeuJnvDnx1genB2eb7JE58TQ@public.gmane.org?subject=unsubscribe