On Wednesday 30 April 2008 00:27, Jim Cook wrote: > At 06:18 AM 4/29/2008, Matthew Toseland wrote: > > >* PGP Signed by an unknown key > > > >On Tuesday 29 April 2008 03:44, Jim Cook wrote: > > > Thank you again, Matthew (and Volodya) for your patience with my > > > naive questions. Regarding the Firefox issue, I've found a Win BAT > > > file <http://www.mouserunner.com/FF_Tips_Multiple_Fx.html> that > > > facilitates running multiple instances with different profiles. > > > >Running multiple instances with different profiles is trivial, the problem is > >that if you don't want unpleasant surprises you have to change the link the > >user normally launches FF from to include -no-remote. Which is not something > >we really want to do... > > In retrospect, it's trivial. And I get why you've included a freenet > Firefox profile and made it difficult to edit.
You mean in that we disable the config related menu items? > However, given the > default "Don't ask at startup" setting in Firefox's profile manager, > and the fact that I'd never run multiple profiles, I was blindsided, > and thought that Freenet had trashed my Firefox setup. Yeah, Firefox is a problem. Not using it is a worse problem. Hopefully we can find a better solution... > Now I know to > create Firefox shortcuts for my normal and freenet profiles with > targets of the form "<path to firefox.exe>" -P <profile name> > -no-remote. What's the downside of doing that during Freenet > installation? Or, if that's hard to implement, it'd be great to > include an explanation of how to do that in the readme or FAQ. It is difficult to implement. It is also unnecessary if you do what you're told! We open a browser window with a page explaining that it's a really bad idea to close this page before closing the browser running Freenet ... if you close it anyway, Bad Things happen - namely your firefox profile default gets reset. > > > > I've had a node up on a Win NT box for ca. 24 hours in promiscuous > > > mode. It's connected to ca. 20 nodes, and is slow but > > > acceptably-responsive. When I'm not browsing, input and output rates > > > are 16.1 KiB/sec and 18.6 KiB/sec respectively. Although output > > > tends to mirror input, there are frequent output spikes that seem to > > > originate from my node. In other words, my node seems to be working. > > > > > > I haven't seen anything (in the security links that you've posted, or > > > elsewhere) about gaining admin access to other nodes via Freenet. I > > > can't imagine that y'all haven't considered this in coding > > > Freenet. So I'm being unreasonably paranoid, right? Of course, > > > there's always the risk of downloading malware (or getting it from my ISP > >=-O). > > > >We may have exploitable bugs, but on that level, I doubt it. Java isn't > >subject to buffer overflows or heap corruption. > > That's very good to know. Even so, I'm still nervous about running > Freenet on a machine that I use for work. And that's why I'm > planning to run it in a virtual machine in nonpersistent mode. > > > > Yesterday, I also had a node up for ca. 12 hours on Ubuntu 7.10 in > > > VMware Player. Before I trashed it and went to sleep, it was > > > connected to ca. 15 nodes, and seemed happy. However, although I > > > added this node and my Win NT node to each other as trusted peers, > > > they never connected. Is that a consequence of running in > > > promiscuous mode? How do I tell them to connect? > > > >They're on the same LAN. There are options you need to set to make that work. > > OK, I get that (and from Volodya's reply). It was just an experiment > to learn adding friends. I'm about ready to start enrolling real friends. > > > > I have a relatively underutilized Win SBS 2003 server, and I'm > > > thinking of setting up a node in Ubuntu/VMware via a dedicated > > > physical NIC. And I'm thinking of running in nonpersistent mode, so > > > that the node and all traces of its activity are lost when I shut it > > > down. Would that be problematic for Freenet, if the node were up for > > > at least a few weeks per instance? > > > >Not if it was online for a reasonable time, although obviously it would be > >better for the network if it was just up. > > Would it be better for the network if I paused it as a snapshot > whenever I needed to reboot? I don't reboot often, just as part of > installing updates or when messing with hardware. Why not just restart it each time? The only reason to recreate it on each startup is in case the datastore contains something incriminating... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20080430/b1db6526/attachment.pgp>
