search for: authnticate

Displaying 6 results from an estimated 6 matches for "authnticate".

Did you mean: authenticate
Authentication Problem in Ruby and Rails
2006 May 05
2
Authentication Problem in Ruby and Rails
Hi to all! I am new to ROR!I hope i will get the help from this group! We configured the email setting in the environment.rb file for sending the email from my local system! but we are getting Authntication problems! How can I solve this problem Please give me the references Thanks and Regards, Kumar -- Posted via http://www.ruby-forum.com/.
sshd
2010 Jun 30
1
sshd
Hi Dont know if its possible, can't find any info on the net, but i wanted to stop my sshd server from returning authntication failed messages to the clients. Example, a person tries to login and the user or password is incorrect, i dont want the server to say 'Received disconnect from IP Too many authentication failures for user'. Just return nothing as if its not there. Is there a
netatalk & Sambas' winbind
2004 Jan 19
1
netatalk & Sambas' winbind
Hi, I've got a SuSE 9.0 running Samba 3.0.1 and Netatalk 1.6.3 Samba is a member server of a win2k domain, I'm using winbind to authnticate my users. Well, with the Windows users, everything is ok. But not with the Mac users I'd like to setup Netatalk to authenticate my Macs against the win2k domain as with Windows. Is this possible? I've sarched the web all around and couldn't find any info on the subject. Warm regar...
under some kind of attack
2017 Jul 20
3
under some kind of attack
Am 20.07.2017 um 12:28 schrieb mj: > I have concoted something that seems to work. And for the archives, this > is it: > >> failregex = auth: Info: ldap\(.+,<HOST>,.+\): invalid credentials >> \(given password: .+ssword\) >> auth: Info: ldap\(.+,<HOST>,.+\): invalid credentials >> \(given password: 1qaz2wsx\) >> auth:
under some kind of attack
2017 Jul 20
0
under some kind of attack
...d NOT want to have them the usual three opportunities to try. In fact: this is a bit similar to your iptables solution, but that only works for non-ssl/non-tls connections. Your iptables solution makes sure that thy cannot authenticate *at all*, while the above solution makes sure they can only authnticate *once*. MJ
under some kind of attack
2017 Jul 20
1
under some kind of attack
...usual three opportunities to try. > > In fact: this is a bit similar to your iptables solution, but that only > works for non-ssl/non-tls connections. > > Your iptables solution makes sure that thy cannot authenticate *at all*, > while the above solution makes sure they can only authnticate *once*. > > MJ Ok I understand, not a bad idea, report how it works for you Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patric...