Re: [Cooker] Mozilla FR

2002-09-11 Thread Ian Davey

On Wed, 2002-09-11 at 11:01, Frederic Crozat wrote:
  Yes I think it's strange to propose only Mozilla 1.1 in mdk 9.0 because
  it's a unstable release of Mozilla. Mozilla 1.0 is the last stable
  release.
 
 Really ? We did you saw Mozilla 1.1 is supposed to be an unstable
 release ??
 

http://www.mozilla.org/releases/stable.html

The 1.X series are the development releases with six week alpha/beta
periods, the 1.0X branch is for upgrades to the stable release.

That said, as a desktop distro it makes more sense for Mandrake to
follow the 1.X branch, as the stable branch really means having a stable
APIs for embedders (AOL on MacOS) and repackagers (i.e. Netscape 7).
It's designed to guarantee minimum changes and is therefore less likely
to break things API-wise. 

I also assume Galeon etc. are following the 1.X releases, so it makes
sense for Mandrake to package the same. 

ian.





Re: [Cooker] feature request - multiple X sessions through kdm/gdm

2002-08-19 Thread Ian Davey

On Mon, 2002-08-19 at 22:35, SI Reasoning wrote:
 I have not had a chance to play around with the 9betas so excuse me if
 this is already in
 
 There is one feature of WinXP that I really like that they ripped from
 Linux but made it simpler to use...and that is the idea of multiple
 desktops for different users. It would be really nice if Mandrake would
 create a choice to login into a new desktop without having to logout of
 an existing one. It shouldn't be that hard to program I would think.
 Just add an option like in XP to switch users or logout and have the
 mandrake kdm/gdm automatically create a new X session if a new logon is
 intitiated. You could then create a unified menu entry that would list
 user accounts so that it would be easy to switch users from within a
 desktop. Have all reentry with the option of being password protected.

If you're running GDM you can do this through the existing Mandrake
menus:

Configuration - Boot and Init - New Login with GDM

ian.





Re: [Cooker] kppp messing up CHAP logins?

2002-08-12 Thread Ian Davey

On Mon, 2002-08-12 at 19:32, Crispin Boylan wrote:
 Hi
 i've tried to use kppp with BTOpenworld here in the uk (it uses CHAP 
 authentication) but no matter what I do, it won't connect.  However, my 
 other ISP Easynet which uses PAP for authentication connects perfectly 
 everytime.
 
 using just the normal pppd scripts works fine for both its only in kppp 
 that problems occur..incidently with Easynet CHAP and PAP is supported 
 and CHAP doesnt work for easynet in kppp either, whilst using pppd 
 scripts with it and chap work fine as well.
 

It works fine for me. I use kppp to connect to BTInternet, so don't
think it's a general issue.

ian.





Re: [Cooker] CGIs don't work (apache or apache2)

2002-08-01 Thread Ian Davey

On Thu, 2002-08-01 at 03:40, Todd Lyons wrote:
 Oden Eriksson wrote on Wed, Jul 31, 2002 at 11:08:30PM +0200 :
  
   What I'd like to see for Mandrake is it as quick and
   easy as possible for anybody to get it to do what they
   want it to do (obviously while being very sensitive to
   security issues).
  Yes..., it's a very sensible tightrope to walk, either usable and less 
  secure, or not, I don't know how to accomplish both, maybe someone else does?
 
 That's pretty easy.  The world's most secure preconfigured apache
 server:
 
 [root@fiji /var/www]# vdir -a www
 total 12
 drwxr-xr-x2 root root 4096 Jul 31 19:36 .
 drwx--   23 root root 4096 Jul 31 19:36 ..
 -rw-r--r--1 root root   63 Jul 31 19:36 index.html
 [root@fiji /var/www]# cat www/index.html
 META HTTP-EQUIV=Refresh CONTENT=0; URL=http://google.com;
 [root@fiji /var/www]# vdir cgi-bin
 total 0
 
 Useful?  No.  Secure?  Yes.

That's not secure. It relies on a browser obeying a redirect and it
doesn't stop someone requesting /cgi-bin/something or
/somethingelse.html. A much more secure default would be to bind Apache
to only listen to requests from the localhost (which is one of the steps
that Bastille does).

You'd then need to specifically open it up to listen to requests from
the internet. Whether that is what people installing Apache would want
is a different matter altogether. Though would encourage them to
actually look at httpd.conf before putting it on the internet.
 
ian.