New answers tagged

1

Well, if you want to disable the default ubuntu user (a reasonable thing to do), you will need to add another user to the system that you will use to connect via SSH. Needless to say, this second user should have sudo privileges.


-1

switch>enable switch# config t Switch(config)#username gozulin privilege 15 password yourpassword Switch(config)end switch# wr Note#1: you don't need to enter 0 or 7 --- try that. Privilege 15 will give you all the privilege as for a root user. Note#2: It is always good to not overwrite the previous credential until you know for sure your new user ...


0

Regarding the second change issue... What is the domain policy setting for "minimum password age"? If that is a non zero number, you need to wait that time period before another change is allowed. You can find that info with powershell command Get-ADDefaultDomainPasswordPolicy or by looking in the Default Domain Policy at the path: Windows Settings/Security ...


0

Password complexity in a Windows environment means you must to use 3 types of different characters out of 4 groups: uppercase characters [A – Z] lowercase characters [a – z ] digits [0 – 9] special characters [!@#$%^&*()-=_+] This policy may be enabled or disabled. I see that in your domain is enabled. Users have to apply above ...


1

The userAccountControl bit for controlling "Password never expires" is 0x10000 (65536 in decimal). The following LDAP filter will return all users with the option set: (&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=65536)) With an adsisearcher that would become something like: $Searcher = ...


1

Recent versions of OpenSSH have made this much easier to accomplish! In /etc/ssh/sshd_config simply add the following: AuthenticationMethods "publickey,password" "publickey,keyboard-interactive" If you wish to allow a specific IP address (e.g. 192.168.10.10) to be able to log in with the OpenSSH default methods, but require every other IP address to use ...


6

You can visualize the failed user names after you turn up the verbosity of the log in sshd_config¹, but there is no way to see the failed passwords as this could be a potential security issue and would violates the privacy of users (for example you could mistype your password and it would be leaked into some log file). All the passwords are handled as ...


2

The problem is that AD now sees the VM as the Official [TM] version of your company-issued laptop. I'm afraid you're going to have to 'fess up to someone who has the privileges to click "reset" on the domain side, then pop the laptop out of and back into AD. This will break the VM on your home desktop.



Top 50 recent answers are included