At 12:43 PM 5/3/2008, Matthew Toseland wrote:

<snip>

> > My node's been up continuously now for about three days, with ca. 20
> > peers, 25.1 KiB/sec average input rate, 27.1 KiB/sec average output
> > rate (of 50.0 KiB/sec) and 13.9 KiB/sec average payload output rate
> > (51%).  Is that reasonable?
>
>With 20 connected/backed off peers? It's a bit low, mine's been a bit low
>lately too though...

I've only provided the default 128M wrapper memory.  Could that be a 
factor?  Are there other config settings that might be limiting throughput?

> > However, in order to achieve that, I've had to stay logged on Win
> > NT.  If I log off while sleeping or away, which has been my practice,
> > Freenet appears to keep running (based on network activity) for a
> > while.  However, when I log on the next day, I find that the node
> > isn't connected to any peers, and also that it won't connect until I
> > stop and restart it.
>
>That is really bizarre. File a bug on https://bugs.freenetproject.org/ .
>Include wrapper.log and any ERRORs in logs/ ...

After checking the logs, it's clear what's going on.  Freenet runs 
just fine after I log off; indeed, it seems to be happier.  However, 
when I log on, various Freenet processes start timing out, and the 
node drops all connections after ca. 10 min.  This is a fairly old 
machine with a 2.8 GHz Pentium D and 2 Gb RAM, and it's pretty maxed 
out during logon.  It loads three apps (Firefox, Eudora and 
UltraEdit) and runs a few system and malware scans, and Freenet drops 
connections before the system frees up.

Although Freenet reports that it's trying to connect, I find that it 
hasn't after more than 2 hr.  But once I stop and restart in Win XP 
services manager, it connects immediately.

Is that behavior normal?

> > Freenet runs as user ".\freenet", and I get that y'all switched from
> > running as LocalSystem to improve security
><https://bugs.freenetproject.org/view.php?id=1231>.
>
>Yes.
>
> > Am I correct in
> > guessing that ".\freenet" is linked to my user account, and so the
> > Freenet service hangs after I log off?
>
>No, it's a separate user.
>
> > Could Freenet run safely as
> > LocalService or NetworkService?
>
>No idea. Probably. Would it be better?

I have no clue.  On my Win XP system now, Freenet is the only service 
running as a non-standard user.  Most services are running as 
LocalSystem, and the rest are running as LocalService or 
NetworkService.  I gather that LocalService and NetworkService have 
restricted permissions, apparently more-or-less comparable to default 
non-admin users.  But I've never needed to mess with that stuff, so I 
don't know it.  And it seems to be OK as is, so I won't mess with it.

<snip>

> > >Why not just restart [the node] each time? The only reason to recreate it
> > >on each startup is in case the datastore contains something 
> incriminating...
> >
> > Although I have no interest in seeing for myself, I gather that
> > Freenet contains truly awful stuff.  If that's so, it's quite likely
> > that "the datastore contains something incriminating".  Right?
>
>Yes, but it's encrypted, and you don't have the key. To find the key 
>you would
>have to go looking for such filth. This provides a reasonable degree of
>plausible deniability.
>
> > But
> > given that I'm running Freenet, I've obviously accepted that as a
> > necessary cost of freedom.  Also, I get that the datastore is
> > encrypted, and that I cannot be expected to know what's
> > there.  Conversely, the contents of my download folder are not
> > encrypted, but arguably I must have put them there intentionally.
>
>Right, that's the difference.
> >
> > Even so, I'm nervous.  Perhaps there are flogs with driveby
> > downloads.  I was thinking of running in nonpersistent mode as an
> > additional safeguard.  But I do appreciate how doing that would
> > partially defeat Freenet's data routing and retention logic.  Anyway,
> > I'm now thinking that running an encrypted virtual machine may be an
> > acceptable alternative.
>
>Possibly. If it's transient it would be recreated on startup; if it isn't, it
>would obviously be possible to investigate it if the computer was taken away.

For now, I've just created an AES-encrypted virtual disk to store downloads.

<snip>

>* PGP Signed by an unknown key
>* text/plain body
>* Unknown Key
>* 0xE43DA450

=
Jim Cook <jimcook at panix.com> 



Reply via email to