Displaying 7 results from an estimated 7 matches for "brillault".
2015 Jun 03
30
[Bug 2408] New: Expose authentication information to PAM
https://bugzilla.mindrot.org/show_bug.cgi?id=2408
Bug ID: 2408
Summary: Expose authentication information to PAM
Product: Portable OpenSSH
Version: -current
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: PAM support
Assignee:
2016 Apr 17
6
[Bug 2564] New: ssh_config AddKeysToAgent doesn't set key name/path
https://bugzilla.mindrot.org/show_bug.cgi?id=2564
Bug ID: 2564
Summary: ssh_config AddKeysToAgent doesn't set key name/path
Product: Portable OpenSSH
Version: 7.2p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee:
2016 Nov 21
11
[Bug 2642] New: [sshconnect2] publickey authentication only properly works if used first: pubkey_prepare doesn't work after pubkey_cleanup
https://bugzilla.mindrot.org/show_bug.cgi?id=2642
Bug ID: 2642
Summary: [sshconnect2] publickey authentication only properly
works if used first: pubkey_prepare doesn't work after
pubkey_cleanup
Product: Portable OpenSSH
Version: 7.3p1
Hardware: amd64
OS: Linux
Status:
2020 Oct 22
2
Directors and LMTP: mailAlternateAddress of same user
Good evening everyone,
I'd like to paste a problem i experience the last days with a mail
cluster system based on three dovecot servers and two directors in front
of them. The Directors are proxying the auth requests to the dovecot
servers below (LDAP). The protocols i use are imap/managesieve/lmtp.?
The setup works as intented, exept one detail. There are a lot of users
that happen to
2014 Nov 18
55
[Bug 2319] New: [PATCH REVIEW] U2F authentication
https://bugzilla.mindrot.org/show_bug.cgi?id=2319
Bug ID: 2319
Summary: [PATCH REVIEW] U2F authentication
Product: Portable OpenSSH
Version: 6.7p1
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Miscellaneous
Assignee: unassigned-bugs at
2020 Oct 26
0
Directors and LMTP: mailAlternateAddress of same user
Dear Ioannis,
> I've searched around for a solution to this, and figured out that a special
> userdb {} section in the protocol lmtp {} section, with driver = ldap etc etc
> so that i 'd be able to "show" the correct user to the lmtp might work, but
> strangely that userdb {} setting looks like being ignored by lmtp.
A very similar issue was discussed on IRC last
2020 Nov 11
0
Support TLS for pure remote doveadm commands
Dear all,
A lot of doveadm commands (e.g. backup/sync, deduplicate, mailbox) support a
`-S` (a.k.a `socket-path`) argument that allows to run the command remotely.
Unfortunately, I think that there is a bug in the handling of the TLS
configuration for this feature.
After a bit of debugging, I think it's simply due to
doveadm_mail_server_user_get_host