Re: [freenet-dev] More Micro$oft insecure crap

2003-02-12 Thread Mark J Roberts
Mark J Roberts: > One should also disable HTTP inserts, which are another way to > divulge compromising information. > > httpInserts=false > > (Note that I've just checked in support for this. Feedback and fixes > are obviously welcome.) I've also implemented a companion "fcpInserts" optio

Re: [freenet-dev] More Micro$oft insecure crap

2003-02-12 Thread Mark J Roberts
Will Glynn: > ... just tell them if they want to be secure that they shouldn't browse > Freenet with anything other than 'less' if they want to remain anonymous. Linux supports per-user firewall rules; these are trivially employed to create a sandbox from which one may access freenet-downloaded co

RE: [freenet-dev] More Micro$oft insecure crap

2003-02-12 Thread Will Glynn
> > I don't know if this has been brought up before, but the windows media > > files (*.wm* such as *.wma *.wmv) allow a URL to be automatically > > accessed by the media file. > Its just windows media files that I know of. Don't forget about Real WhateverItIsCurrently™. At least as of a year or

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Greg Wooledge
Travis Bemann (tabemann at wisc.edu) wrote: > I know it will run on practically any UNIX machine with X Windows > (well, at least some implementation of X11R6, but that's practically > everyone using X Windows today). I'd mention our HP-UX 10.20 systems at work, which run X11R5, but that would be

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Matthew Toseland
On Mon, Sep 09, 2002 at 01:06:11PM -0500, Travis Bemann wrote: > On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > > >From Travis Bemann > > > > > > >It would be more appropriate to do so with something like gra

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Greg Wooledge
Travis Bemann ([EMAIL PROTECTED]) wrote: > I know it will run on practically any UNIX machine with X Windows > (well, at least some implementation of X11R6, but that's practically > everyone using X Windows today). I'd mention our HP-UX 10.20 systems at work, which run X11R5, but that would be a

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 07:34:56PM +0100, Matthew Toseland wrote: > On Mon, Sep 09, 2002 at 01:06:11PM -0500, Travis Bemann wrote: > > On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > > > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > > > >From Travis Bemann >

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > >From Travis Bemann > > > > >It would be more appropriate to do so with something like graphical > > >Links; Mozilla is wayyy to bloated a program to start with...

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > >From Travis Bemann > > >It would be more appropriate to do so with something like graphical > >Links; Mozilla is wayyy to bloated a program to start with... > > how is graphical links portability wise? I know it will run on pra

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 07:34:56PM +0100, Matthew Toseland wrote: > On Mon, Sep 09, 2002 at 01:06:11PM -0500, Travis Bemann wrote: > > On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > > > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > > > >From Travis Bemann <

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Matthew Toseland
On Mon, Sep 09, 2002 at 01:06:11PM -0500, Travis Bemann wrote: > On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > > >From Travis Bemann <[EMAIL PROTECTED]> > > > > > > >It would be more appropriate to do so wit

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 12:41:14PM -0500, Travis Bemann wrote: > On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > > >From Travis Bemann <[EMAIL PROTECTED]> > > > > >It would be more appropriate to do so with something like graphical > > >Links; Mozilla is wayyy to bloated a prog

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Travis Bemann
On Mon, Sep 09, 2002 at 03:04:14AM -0400, Benjamin Coates wrote: > >From Travis Bemann <[EMAIL PROTECTED]> > > >It would be more appropriate to do so with something like graphical > >Links; Mozilla is wayyy to bloated a program to start with... > > how is graphical links portability wise? I kno

[freenet-dev] More Micro$oft insecure crap

2002-09-09 Thread Benjamin Coates
>From Travis Bemann >It would be more appropriate to do so with something like graphical >Links; Mozilla is wayyy to bloated a program to start with... how is graphical links portability wise? -- Benjamin Coates ___ devl mailing list devl at freenet

RE: [freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Benjamin Coates
>From Travis Bemann <[EMAIL PROTECTED]> >It would be more appropriate to do so with something like graphical >Links; Mozilla is wayyy to bloated a program to start with... how is graphical links portability wise? -- Benjamin Coates ___ devl mailing

[freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Timm Murray
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If we wanted to go that far, we wouldn't need FProxy in the first place. FProxy is there because it makes the browser take care of all the messy GUI stuff. It kinda goes along with the idea of making a web browser a *platform*, not just a way of d

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Timm Murray
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If we wanted to go that far, we wouldn't need FProxy in the first place. FProxy is there because it makes the browser take care of all the messy GUI stuff. It kinda goes along with the idea of making a web browser a *platform*, not just a way of

[freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Travis Bemann
On Sun, Sep 08, 2002 at 03:37:33PM -0500, Eric Thacker wrote: > Heres another idea.. What about a freenet browser? Why not just hack > up the mozilla code and release a browser that runs on every OS, works > with fproxy, and solves the IE/Media URL problems. This way there would > be a browser t

[freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Robert Bihlmeyer
eric at caffrey.net writes: > Its just windows media files that I know of. MPEG files are safe unless > its really a windows media file renamed to a .mpg extention. Well mpeg is a quite flexible format, you can stuff a lot in there. If winamp decided to interpret the content of a special chunk a

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Travis Bemann
On Sun, Sep 08, 2002 at 03:37:33PM -0500, Eric Thacker wrote: > Heres another idea.. What about a freenet browser? Why not just hack > up the mozilla code and release a browser that runs on every OS, works > with fproxy, and solves the IE/Media URL problems. This way there would > be a browser

[freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Eric Thacker
Heres another idea.. What about a freenet browser? Why not just hack up the mozilla code and release a browser that runs on every OS, works with fproxy, and solves the IE/Media URL problems. This way there would be a browser that definatly WORKS without the freenet developers having to figure ou

[freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread fish
On Sat, 7 Sep 2002 eric at caffrey.net wrote: > I don't know if this has been brought up before, but the windows media files > (*.wm* such as *.wma *.wmv) allow a URL to be automatically accessed by > the media file. For example, once a movie file starts rolling credits, > the people who encoded

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Eric Thacker
Heres another idea.. What about a freenet browser? Why not just hack up the mozilla code and release a browser that runs on every OS, works with fproxy, and solves the IE/Media URL problems. This way there would be a browser that definatly WORKS without the freenet developers having to figure o

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-08 Thread Robert Bihlmeyer
[EMAIL PROTECTED] writes: > Its just windows media files that I know of. MPEG files are safe unless > its really a windows media file renamed to a .mpg extention. Well mpeg is a quite flexible format, you can stuff a lot in there. If winamp decided to interpret the content of a special chunk as

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread fish
On Sat, 7 Sep 2002 [EMAIL PROTECTED] wrote: > I don't know if this has been brought up before, but the windows media files > (*.wm* such as *.wma *.wmv) allow a URL to be automatically accessed by > the media file. For example, once a movie file starts rolling credits, > the people who encoded

[freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread e...@caffrey.net
age -- >To: devl at freenetproject.org >From: Ed Onken >Subject: Re: [freenet-dev] More Micro$oft insecure crap >Reply-To: devl at freenetproject.org >Date: Sat, 07 Sep 2002 13:54:52 -0500 > > >I agree, but I would think the warning should explain how--just like you >

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread eric
age -- >To: [EMAIL PROTECTED] >From: Ed Onken <[EMAIL PROTECTED]> >Subject: Re: [freenet-dev] More Micro$oft insecure crap >Reply-To: [EMAIL PROTECTED] >Date: Sat, 07 Sep 2002 13:54:52 -0500 > > >I agree, but I would think the warning should explain how--just like yo

[freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread eric
I don't know if this has been brought up before, but the windows media files (*.wm* such as *.wma *.wmv) allow a URL to be automatically accessed by the media file. For example, once a movie file starts rolling credits, the people who encoded the file can have it open a browser and hit their webs

Re: [freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread Ed Onken
I agree, but I would think the warning should explain how--just like you explained it. I didn't know windows media files could do that until I read it here. I can't rememember for sure, but I thought I had an MPEG try to pull up a website when I played it. I don't know if that's possible (a

[freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread Ed Onken
I agree, but I would think the warning should explain how--just like you explained it. I didn't know windows media files could do that until I read it here. I can't rememember for sure, but I thought I had an MPEG try to pull up a website when I played it. I don't know if that's possible (a s

[freenet-dev] More Micro$oft insecure crap

2002-09-07 Thread e...@caffrey.net
I don't know if this has been brought up before, but the windows media files (*.wm* such as *.wma *.wmv) allow a URL to be automatically accessed by the media file. For example, once a movie file starts rolling credits, the people who encoded the file can have it open a browser and hit their websi