search for: vipw

> On 6/14/20 1:39 PM, Jay Hart wrote: >> You may need to modify /etc/shadow for consistency. >> >> I don't know what to do here. Need some guidance please. > > > Run "vipw -s" and make the same change to that file's record for ABCLast. > In /etc/passwd the directory was shown in plain text. So I just moved over in the line and changed /home/ABCLast to /home/ALast. Saved file, and exited. I don't see a directory name in /etc/shadow using 'vipw -...

Hello, could somebody to comment PR bin/51148? It is suggestion how to pass a value of cache size to pwd_mkdb when we are doing vipw or such. It can give a greate speed-up when master.passwd is really big (and sometimes it is). Appropriate cache size can make process 10 to 100 or more times faster. I gave the results of measurements in that problem report. Thanks in advance! SY, Alex

...ed to test diskusage/performance on zfs shared via nfs. I have installed nevada b64a. Historically uid/gid for user www has been 16/16 but when I try to add uid/gid www via smc with the value 16 I''m not allowed to do so. I''m coming from a FreeBSD backgroup. Here I alter uid using vipw and edit /etc/group afterwards. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare

...;ve seen show machine accounts in the passwd file that DO have a $ at the end of the machine name. So, $ or no $? The explanation on the How-To page is confusing, when it says "The problem is only in the program used to make the entry....Create a user without the "$". Then use vipw to edit the entry, adding the "$"". This is perplexing. Why would it make any difference whether you put in the $ with vipw or some other editor? And why does the heading of this section say ""$" Cannot Be Included in Machine Name?" I don't quite get w...

...ckground ch{fn,pass,sh} are utilities for changing user "finger" information, passwords, and login shell, respectively. The yp* variants perform the analogous changes on a NIS account. II. Problem Description A "format string vulnerability" was discovered in code used by the vipw utility during an internal FreeBSD code audit in July 2000. The vipw utility does not run with increased privileges and so it was believed at the time that it did not represent a security vulnerability. However it was not realised that this code is also shared with other utilities -- namely chfn, c...

I modified a users name on my system. From ABCLast, to ALast (used as an example). I modified the username, then the group name of the user (to align with the new name), and then I moved the users home directory from /home/ABCLast, to /home/ALast. Then using vipw, edited the home directory to use /home/ALast. When I got finished editing the passwd file, I got the following message: You have modified /etc/passwd. You may need to modify /etc/shadow for consistency. I don't know what to do here. Need some guidance please. lastly, did I miss anything he...

Hello, For some reason, I thought little about the "clear" command today.. Let's say a privileged user (root) logs on, edit a sensitive file (e.g, a file containing a password, running vipw, etc) .. then runs clear and logout. Then anyone can press the scroll-lock command, scroll back up and read the sensitive information.. Isn't "clear" ment to clear the backbuffer instead of printing a full screen of returns? If it does, I'm not sure how that would effect a use...

...:42 -0400 > From: Jay Hart <jhart at kevla.org> > >> On 6/14/20 1:39 PM, Jay Hart wrote: >>> You may need to modify /etc/shadow for consistency. >>> >>> I don't know what to do here. Need some guidance please. >> >> >> Run "vipw -s" and make the same change to that file's record for >> ABCLast. >> > > In /etc/passwd the directory was shown in plain text. So I just > moved over in the line and changed /home/ABCLast to /home/ALast. > Saved file, and exited. > > I don't see a dir...

Hi, freebsd-security. I have FreeBSD 5.3-STABLE. When I try to change user's password (via passwd) I recieve the following: passwd: entry inconsistent passwd: pam_chauthtok(): error in service module passwd: in pam_sm_chauthtok(): pw_copy() failed and password stays unchanged. There are no other errors in the authorization system at all. Contents of /etc/pam.d stayed unchanged (compared to

...I can see this user in Samba database using "pdbedit -Lv" command, but I can't logon by same user at every Win2k/XP workstations ( before I added those workstations to Samba domain successfully). By investigating I understand if I manually add this user in /etc/passwd ( I do it using vipw ) without setting password for user, then I can log on this user at WIn2k/XP. But why ? If I get positive reaction on ssh login ( this user can do it), and I see user by 'getent passwd', so Unix user account operate. (if I understand pam_ldap works right). If I see Samba user account '...

