Displaying 13 results from an estimated 13 matches for "do_auth".
2010 Feb 10
3
saslauthd attack
...ers. Meanwhile...
I'm running Sendmail. This pertains to Centos 4 and 5 servers. I'm also
running fail2ban on some and Ossec on others. So far, no blocking is
being done. When I look at the logs all I find is under messages and
here is a sample:
Feb 10 05:23:08 neptune saslauthd[3370]: do_auth : auth failure:
[user=anna] [service=smtp] [realm=] [mech=shadow] [reason=Unknown]
Feb 10 05:23:25 neptune saslauthd[3369]: do_auth : auth failure:
[user=anna] [service=smtp] [realm=] [mech=shadow] [reason=Unknown]
Feb 10 05:23:58 neptune saslauthd[3370]: do_auth : auth fa...
2017 Oct 17
2
Auth failure messages
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
crackers out there. I'd like to block SMTP completely from t...
2005 Sep 19
1
pam and sasl2-sample-server failure
...ccept lock
saslauthd[3176] :have_baby : forked child: 3177
saslauthd[3176] :have_baby : forked child: 3178
saslauthd[3176] :have_baby : forked child: 3179
saslauthd[3176] :have_baby : forked child: 3180
saslauthd[3177] :rel_accept_lock : released accept lock
saslauthd[3177] :do_auth : auth failure: [user=testuser]
[service=rcmd] [realm=] [mech=pam] [reason=PAM auth error]
# sasl2-sample-server -s rcmd -p 8000
trying 2, 1, 6
trying 10, 1, 6
socket: Address family not supported by protocol
accepted new connection
send: {11}
PLAIN LOGIN
recv: {5}
LOGIN
recv: {1}
N
send:...
2005 Mar 15
0
cyrus - sieveshell - su - named issues (selinux?) on
sieveshell cannot connect as any user
Mar 14 23:53:45 srv1 saslauthd[22038]: do_auth : auth failure:
[user=root] [service=sieve] [realm=] [mech=shadow] [reason=Unknown]
Mar 14 23:53:45 srv1 sieve[22047]: Password verification failed
Mar 14 23:53:45 srv1 perl: No worthy mechs found
Mar 15 00:01:54 srv1 saslauthd[22164]: do_auth : auth failure:
[user=root] [service=s...
2008 May 25
1
saslauthd for sendmail SMTP relay
...#39;t changed anything neither on the server nor on
the clients. Now whenever a client tries to relay email I see this
messages in the logs:
/var/log/maillog:
AUTH failure (LOGIN): authentication failure (-13) SASL(-13):
authentication failure: checkpass failed
/var/log/messages:
saslauthd[3665]: do_auth : auth failure: [user=username]
[service=smtp] [realm=] [mech=shadow] [reason=Unknown]
Does someone have an idea how to debug this further, esp. how to find
the real reason as the message [reason=Unknown] is not very helpful at
all.
Thanks in advance,
Bernd.
2012 Oct 13
2
Proposed libguestfs API for implementing libvirt virConnectOpenAuth
As in the example code below.
static void
do_auth (guestfs_h *g,
void *opaque,
uint64_t event,
int event_handle,
int flags,
const char *buf, size_t buf_len,
const uint64_t *array, size_t array_len)
{
char **creds;
size_t i;
char *prompt;
char *reply;
size_t replylen;
// buf will be...
2017 Apr 26
4
saslauth logging
Hi
Not sure whether this is the correct list to ask ... if it's not please direct me to the correct one.
Is it possible on to log a bit more detail when auth failure occurs when using saslauthd?
saslauthd[2119]: do_auth : auth failure: [user=DELETED] [service=smtp] [realm=DELETED] [mech=pam] [reason=PAM auth error]
What I want is the IP address and if possible the incorrect password (just to see how far they are off).
Is this possible?
thanks
Jobst
--
If a pig loses its voice, is it disgruntled?
| |0|...
2009 Aug 26
3
saslauthd
...slauthd/mux
saslauthd[1936] :main : using process model
saslauthd[1936] :have_baby : forked child: 1937
saslauthd[1936] :have_baby : forked child: 1938
saslauthd[1936] :have_baby : forked child: 1939
saslauthd[1936] :have_baby : forked child: 1941
saslauthd[1937] :do_auth : auth failure: [user=testomat at mail]
[service=smtp] [realm=mail] [mech=shadow] [reason=Unknown]
saslauthd[1937] :do_request : response: NO
output in /var/log/messages:
Aug 26 07:41:31 x02-new saslauthd[1673]: server_exit : master exited: 0
Aug 26 07:41:33 x02-new saslauthd[19...
2017 Apr 26
0
saslauth logging
On 4/25/2017 7:00 PM, Jobst Schmalenbach wrote:
> Is it possible on to log a bit more detail when auth failure occurs when using saslauthd?
>
> saslauthd[2119]: do_auth : auth failure: [user=DELETED] [service=smtp] [realm=DELETED] [mech=pam] [reason=PAM auth error]
>
> What I want is the IP address and if possible the incorrect password (just to see how far they are off).
> Is this possible?
what protocol are these users connecting with thats using sasl...
2009 Oct 21
1
CentOS-5.3 saslauth configuration issue
...documentation on
how to do this. What I am running into in this case has me baffled.
If I start saslauthd as a service:
# service saslauthd start
And I try testsaslauthd -u cyrus -p test
Then I see this:
0: NO "authentication failed"
and in the syslog I see this::
saslauthd[5995]: do_auth : auth failure: [user=cyrus]
[service=imap] [realm=] [mech=pam] [reason=PAM auth error]
However, if I stop the system service:
# service saslauthd stop
and I run the saslauthd daemon from the tty with debug on:
# saslauthd -a shadow -d -n 6
then when I try
# testsaslauthd -u cyrus -p...
2006 May 31
13
What are controller modules *for*?
I am aware that controllers can be placed in modules:
ruby script/generate controller modulename/controllername
But what does this buy me? Is it just a way of ensuring that my source
code is nicely arranged, or can I use the fact that a set of controllers
are all within a particular model to implement functionality common to
all of those controllers?
Why am I asking?
The app
2012 Oct 13
0
[PATCH] New APIs: Model libvirt authentication events through the API.
...ate ();
+ if (!g) exit (EXIT_FAILURE);
+
+ /* Tell libvirt what credentials the program supports. */
+ r = guestfs_set_libvirt_supported_credentials (g, creds);
+ if (r == -1)
+ exit (EXIT_FAILURE);
+
+ /* Set up the event handler. */
+ eh = guestfs_set_event_callback (
+ g, do_auth,
+ GUESTFS_EVENT_LIBVIRT_AUTH, 0, NULL);
+ if (eh == -1)
+ exit (EXIT_FAILURE);
+
+ /* An example of a call that may ask for credentials. */
+ r = guestfs_add_domain (
+ g, "dom",
+ GUESTFS_ADD_DOMAIN_LIBVIRTURI, "qemu:///system",
+ -1);
+ if...
2003 Jul 18
2
ASMTP setup on 4.8
Hello,
I'm trying to set up a sendmail server on 4.8 that supports auth-based
relaying. I followed the procedures at
http://puresimplicity.net/~hemi/freebsd/sendmail.html, and aside from
having to run makes manually in the library directories, I had no
difficulty. I did not use the rebuild world recommendation, though.
Everything is up and running, but whenever I try to send mail