New answers tagged authentication
From your description it seems that the problem isn't with the LDAP server as other servers and machines were able to authenticate without problem. My thoughts were to look at /etc/pam.d/common-auth and /etc/pam.d/common-account to have OpenSuSE read from those files for authentication.
This will fix it (keep in mind I am using Apache 2.4): Require user dorian
There is another way of thinking on this matter: Restrict ssh access to specific groups. Edit /etc/ssh/sshd_config Add the line AllowGroups sshusers or AllowGroups your_user_primary_group In case of AllowGroups sshusers create this administrative group: groupadd -r sshusers Add ssh allowed users to this group: usermod -aG sshusers username Reload sshd ...
EAP-TLS is seen as the superior authentication choice for PPTP. However, it requires implementation of a public-key infrastructure for both client and server certificates. As such it is not a viable authentication option for many remote access installations. In the Microsoft implementation, the tunneled PPP traffic can be authenticated with PAP, CHAP, ...
To avoid showing the password on the command where other users can see it with ps, you should not pass the password in the command. It's why many utilities don't support passwords as command line arguments. Instead store your password in a ~/.netrc file and pass the -n option to curl. For the details of file syntax, I let you see the man of curl.
Top 50 recent answers are included