...computer account. use your global user account or local user account to access this server " I've already used root account to joining W2K client into my Samba Server and already put @wheel in domain admin group on my smb.conf too. Before that I've already added machine account using vipw into my passwd file. I hope there's anybody who could show me the missing part that I've forgot. Sorry if my English makes you confused. :) Regards, Dede Nurmansyah Here's my global part of smb.conf [global] workgroup = NIX netbios name = FreeBSD...

...security = user socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins support = yes workgroup = workgroup [public] path = /tmp guest ok = yes writeable = yes EOF I already made the changes on regedit in my WinXP box. this is how vipw looks like: gino:x:500:500::/home/gino:/bin/bash R32$:x:1200:300:workstation:/dev/null:/bin/false this vigr: gino:x:500: R32:x:1200: workstation::300:

I'm setting up a new install of samba 2.2.7a on FreeBSD 4.7 Here's a little run-through of what I have done. I added a machine account in /etc/group as follows: machines:*:201 I have added all of my machine accounts in to /etc/passwd as follows: sclepy$:*:201:201::0:0:Machine account for Sclepy:/dev/null:false lexus$:*:202:201::0:0:Machine

Hello all, I was using Samba 2.2.5 on a Linux machine as a PDC and it was working fine. But know I installed FreeBSD 4.7 in this machine and installed Samba 2.2.6pre2. It's still working as a PDC, but I can't add machine trust accounts because FreeBSD doesn't accept $ in its usernames. How should I do now? Thanks in advance.

Due to FreeBSD not allowing '$' in usernames, and because I have to add a machine account for each computer I add to my Samba domain, what can I do to try and accomplish the following? 1. Automate FreeBSD to allow me to add machines to a domain the same way Windows lets you do it from the workstation. 2. Add user accounts which incorporate '$' without having to create a

...he WinXP clients fails to join the domain with the error message: FROM WINXP: "The specified network password is not correct" FROM LOG: "[2003/01/29 23:27:03, 0] smbd/service.c:make_connection(563) Can't become connected user!" I run FreeBSD 4.7 and ive added the users by: vipw and smbpasswd -a USERNAME, and added the machine accounts the same way but with $ in the /etc/passwd and -m on smbpasswd. Any ideas? cheers safl

...d Quota support. Everything installs properly I created the groups machines:201, and admins:200. Added every user with the command "smbpasswd -a <username>" Also added every machine with this command "smbpasswd -a -m <machine_name>" Edited the password file via "vipw" And added the lines in it corresponding machine_name$:*:201:201::0:0:Machine account for a machine:/dev/null:false After that I created the following smb.conf file. -------------------------------------------------------- # Global parameters [global] workgroup = LEOPOLDNET ne...

Hi, I'm using Unix now for the last 2 years, so I'm learning everyday new things. Now I'm trying to configure Samba 2.2.5 (on Freebsd 4.4) so that w2k machines can logon to the domain. I added several users to smbpasswd (which are real users on the server. I would like to have "virtual users" which don't have a real account but that's an other problem) In several

...be no password, shell or home directory and the name is the NTws name with a '$' added at the end. : adduser ?g machines ?c NTMachine ?d /dev/null ?s /bin/false ?n bc-06$ Note : FreeBSD adduser does not like finding '$' in a user name, add the entry directly to /etc/passwd using vipw or similar. Add that name to smbpasswd (assumes you have a link to smbpasswd on path) : smbpasswd ?a ?m bc-06$

...a set of existing users, I'd add them in > > lowercase, then edit > > /etc/passwd > > /etc/shadow > > /etc/group > > /etc/gshadow > > and mv the /home/ directory to names you want (making sure > > everything matches). > > You might choose to use vipw and vigr to edit the above files as well. > > If you use local mail spools, you will need to rename /var/spool/mail/user > to /var/spool/mail/USER That's actually a different problem and a good reason by itself not to ever use uppercase in a user login name. Mailers on unix-like sy...