similar to: FW: problem in Authentication.

Hi, Actually I'm installing Documentum on Linux Debian. Few from the steps: 1. Obtain the GNU SMB library source code. This is available at Samba sites on the Web. 2. Build the GNU SMB library. 3. Copy the smbvalid.a library from the /smbval directory to the $DM_HOME/install/ external_apps/checkpass directory. 4. Copy the valid.h file from the /include directory to the $DM_HOME/

http://bugzilla.mindrot.org/show_bug.cgi?id=974 Summary: Enhancement : Record Badlogins for all supported Authentication methods Product: Portable OpenSSH Version: 3.9p1 Platform: HPPA OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo:

On Mon, September 14, 2015 14:51, James B. Byrne wrote: > The Logwatch imapd service script distributed with CentOS-6 does not > generate anything when I run logwatch --service all on a cyrus-imapd > host. Is this expected behaviour? Is there a separate script for > cyrus-imapd or are their configuration options required to get the > existing script to work. > > I have found

Hi, I'm running a Centos 5.1 server that uses saslauthd to allow sendmail SMTP relaying for some clients. saslauthd is configured to use method "shadow" to lookup the username / password directly from /etc/shadow. This setup has been working for several month now, but is broken since last Monday. I haven't changed anything neither on the server nor on the clients. Now whenever a

On Mon, 7 May 2001, Lawrence Greenfield wrote: > Date: Mon, 7 May 2001 13:37:42 -0300 (ADT) > From: "Marc G. Fournier" <marc.fournier@acadiau.ca> > > [...] > If I do an 'saslpasswd -d marc' to remove myself from the sasldb file, > then try and re-connect with pine, I get the following error: > > May 7 13:21:00 new-relay imapd[66067]:

Hello list. I have a question for fail2ban for bad logins on sasl. I use sasl, sendmail and cyrus-imapd. In jail.conf I use the following syntax: [sasl-iptables] enabled = true filter = sasl backend = polling action = iptables[name=sasl, port=smtp, protocol=tcp] sendmail-whois[name=sasl, dest=my at email] logpath = /var/log/maillog maxretry = 6 and the following filter:

Hello! After moving from Centos 5.6 to Centos 6, I figured that Sendmail minor version was updated from 8.13.x to 8.14 and Dovecto from 1.2 to 2.0.x In previous configuration SMTP auth worked fine (no SASAUTHD neccessary) for virtual users table. Dovecot was authenticating virtual users virtual checking dovecot.passwd file. I'm not sure how Sendmail was processing SMTP AUTH for virtual users

http://bugzilla.mindrot.org/show_bug.cgi?id=974 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Platform|HPPA |All Summary|Enhancement : Record |Record Badlogins for

I am trying to deploy my first rails app with Dreamhost. I ftp''d over my existing app, turned on Passenger and pointed it to my /public directory. When I go to ''www.mydomain.com'' I get the ''Ruby on Rails: Welcome aboard'' default page, including the following: Getting started Here’s how to get rolling: 1. Create your databases and edit

Folks I am using sendmail as my mail server. SELINUX is disabled. I observe messages in Centos 7 (and 6) in /var/log/messages, similar to: saslauthd[2765]: do_auth : auth failure: [user=bettie] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error] I guess that this is because somebody tried to access one of the SMTP ports with a logon attempt. This is understandable; there are

Dear Timo, Do you intend to introduce bcrypt into the built in password schemes? In lew of all these hacks lately many larger companies appear moving this way, we are looking at it too, but dovecot will then be the weakest link in the database security. So, are you planning on this and if so what sort of timeframe / version would you expect it to be in beta ? Nik

https://bugzilla.mindrot.org/show_bug.cgi?id=974 Simon Deziel <simon at sdeziel.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon at sdeziel.info -- You are receiving this mail because: You are the assignee for the bug.