similar to: Dovecot not obeying disable_plaintext_auth = yes and how to force/disable encryption

Displaying 20 results from an estimated 9000 matches similar to: "Dovecot not obeying disable_plaintext_auth = yes and how to force/disable encryption"

2013 Feb 19
1
Dovecot auth works when tested with doveadm, but fails with Postfix
I have three postfix 2.9.5 servers: chombo, rush, yoshi. Chombo relays to rush and yoshi for outbound email. Outbound relay requires SASL authentication. Rush and yoshi run Dovecot 2.1.12 servers with simple passwd-file backends. If I create a new password hash for chombo's user, houseloki, on either rush or yoshi: # doveadm pw -u houseloki -p <password> {CRAM-MD5}... Then I
2017 Oct 26
2
haproxy ssl support
Even though it seems dovecot (using 2.2.33.1) supports haproxy's send-proxy-v2, it seems to lack send-proxy-v2-ssl (which also sends client's ssl state). It would be a nice feature for the backend server to identify clients so one wouldn't have to use disable_plaintext_auth on a production environment. --- haproxy.cfg frontend pop3 bind [::]:110 v4v6 bind
2017 Oct 26
1
haproxy ssl support
When is 2.3 scheduled to be released? Kevin > On Oct 26, 2017, at 7:57 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > Hi! > > There is support for haproxy SSL TLVs in 2.3. See > > https://github.com/dovecot/core/compare/f43567aa%5E...b6fbc235.patch > > Aki > >> On October 26, 2017 at 12:25 PM Rok Poto?nik <r at rula.net> wrote: >>
2017 Oct 26
0
haproxy ssl support
Hi! There is support for haproxy SSL TLVs in 2.3. See https://github.com/dovecot/core/compare/f43567aa%5E...b6fbc235.patch Aki > On October 26, 2017 at 12:25 PM Rok Poto?nik <r at rula.net> wrote: > > > Even though it seems dovecot (using 2.2.33.1) supports haproxy's > send-proxy-v2, it seems to lack send-proxy-v2-ssl (which also sends > client's ssl state).
2016 Oct 15
2
IPv6 address configuration and default IPv6 address with CentOS 6.8?
Hello, when I have this in /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no ONBOOT=yes DEVICE=eth0 USERCTL=no ... IPV6INIT=yes IPV6ADDR=2001:DB8:DEAD:BEEF::10 IPV6ADDR_SECONDARIES="2001:DB8:DEAD:BEEF::20 2001:DB8:DEAD:BEEF::30 2001:DB8:DEAD:BEEF::40 2001:DB8:DEAD:BEEF::50" IPV6_AUTOCONF=no IPV6_DEFAULTGW=2001:DB8:DEAD:BEEF::1 IPV6_DEFAULTDEV=eth0 I
2018 Sep 10
2
samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ
Hi, all I trying setting domain samba with bind9-DLZ. I followed the tutorial https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, but not work. see the tests bellow ricardobarbosa at isadora:~$ bash tools/testSambaRecords.sh Host _ldap._tcp.freewaynet.corp not found: 3(NXDOMAIN) Host _kerberos._udp.freewaynet.corp not found: 3(NXDOMAIN) Host
2016 Sep 13
2
IPv6 routing with 2 different prefixes
Hello I've got two prefixes, one /48 and one /64 let's say these two 2001:db8:0815::/48 2001:db8:4711:cafe::/64 the router has on it's ethernet interface the following to IPv6 addresses: 2001:db8:0815::1/48 2001:db8:4711:cafe::1/64 a windows box has 2001:db8:0815::17/48 and 2001:db8:0815::1 as it's gateway a linux box has 2001:db8:4711:cafe::11/64 and 2001:db8:4711:cafe::1 as
2011 Dec 01
0
Are squeeze Xen dom0 kernels subject to this the same IPv6 GSO problem?
Hi, I have three squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They've been in production for around 6 months now
2011 Dec 13
0
Are Debian squeeze dom0 kernels subject to this same IPv6 GSO problem?
Hi, I have three Debian squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They''ve been in production for around 6
2020 May 07
6
[Bug 3161] New: ssh -J <public IPv6> <LL IPv6%scopeID> doesn't work as expected
https://bugzilla.mindrot.org/show_bug.cgi?id=3161 Bug ID: 3161 Summary: ssh -J <public IPv6> <LL IPv6%scopeID> doesn't work as expected Product: Portable OpenSSH Version: 8.2p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5
2018 Sep 10
1
samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ
Em 10-09-2018 10:43, Rowland Penny via samba escreveu: > On Mon, 10 Sep 2018 09:56:46 -0400 > spiderslack via samba <samba at lists.samba.org> wrote: > >> Hi, all >> >> >> I trying setting domain samba with bind9-DLZ. I followed the tutorial >> https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, >> but not
2014 May 13
0
[Bug 940] New: ip6tables-save output invalid rule when using D/SNPT
https://bugzilla.netfilter.org/show_bug.cgi?id=940 Summary: ip6tables-save output invalid rule when using D/SNPT Product: iptables Version: 1.4.x Platform: x86_64 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: ip6tables AssignedTo: netfilter-buglog at lists.netfilter.org
2014 Dec 03
0
[Cerowrt-devel] tinc vpn: adding dscp passthrough (priorityinherit), ecn, and fq_codel support
On Wed, Dec 3, 2014 at 6:17 AM, David P. Reed <dpreed at reed.com> wrote: > Tor needs this stuff very badly. Tor has many, many problematic behaviors relevant to congestion control in general. Let me paste a bit of private discussion I'd had on it in a second, but a very good paper that touched upon it all was: DefenestraTor: Throwing out Windows in Tor
2011 Mar 07
1
what wrong about my ipv6 address
Hi I used the command "ip -6 addr add 2001:DB8:CAFE:1111::12/64 dev eth0" to add ipv6 address and can see it in ifconfig but can't ping it Why? Thank you # ping6 2001:db8:cafe:1111::12 PING 2001:db8:cafe:1111::12(2001:db8:cafe:1111::12) 56 data bytes >From ::1 icmp_seq=1 Destination unreachable: Address unreachable >From ::1 icmp_seq=2 Destination unreachable: Address
2015 Oct 14
1
TLS communication director -> backend with X.509 cert checks?
Hi Timo Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 01:10:20 CEST): ? > Ah, the information comes from the other director running. The other one > is using an unpatched version of dovecot. Your patch for backend-certificate verification works. Thank you for the good and fast work. Is there any chance that this will make it into Dovecot's next release? BTW: The
2009 Jun 05
1
[Bug 1602] New: ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Summary: ssh: doesn't handle IPv6 addresses with brackets Product: Portable OpenSSH Version: 5.2p1 Platform: All OS/Version: Linux Status: NEW Keywords: low-hanging-fruit Severity: normal Priority: P2 Component: ssh AssignedTo:
2020 May 15
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #6 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Just did some more testing with OpenSSH_8.1p1 Apr 2020. It looks like someone did the work to implement a new ssh://[brackets] syntax except in the case where brackets are actually needed. Baffling. So these now work: ssh ssh://[host.local]:23 ssh
2016 Nov 09
0
[Bug 1097] New: TARPIT function does not work in ip6tables
https://bugzilla.netfilter.org/show_bug.cgi?id=1097 Bug ID: 1097 Summary: TARPIT function does not work in ip6tables Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Ubuntu Status: NEW Severity: normal Priority: P5 Component: ip6_tables (kernel) Assignee:
2014 Jan 03
1
disable_plaintext_auth = yes not showing in doveconf -n output?
I have it set, but it doesn't show up. However, I noticed that it does show as enabled by default in doveconf -a output. Is this why it doesn't show up in doveconf -n output? -- Best regards, Charles
2013 Nov 21
2
Query:: Reg: Libvirt Networking
Currently, I have two networks configured via xml: virsh # net-dumpxml TestNetwork1 <network connections='2'> <name>TestNetwork1</name> <uuid>a76f665a-0196-4edb-81b4-340944a6869c</uuid> <forward dev='p1p1' mode='nat'> <nat> <port start='1024' end='65535'/> </nat> <interface