`messagebus' with uid `556'
pwd_mkdb: olivares
gid is incorrect
pwd_mkdb: at line #25
pwd_mkdb: /etc/master.passwd: Inappropriate file type or format
pw: passwd file update: No such file or directory
*** Error code 74
Stop in /usr/ports/devel/dbus.
=== Installation of dbus-1.4.12_2 (devel/dbus
On Mon, 28 May 2012 08:44:46 -0500, Antonio Olivares wrote:
I have copied the file master.passwd.bak from /var/backups/ into /etc/
and it still does not work. I cannot get around this error.
You have to make sure /etc/passwd and /etc/master.passwd have
the same content (just that they differ
/passwd and /etc/master.passwd have
the same content (just that they differ in passwords and in
file permissions). The database files /etc/(s)pwd.db will be
created from those files by the pwd_mkdb command. This of
course requires root access (which I assume you have made
sure).
Is there a way
On Mon, 28 May 2012 11:51:23 -0500, Antonio Olivares wrote:
I have run the command as root user
# pwd_mkdb -d /etc/master.passwd
Looks wrong; the parameter -d is -d directory, explained
as Store databases into specified destination directory
instead of /etc.
The coorect command should
Looks wrong; the parameter -d is -d directory, explained
as Store databases into specified destination directory
instead of /etc.
The coorect command should be
# pwd_mkdb /etc/master.passwd
See man pwd_mkdb for details.
but it fails with a pam_auth() or I can't remember exact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/03/2010 05:41:10, Dan Nelson wrote:
In the last episode (Mar 10), Modulok said:
I need to migrate a passwd file from an old 6.2 server to a newer 8.0
server (different box). This is what I did:
copied the '/etc/master.passwd' from old
to a newer 8.0
server (different box). This is what I did:
copied the '/etc/master.passwd' from old server to '/etc/master.passwd'
on new server then ran:
pwd_mkdb /etc/master.passwd pwd_mkdb -p /etc/master.passwd
It seems to work, but is this correct? I'd hate to miss somethign before
I need to migrate a passwd file from an old 6.2 server to a newer 8.0
server (different box). This is what I did:
copied the '/etc/master.passwd' from old server to
'/etc/master.passwd' on new server
then ran:
pwd_mkdb /etc/master.passwd pwd_mkdb -p /etc/master.passwd
It seems to work
In the last episode (Mar 10), Modulok said:
I need to migrate a passwd file from an old 6.2 server to a newer 8.0
server (different box). This is what I did:
copied the '/etc/master.passwd' from old server to '/etc/master.passwd'
on new server then ran:
pwd_mkdb /etc/master.passwd
MD5 seems to be compromised by potential collision attacks. So I tried
to figure out how I can use another hash for security purposes when
hashing passwords for local users on a FreeBSD 7/8 box, like root or
local box administration. Looking at man login.conf reveals only three
possible hash
Hi All,
Somebody already modified scripts migrationtools
(http://www.padl.com/OSS/MigrationTools.html) to convert
master.passwd for ldap? Using scripts original (migrate_passwd.pl)
the conversion is wrong, as below
dn: uid=test,ou=People,dc=padl,dc=com
uid: test
cn: User by test
objectClass
João Carlos Mendes Luís [EMAIL PROTECTED] writes:
This question must be really dumb, but I cannot find its answer.
In a somewhat recently updated RELENG_6 FreeBSD, whenever I run the
program /usr/bin/passwd to change an users password, it encrypts the
password using DES. I have
Lowell Gilbert wrote:
João Carlos Mendes Luís [EMAIL PROTECTED] writes:
This question must be really dumb, but I cannot find its answer.
In a somewhat recently updated RELENG_6 FreeBSD, whenever I run the
program /usr/bin/passwd to change an users password, it encrypts the
password
On Friday 07 September 2007 03:28:48 João Carlos Mendes Luís wrote:
This question must be really dumb, but I cannot find its answer.
In a somewhat recently updated RELENG_6 FreeBSD, whenever I run the
program /usr/bin/passwd to change an users password, it encrypts the
password using
This question must be really dumb, but I cannot find its answer.
In a somewhat recently updated RELENG_6 FreeBSD, whenever I run the
program /usr/bin/passwd to change an users password, it encrypts the
password using DES. I have already configured /etc/login.conf for MD5,
but it still
Hi all,
I have two servers that I will be upgrading.
Will the passwords in 4.7 and 4.10 (in the master password file work in 6.1?
They all start with $1$
-Grant
___
freebsd-questions@freebsd.org mailing list
Grant Peel wrote:
Hi all,
I have two servers that I will be upgrading.
Will the passwords in 4.7 and 4.10 (in the master password file work in 6.1?
They all start with $1$
-Grant
Just run cap_mkdb /etc/master.passwd -- you'll have to once you upgrade
and it's a step that many times I even
for the webserver to do it, short of adding a bunch of users to
group shadow.
Unfortunately, mod_auth_pwcheck only seems to work nicely for Apache
1.3.
Has anyone done this sort of thing? I'd prefer to not use .htaccess
or any non-master.passwd auth mechanism.
Thanks,
-John
Hello,
after some weird disk accident I have only pwd.db and spwd.db from my
passwd files left. Passwd and master.passwd are missing. Couln't find them
in /lost+found too. The system is running, but I can not add new users, of
course (baybe only using pwd_mkdb -u ).
Is there any way how
On 9/11/06, Leo Mrafko [EMAIL PROTECTED] wrote:
Hello,
after some weird disk accident I have only pwd.db and spwd.db from my
passwd files left. Passwd and master.passwd are missing. Couln't find them
in /lost+found too. The system is running, but I can not add new users, of
course (baybe only
On Mon, 11 Sep 2006, michael johnson wrote:
On 9/11/06, Leo Mrafko [EMAIL PROTECTED] wrote:
Hello,
after some weird disk accident I have only pwd.db and spwd.db from my
passwd files left. Passwd and master.passwd are missing. Couln't find them
in /lost+found too. The system is running
On Sep 11, 2006, at 12:14 PM, Leo Mrafko wrote:
/var/backups contains a few files you may need.
Yeah, really, thanks, I found there some backup. But I still
wonder, if
there is a possibily to reconstruct master passwd back from .db files,
e.g. in case this backup is not up-to-date. I think
. in case this backup is not up-to-date. I think it should be
possible,
but I don't knw how..
You should be able to use pwd_mkdb -p; see the manpage.
Thanks, but sorry, this can only make passwd from master.passwd, AFAIK.
Leo
--
-Chuck
Hi!
All of a sudden, our ypwhich uses an unprivileged port when accessing
master.passwd, and of course, it does not get any results:
# ypmatch girgen master.passwd
ypmatch: can't match key girgen in map master.passwd.byname. reason: YP
server error
messages:
Nov 16 14:51:13 banan ypserv
PROTECTED] On Behalf Of Paul Hoffman
Sent: Friday, September 16, 2005 3:22 PM
To: freebsd-questions@FreeBSD.ORG
Subject: What does an * in master.passwd (not passwd) mean?
In 5.4 (and probably lots of other versions), the master.passwd file
is pre-seeded with lots of accounts such as daemon, operator
In 5.4 (and probably lots of other versions), the master.passwd file
is pre-seeded with lots of accounts such as daemon, operator, and so
on. The master.passwd file looks like:
daemon:*:1:1::0:0:Owner of many system processes:/root:/usr/sbin/nologin
operator:*:2:5::0:0:System :/:/usr/sbin
In the last episode (Sep 16), Paul Hoffman said:
In 5.4 (and probably lots of other versions), the master.passwd file
is pre-seeded with lots of accounts such as daemon, operator, and so
on. The master.passwd file looks like:
daemon:*:1:1::0:0:Owner of many system processes:/root:/usr/sbin
decided to use the same character for password not
shown in passwd and cannot ever log in in master.passwd should be,
well, punished somehow.
Thanks, this makes perfect sense. I'll craft up a short explanation
for the man page and send in a pr
John wrote:
Is it possible to restore/merge master.passwd across the revision boundary?
I just moved a bunch of user accounts from 4.9 system to 5.3 system. All
it took was pasting the relevant lines of old master.passwd into new
master.passwd using vipw. I didn't touch any system user accounts
a new passwd database from the old master.passwd.
Is it possible to restore/merge master.passwd across the revision boundary?
Do I have to do the same with /etc/groups?
thanks
--
John - [EMAIL PROTECTED] - http://www.reiteration.net/~jfm
For PGP public key finger [EMAIL PROTECTED] or see webpage
RJ Ive been playing with vipw trying to change passwords into * for a
RJ slightly higher level of security but ran into some very big problems. From
RJ reading through the FreeBSD handbook it seemed all i had to do was replace
RJ the encrypted password with *, which is what i did. I thought it
Both accounts are now active but i would like to remove the encrypted
password from master.passwd and replace it with a *. Is this possible with
vipw?
Thanks for your reply hugle
From: hugle [EMAIL PROTECTED]
Reply-To: hugle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: master.passwd
can't do that. You need the password hash in /etc/master.passwd
if you want people to be able to log in via the console. You should
have at least the root account and your own user account in the local
/etc/master.passwd file with valid passwords, or you can find yourself
in a whole heap of trouble
On Thu, 18 Dec 2003 11:44:14 +
Rhys John [EMAIL PROTECTED] probably wrote:
Both accounts are now active but i would like to remove the encrypted
password from master.passwd and replace it with a *. Is this possible with
vipw?
It doesn't matter what you use for editing your password
- Original Message -
From: Rhys John [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, December 18, 2003 5:44 AM
Subject: Re: master.passwd -- securing
Both accounts are now active but i would like to remove the encrypted
password from master.passwd and replace
Why do you want to do this? master.passwd already is inherantly secure.
The /etc/passwd file is what's used by most programs, and master.passwd
only for login purposes. You have to have the password stored somewhere
or there can be no authentication, unless you go with some sort of
hardware
36 matches
Mail list logo
