TheSin wrote:
name:desc::shell:home
Why change the default order, name:pass:desc:home:shell? This leads to
unnecessary confusion. And group:pass:members.
I'll second Chris; Why a password field at all? All the users Fink
defines so far are non-login users that have '*' as password.
--
Martin
On Monday, August 11, 2003, at 07:36 AM, TheSin wrote:
I have started a new fink branch to auto add and remove users/groups.
I'd like to vote on the field style for this.
You are aware all fink installs need to have the same uids for the same
users, yes? (because we support combining binary a
this isn't a problem in the aproch I'm taking as I'm setting the
user/groups in the postinstall scripts.
On Tuesday, August 12, 2003, at 10:56 PM, Ben Hines wrote:
You are aware all fink installs need to have the same uids for the
same users, yes? (because we support combining binary and source
Sorry, i see your other messages now, I see you took the clue stick. :)
-Ben
On Tuesday, August 12, 2003, at 09:56 PM, Ben Hines wrote:
On Monday, August 11, 2003, at 07:36 AM, TheSin wrote:
I have started a new fink branch to auto add and remove users/groups.
I'd like to vote on the field
What happens if two packages specify the same user? Even if this is OK,
what happens if they give different info about that user?
-- Dave
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Po
I have started a new fink branch to auto add and remove users/groups.
I'd like to vote on the field style for this.
Type 1:
User: <<
Name: postfix
Desc: Postfix User
Pass: password
Shell: /usr/bin/false
Home: %p/var/mail
<<
Group: <<
Name: postfix
I still haven't looked at how debian handles this problem either, and I
agree that a default password in a public clear text file is a bad
idea, specially if the user needs a valid shell. That is why i figure
fink could build it's own pass but then there would be no way of
knowing the pass whi
Am I missing something?
I don't understand why you have a Pass field at all. Default passwords
are evil, and are an obvious route for attackers. Perhaps Pass should
be a flag to indicate that Fink should prompt the user for a password?
That's still rotten, IMHO, but infinitely better than
forgot to hit reply-all again.
Begin forwarded message:
From: TheSin <[EMAIL PROTECTED]>
Date: Monday, August 11, 2003 10:45:38 AM Canada/Mountain
To: "David R. Morrison" <[EMAIL PROTECTED]>
Subject: Re: [Fink-devel] new user branch
I haven't decided yet as for dif
TheSin said:
> but this is why I'm posting the list, I need ideas for this sort of
> thing, I have most of the major stuff worked out, like not needed a db
> for uids
I must have missed this-- how does this work? (or do I have to UTSL?)
> On Monday, August 11, 2003, at 11:40 AM, Chris Dolan wrote
10 matches
Mail list logo