search for: user1a

.../home/user2/html Using vsftp, I have set the default to chroot a user to their home directory. So user1 ftping in whill go right to his directory and not be able to go higher. My problem is adding a second user to be able to access the directory via ftp. In other words, user1 has a partner named user1a. I tried adding user1a in user1 group and not in user1 group...netiher worked. I tried adding user1a with no home directory and tried making their home directoy /home/user1 In all cases, ftp says 'cannot move to /home/user1' when trying to access with user1a. I am to the point it is ti...

...user from the command line, as a non-root user. I know I can use 'smbpasswd', 'samba-tool user setpassword', or 'samba-tool user password', but these all seem to require root privileges. When I run them as root, they work, but when I run them as non-root user, I get: user1a at test-s4ad:~$ smbpasswd -U dago Old SMB password: New SMB password: Retype new SMB password: SAMR connection to machine NT_STATUS_ACCESS_DENIED failed. Error was 127.0.0.1, but LANMAN password changes are disabled or user1a at test-s4ad:~$ samba-tool user password -U dago Password f...

...gt; non-root user. > > I know I can use 'smbpasswd', 'samba-tool user setpassword', or > 'samba-tool user password', but these all seem to require root > privileges. When I run them as root, they work, but when I run them as > non-root user, I get: > > user1a at test-s4ad:~$ smbpasswd -U dago > Old SMB password: > New SMB password: > Retype new SMB password: > SAMR connection to machine NT_STATUS_ACCESS_DENIED failed. Error was > 127.0.0.1, but LANMAN password changes are disabled > > or > > user1a at test-s4ad:~$ sa...

...ialized nss_winbind group backend [ 932]: nss_winbind: _nss_winbind_setgrent_solwrap [ 932]: setgrent ... [ 932]: getgrent group.gr_name = Domain Users group.gr_passwd = x group.gr_gid = 10000 group.gr_mem = 0x25afc (user1a) 0x25b00 (user2a) [ 932]: nss_winbind: _nss_winbind_getgrent_solwrap: Returning group: Domain Users ... [ 932]: getgrent group.gr_name = globalgrp group.gr_passwd = x group.gr_gid = 10328...

Dear all, i have a problem with sssd in conjunction with ldap on a centos 7 x86_64 box. ldap works fine. I can login there as an usual user registred in ldap. I want now restrict the access with ldap's host attribute. This is beeing ignored. Still every ldap user can login, no matter what the host attribute says. I googled around and only found that sssd.conf need two lines: access_provider

...** shadowFlag: 0 shadowInactive: -1 gidNumber: *** shadowMin: -1 shadowMax: 999999 homeDirectory: /home/USER1 sn: USER1 mail: USER1 at my.doma.in mailHost: lmtp:unix:/var/lib/imap/socket/lmtp shadowWarning: 7 sambaSID: ***************************************** shadowExpire: -1 mailAlternateAddress: USER1a cn: surname lastname gecos: surname lastname loginShell: /bin/bash host: another-node What information is still missing? Any hint is welcome. Thank you in advance, ulrich