New answers tagged

0

ldap_access_filter looks weird. Try without it.


0

I ended up answering my own question - this is possible. I found out that Duo offers a free trial, so I went ahead and set up an account to try to get it to work with my setup. In the end, I was able to have both Active Directory LDAP and Duo Security LDAP set up at the same time. The relevant part of the code is here: tunnel-group VPN_RA type remote-access ...


0

I managed to solve this doing this: <Directory "/path/to/maindirectory"> [... auth stuff ... ] </Directory> <Directory "/path/to/mysubdirectory"> Allow from All Satisfy Any </Directory> Do NOT use Locations, because they're made to be case sensitive and they do not act on actual folder access, but just over the URL. So, for ...


1

The server didn't accept the key your client provided. The client provided only "/Users/kosmos/.ssh/id_rsa_old", guessing that's not the key that's in your authorized_keys file on the remote server. Check the auth.log on the server, it should contain something helpful as to why. If the public key for that id_rsa_old is in your authorized_keys file on that ...


0

Disable anonymous authentication and enable Windows Authentication. The client computers and the server itself will both need to be joined to the same AD domain for this to work. You then grant each AD user read/execute permissions to the web root folder (NTFS folder permissions) - the authentication is then automatic - the users will either get a 403 ...


0

Jason, is it possible for you to change the c=simple/simple to c=relaxed\relaxed? I seen a lot of times where different DKIM Validators struggle with the whitespace folding. You say it's only failing with "Bulk", so that tells me you are sending this out through some SMTP Service, which makes me more inclined to believe the headers are being rewritten and ...


0

Check if /etc/apache2/portal.keytab is owned by the webserver user (www-data on debian systems) and only readable by this user (-r--------). Check if you configured your browser for both the domain test.com and subdomains about:config network negotiate-auth.trusted-urls test.com, .test.com


1

Time have changed. There was a time when every system's administrator could be reached at the hostmaster address for that server. Connectivity once depended on knowing an administrator who would allow you access, and a routing map between systems was regularly published. Those days are long gone and security threats are wide-spread. The userid > 1000 ...


9

For that key, the organization don't have non-repudiation. IE, if someone does something abusive or destructive to that system using 'your' key, the admin can't point the blame at you for being solely responsible for it. Since the person that gave it to you also had the key. It probably isn't that bad for you, since it gives you a defense, but horrible ...


22

It is exactly as you say: The whole concept of public key authentication is that the private key should only be known to the owner, while the corresponding public key can be widely disseminated. The security of your authentication depends on the security of the private key, not of the security of the public key. The fact that somebody else provides you ...


0

For binding as uid=f.lastname,cn=domain.bg to work with CommuniGate that record should contain the userPassword attribute. The LDAP Central Directory in CommuniGate can be configured to copy account passwords to the directory records. Another option is to enable the LDAP Direct Provisioning option in CommuniGate: it this case operations that use DNs ...



Top 50 recent answers are included