10 More Discussions You Might Find Interesting
1. Solaris
Have an issue with a user or root changing the user's passwd.
We run the passwd command and a complex passwd is entered a message is displayed,
"passwd is based on a dictionary word."
We do have a dictionary file and I know for a fact the complex passwd is not in the list. This happens on a... (3 Replies)
Discussion started by: solizkewl
3 Replies
2. Solaris
bash-3.00# passwd sami
New Password:
Re-enter new Password:
Dec 14 00:07:43 hack passwd: passwdutil: crypt_gensalt Invalid argument
passwd: Unexpected failure. Password database unchanged.
Permission denied
i got this error while i am change the user(sami) passwd. (3 Replies)
Discussion started by: samiulla
3 Replies
3. Solaris
Hi
Administering Solaris Systems - Solaris 10 mostly.
If I change the /etc/default/passwd settings - E.G. to increase minimum passwd length, then what happens to existing users with passwords shorter than this. presumably they are not affected until next time they want to change password.
... (4 Replies)
Discussion started by: Mudshark
4 Replies
4. Shell Programming and Scripting
Can anybody please help me on how to code for the below requirement:
I need to write a shell script (on different unix server) to copy files from multiple folders (ex. BRN-000001) from one windows server (\\boldls-mwe-dev4)to a different windows server(\\rrwin-ewhd04.ecomad.int). This shell... (4 Replies)
Discussion started by: SravsJaya
4 Replies
5. Shell Programming and Scripting
Hi Expert,
I have environment where password is locally managed, not NIS, not LDAP, not Centrally managed.
In order to access to this environment I have to use Jump Box, and only from jumpbox I can login to every host. I can't login direct from inside one host within that environment to... (1 Reply)
Discussion started by: regmaster
1 Replies
6. HP-UX
My goal is to protect the /etc/passwd from unauthorized viewing. I wish ti change the permissions of the file to :
-r--r----- 1 root bin
so only root or accounts of the "bin" group could query this sensitive file. All our other processes have been ajusted to not need any info from... (16 Replies)
Discussion started by: MartinGravel
16 Replies
7. UNIX for Dummies Questions & Answers
My situation is that we have production unix scripts that ftp files over to a windows server. I'm not sure if its a 2000 or 2003 server as I dont work on server, more on the unix side. It turns out that they are changing servers on the network. So they are migrating our data over from say Server 1... (1 Reply)
Discussion started by: NycUnxer
1 Replies
8. Solaris
Hello. I'm getting very odd behavior when I try to change a user's password in Solaris 8. The shell, where it used to ask for a new passwd and a confirmation, now asks FOUR times, with two success message.
This is what happens every time:
# passwd myusername
New Password: xxxxxxxx
New... (2 Replies)
Discussion started by: rockusa
2 Replies
9. UNIX for Dummies Questions & Answers
I booted up Sun V240 server with boot cdrom -s using the Sun Operating System CD. I now am at the # prompt and su - root . The system will not allow me to set password for root. Get following error:
# passwd
New Password: xxxxxxxx
Re-enter new Password: xxxxxxxx
passwd: Unexpected failure. ... (4 Replies)
Discussion started by: mayewil
4 Replies
10. Solaris
Now I face a problem in changing the NIS passwd,I have no idea,want you to help me!
Today I add some user in the NIS master server ,I "vi" /etc/passwd &/etc/shadow,add user account and password by hand(shadow----no password ,only eight ":").
when finsh,I login ,system told me to input a password... (3 Replies)
Discussion started by: dlsjm
3 Replies
SMBPASSWD(5) File Formats and Conventions SMBPASSWD(5)
NAME
smbpasswd - The Samba encrypted password file
SYNOPSIS
smbpasswd
DESCRIPTION
This tool is part of the samba(7) suite.
smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as
account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several
different formats in the past.
FILE FORMAT
The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix passwd(5) file. It is an ASCII file containing one
line for each user. Each field within each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The
smbpasswd file contains the following information for each user:
name
This is the user name. It must be a name that already exists in the standard UNIX passwd file.
uid
This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then
Samba will refuse to recognize this smbpasswd file entry as being valid for a user.
Lanman Password Hash
This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known
string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash
is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical
(i.e. the password is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO
PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as disabled
and the user will not be able to log onto the Samba server.
WARNING !! Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this
password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and
must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with
read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other
access.
NT Password Hash
This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's
password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it.
This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much
higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical
(i.e. the password is not "salted" as the UNIX password is).
WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this
password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and
must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with
read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other
access.
Account Flags
This section contains flags that describe the attributes of the users account. This field is bracketed by '[' and ']' characters and is
always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following
characters:
o U - This means this is a "User" account, i.e. an ordinary user.
o N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored).
Note that this will only allow users to log on with no password if the
null passwords parameter is set in the smb.conf(5) config file.
o D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user.
o X - This means the password does not expire.
o W - This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow
Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC.
Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information
regarding the flags that are supported please refer to the man page for the pdbedit command.
Last Change Time
This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for "Last Change Time")
followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made.
All other colon separated fields are ignored at this time.
VERSION
This man page is correct for version 3 of the Samba suite.
SEE ALSO
smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open
Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to
DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
Samba 4.0 06/17/2014 SMBPASSWD(5)
02-25-2013
Changing windows xp passwd doetn't change smbpasswd on server