A patch was proposed (and merged) in the linked upstream bug:
https://github.com/cyrusimap/cyrus-sasl/pull/6
This seems to be marked for the 2.2.0 release.
The next steps here would be to backport and verify the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: cyrus-sasl2
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657897
Title:
Failure to report rhosts
To manage notifications about this bug go to:
https://
I think we should defer to upstream on this one.
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided => Critical
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Critical => Wishlist
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug not
Upstream issue: https://github.com/cyrusimap/cyrus-sasl/issues/346
** Also affects: cyrus-sasl2 via
https://github.com/cyrusimap/cyrus-sasl/issues/346
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Is this log line enough for fail2ban purposes?
Jan 25 16:56:13 uvt-yakkety postfix/smtpd[3313]: warning:
unknown[192.168.122.1]: SASL login authentication failed: authentication
failure
You have:
- the service (smtpd)
- the ip (192.168.122.1)
- the failure reason ("authentication failure")
** Bu
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657897
Title:
Failure to report rhosts
To manage notifications about this b
Yes that is the correct issue occurring effectively pam never sees the rhost
data from sendmail which can be seen in the auth log.
Jan 25 16:56:12 uvt-yakkety saslauthd[3020]: pam_unix(smtp:auth):
authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
user=powersj
I did some more inves
@James, big thanks for the information I think your clarity about the
logging of the rhost and the redhat bug helped a bit.
To help get work completed on this bug I tried to reproduce this by
setting up a mail server using sasl using these steps [1]. I was then
able to telnet to it from a remote h
Hi, Thanks for the reply.
First of I will say that everything to reproduce this is a default
configuration for saslauthd. You simply have to install it. The next
part would be to install any of the other default like imapd(no
configuration required) or sendmail(which does need configured). Or any
Hi James,
thank your for your report and your help to make Ubuntu better.
These are essentially two issues in one.
For the first being "fail sasl+pam" - would you have some steps to reproduce
the issue.
At least I must admit I never set them up, and others coming by to help might
as well.
So if
10 matches
Mail list logo