I used the above command to add a user "john". How do I delete and block john.
On many systems:
If you want to remove the homedir also, use the -r flag.
Alternativly, to just block access without removing the account, edit /etc/shadow and change the password to *LK* to lock the account.
If userdel isn't available, you can manually remove the entires from /etc/passwd and /etc/shadow. Then just check /etc/group and remove their name, and delete their home directory.
hi, i am on aix. i used smitty to remove a user..
but then found that its directory still exists....
so i have to remove the directory manually...
am i doing it the right way? (2 Replies)
Hi,
The Setup is like this. I'm connecting to Unix machine from my local machine. After connecting to Unix M/c, i need to connect FTP server. Am successful in connecting to FTP server, but am not able to download the file from the ftp server to my local machine. I have different user id's and... (1 Reply)
Hello! Can anyone please assist:
Question:
On Linux Server I have created two users John and Matt. I want to give both the users the ability to run 'more' and 'tail -f' commands on the log file in the directory /var/log/test.log. I do not want to give them SU rights.
Can any one please... (6 Replies)
Hi,
We have a requirement to do passwordless entry from one user to a different user on the same AIX server using ssh keys.
Can some one help me with this?
Thanks in advance,
Panditt (3 Replies)
Can someone help in writing some script through which I can transfer file (scp) from root user in abc server to crt user in hfg server and can give the crt user password in script itself so that it doesn't prompt me every time for password (4 Replies)
Oracle Linux 6.6
grid user's secondary groups are asmadmin,asmdba,asmoper and dba
# id -a grid
uid=638(grid) gid=2000(oinstall) groups=2000(oinstall),2100(asmadmin),2200(dba),2300(asmdba),2301(asmoper)
I want to remove dba as the secondary group for grid and keep the remaining ones.
ie. I... (5 Replies)
Based on the NIS migration tests I did and another question I posted earlier on.
https://www.unix.com/solaris/272021-solaris-8-md5-encryption-support.html
I tried to downgrade NIS linux encryption to DES to support solaris connection.
So I modified /etc/pam.d/system-auth as below,
password... (0 Replies)
Hello,
i configured rhel linux 6 with AD directory to authorize windows users to connect on the system and it works.
i have accounts with high privileges (oracle for example) if an account is created on the AD server i would to block him.
I looked for how to do, for the moment all the... (3 Replies)
I have googled this and found many solutions, but none of them are working for me. I am in a korn shell, most others reference bsh, maybe that is the issue? Anyway, all I am trying to do is use a variable I have declared in my main script in a remote shell I am running through ssh.
So I have a... (8 Replies)
Discussion started by: DJR
8 Replies
LEARN ABOUT DEBIAN
doveadm-auth
DOVEADM-AUTH(1) Dovecot DOVEADM-AUTH(1)NAME
doveadm-auth - Test authentication for a user
SYNOPSIS
doveadm [-Dv] auth [-a auth_socket_path] [-x auth_info] user [password]
DESCRIPTION
The auth command can be used to test the authentication for the given user.
OPTIONS
Global doveadm(1) options:
-D Enables verbosity and debug messages.
-v Enables verbosity, including progress counter.
Command specific options:
-a auth_socket_path
This option is used to specify an absolute path to an alternative UNIX domain socket.
By default doveadm(1) will use the socket /var/run/dovecot/auth-client. The socket may be located in another directory, when the
default base_dir setting was overridden in /etc/dovecot/dovecot.conf.
-x auth_info
auth_info specifies additional conditions for the auth command. The auth_info option string has to be given as name=value pair.
For multiple conditions the -x option could be supplied multiple times.
Possible names for the auth_info are:
service
The service for which the authentication lookup should be tested. The value may be the name of a service, commonly used with
Dovecot. For example: imap, pop3 or smtp.
lip The local IP address (server) for the test.
rip The remote IP address (client) for the test.
lport The local port, e.g. 143
rport The remote port, e.g. 24567
ARGUMENTS
user The user's login name. Depending on the configuration, the login name may be for example jane or john@example.com.
password
Optionally the user's password. doveadm(1) will prompt for the password, if none was given.
EXAMPLE
This example demonstrates an imap authentication test for user john, assuming the user is connected from the host with the IP address
192.0.2.143.
doveadm auth -x service=imap -x rip=192.0.2.143 john johns_password
passdb: john auth succeeded
extra fields:
user=john
REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail-
able at: http://dovecot.org/bugreport.html
SEE ALSO doveadm(1), doveconf(1)Dovecot v2.1 2010-06-09 DOVEADM-AUTH(1)