Tag Info

New answers tagged

0

Check Security log in Windows Event Log. All logon events are registered here. Use find (or filter) to search for specified accounts events.


1

Incomplete advice. The answer is: As previously mentioned clear all entries in credentials manager, close any open share explorer windows and/or all applications utilizing the share. THEN Open services manager. Find the "Workstation" service and restart it.


-1

you are in o=Mindlandcollege ConsoleOne is deprecated at this point for any function and the export tool was never all that, iManager is the current tool from Novell. That being said, I would use Apache Directory Studio as it talks directly to the LDAP and has a more easily understandable toolset. Save consoleone and imanager for actually manipulating the ...


2

You're thinking about this from the wrong direction. Certificate authentication is a replacement or enhancement for username/password or AD authentication. When a user connects to your site and presents a certificate, then the user is logged in as the user that certificate is mapped to. So if you have 3 users you want to be able to use your site, either ...


8

As I can see, your expectation is user can't send behalf other user because you put reject_sender_login_mismatch in smtpd_sender_restrictions. Yes, that should work. Unfortunately, you put reject_sender_login_mismatch after permit_sasl_authenticated. Based on postfix logic, if your client successfully login via SASL, it won't checked against ...


1

< bot >Convert answer as comment in answer section< /bot > Nginx support multiple root certificates. Just put multiple root CA certificates into a file specified in the ssl_client_certificate directive. Note the docs explicitly say "certificates"(plural). This is a consideration why nginx doesn't support ssl_client_certificate in a directory (as ...


0

I use bogus credentials to really disable access. net use * /d /y net use "\\10.0.0.5\c$" "badpassword" /user:"baduser" net use * /d /y that seems to overwrite the old credentials and forces explorer to attempt to use the new bad credentials.


1

Even better... http://blogs.technet.com/b/cloudpfe/archive/2014/10/26/using-time-based-one-time-passwords-for-multi-factor-authentication-in-ad-fs-3-0.aspx This lists the entire TOTP solution for AD FS.


0

< bot >convert self-answerer question to CW< /bot > I was finally able to get it working thanks to Pothi. Here is my final config nginx.conf: server { listen 80; server_name _; proxy_set_header Authorization ""; #$http_authorization; proxy_pass_header Authorization; auth_basic "Restricted"; ...


1

Without extra effort nothing is preventing a (dubiously determined) attacker from initiating a man-in-the-middle attack during the first key exchange and all subsequent connections. This is the same risk inherent in any key exchange over the internet. You can verify the fingerprints of both the master and the minion. On master: sudo salt-key -F On minion: ...


2

It's quite old question, but someone might find it help full. First of all: change sshd_config and use default option: UsePAM yes. Logging on Centos/RedHat is through PAM to SSSD, and than Kerberos itself. The same is with SSH, it first looks on PAM config, and contact SSSD, than Kerberos. Because of Kerberos verifing domain, I would recommend using ...


1

After many tries I've found the solution. The problem was in incorrect VirtualHost configuration for git-http-backend. Here's my working config: <IfModule mod_ssl.c> <VirtualHost _default_:443> DocumentRoot /git/myrepos SetEnv GIT_PROJECT_ROOT /git/myrepos SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /myrepos/ ...


0

restorecon -r -vv /home/user/.ssh Will fix problem. Found here


0

sshd_config is for the server so that's where you are saying look in this file for the public key to make sure it matches a private key your client is sending. Public keys on server go in ~/.ssh/authorized_keys Then the client sends its private key in ~/.ssh/id_rsa and the server matches them up and allows you in The client side is setup here ...


0

Your id_rsa file contains information about both your private and public key. It is only offering the public part of the key. I believe that type 1 or type 2 designates whether it is an RSA or DSA key.


2

The port number shown is the ephemeral client-side port number, corresponding to the source port as seen by the SSH server. Server-side, all ssh connections are to port 22. Here's me sshing into my colo'ed server, and confirming the port listed in the relevant syslog file: odessa% ssh www.teaparty.net [...] [me@lory ~]$ tail -2 /var/log/facility/authpriv ...


1

Set auth_username_format to %Lu.%Ld It will result username.domain in lowercase. See this wiki for complete variables from dovecot


0

The last entry on this thread talks about using a specific tool to determine the user in question for this error (Login ID is unique since boot, but after a reboot changes so you need to see what account is connected to this request) and validate whether they should have permissions to do what they are attmepting: ...


0

You can use <Location /your-wp-page > directive in apache (httpd.conf) So you can use something similar in nginx.


0

Reading this documentation and executing the following commands: keystone service-create --name=keystone --type=identity --description="Identity Service" && \ keystone service-list keystone endpoint-create \ --region RegionOne \ --service-id=<service-list-id> \ --publicurl=http://<ip>:5000/v2.0 \ ...


0

Since Apache2 starts as root and reads config file before dropping root. Assuming your current file config is owned by root and group is root, like so: -rw-r--r-- 1 root root 1.4K 2014-10-15 14:43 vhostconf You can just drop read/write/execute from the file to "other users": sudo chmod o-rwx /etc/apache2/sites-available/vhostconf You should end up with: ...


0

This may be pretty rudimentary, basic stuff, but I have missed the simple stuff too many times. Presuming your web-client is running inside Windows and is a web-client that understands Windows CAPI, you would want the user-certificate to reside in CAPI --> Current User --> Personal --> Certificates, and must have Extended Key Usage "clientAuth". In this ...



Top 50 recent answers are included