similar to: DO NOT REPLY [Bug 1890] TLS for rsync protocol

https://bugzilla.samba.org/show_bug.cgi?id=1890 devzero at web.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devzero at web.de ------- Comment #3 from devzero at web.de 2009-08-07 05:11 CST ------- wouldn`t it be better to give up on that effort

https://bugzilla.samba.org/show_bug.cgi?id=1890 --- Comment #11 from roland <devzero at web.de> 2013-11-22 22:21:30 UTC --- from the rsync 3.1.0 release notes : Rsync now comes packaged with an rsync-ssl helper script that can be used to contact a remote rsync daemon using a piped-stunnel command. It also includes an stunnel config file to run the server side to support

https://bugzilla.samba.org/show_bug.cgi?id=1890 Summary: TLS for rsync protocol Product: rsync Version: 2.6.3 Platform: All URL: http://metastatic.org/source/rsync-ssl.patch OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=1890 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-10-08 14:49 ------- There is a diff in the patches directory named

On Wed, 14 Nov 2018, Aki Tuomi wrote: >> I'm providing IMAP+Starttls on port 143 for users with legacy MUA. So >> I've to enable TLS1.0 up to TLS1.3 For IMAPS / port 993 I like to >> enable TLS1.2 and TLS1.3 only. >> >> Is this possible with dovecot-2.2.36 / how to setup this? > > Not possible I'm afraid. ("Not possible" = challenge!)

On 11/14/2018 01:46 PM, Joseph Tam wrote: > On Wed, 14 Nov 2018, Aki Tuomi wrote: > >>> I'm providing IMAP+Starttls on port 143 for users with legacy MUA.? So >>> I've to enable TLS1.0 up to TLS1.3 For IMAPS / port 993 I like to >>> enable TLS1.2 and TLS1.3 only. >>> >>> Is this possible with dovecot-2.2.36 / how to setup this? >>

Hi, I've just updated ticket 1890 - https://trac.xiph.org/ticket/1890#comment:8 === As we have moved to the Xiph server at OSUOSL - we have now disabled this limitation and will observe the situation. Personally I'm very disappointed that most clients downloading the yp.xml are not accepting compressed encoding. Right now the file is 4818606 Bytes in size, most clients download it

On 6/13/21 3:36 PM, Jim Klimov via Nut-upsdev wrote: > Haven't got many ideas on this today, preoccupied with other > house-work, but can share a couple :) > > Regarding two implementations - I believe NSS and OpenSSL are licensed > differently and/or are (initially were?) available non-overlapping on > different OSes. A quick googling now showed that they both were >

On June 13, 2021 9:02:46 PM GMT+03:00, Tim Dawson <tadawson at tpcsvc.com> wrote: >Let's not overlook the simple fact that a lot of deployments are behind >secure firewalls, on secure networks, and on servers and lans that no >users have access to (physical ormotherwise), and thus have negligible >security requirements beyond what the environment already provides. >Yes,

Hmmm, you obviously know a lot more about systemd than I do, I'm going to have to look at what you posted more carefully. Thanks. ----- Original Message ----- From: "James Hogarth" <james.hogarth at gmail.com> To: "CentOS mailing list" <centos at centos.org> Sent: Wednesday, December 23, 2015 4:08:31 AM Subject: Re: [CentOS] Starting stunnel on boot with

On 23 December 2015 at 05:38, Kahlil Hodgson <kahlil.hodgson at dealmax.com.au> wrote: > On my CenOS7 system with stunnel from base > > stunnel-4.56-4.el7.x86_64 > > there's a systemd service file > > /etc/systemd/system/stunnel.service > > try > > sudo systemctl enable stunnel.service > > > Packaged unit files are in

I'd imagine document will answer many prayers for stumped admins These are my notes to setup SuSE Linux Enterprise Server v9 and how to configure Samba v3.04-SuSE to work as a member server in a domain Also, this document contains FULL instructions on how to setup SSL Secured SWAT (Samba Web Administration Tool) This document is a step by step guide to installing SLES and Samba. Of course

These self-host builders all just starting failing. It looks like tablegen is being miscompiled. The first failed builds: (1) http://lab.llvm.org:8011/builders/llvm-gcc-i386-linux-selfhost/builds/208 (2) http://lab.llvm.org:8011/builders/dragonegg-i386-linux/builds/194 (3) http://lab.llvm.org:8011/builders/dragonegg-x86_64-linux/builds/197 The odd thing is that I can't see any suspicious

On 2011-04-08 08:58, Duncan Sands wrote: > Hi Renato, > >> I was recently investigating the build bot infrastructure and noticed >> that the arm-linux target is failing for quite a long time. I believe >> that it means ARM code is not executed all that often in LLVM tests, >> is that correct? Hi i will summarise the last sucessfull builds by the ARM builder:

Please use the correct link : http://63.145.236.72:8011 and ignore the previous. Also log for broken build is here: make[1]: Entering directory `/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build llvm[1]: Compiling APInt.cpp for Release+Asserts build In file included from APFloat.cpp:15: In file

On my server, stunnel is running to accept HTTPS (port 443) connection from clients and redirect them to localhost:80. And on port 80 of my server, WEBrick is running to accept HTTP connection. In such situation, WEBrick generates URLs beginning with ''http://'', not with ''https://''. So one can access to ''https://myserver/'', but when he click on

Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host? -eric On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote: > The host c++ standard library is missing <utility>, it appears. > > > On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > >> Please use the correct link : >>

I have tracked it down to the real reason. The revisions 139934-139937 has changed the order in which configure chooses a compiler. Clang is checked first, then llvm-gcc, and then gcc. I can see the reason for this change. However, in this particular case it has broken the build because Ubuntu includes clang 2.8 which doesn't know where includes are. I have removed clang from the host to

The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >

Is there a good nntp client for Centos 6 that handles SSL native? It was difficult, to say the least, on Centos anyway, to get Pan to post to Mixmin servers, which require SSL (so we have to use Stunnel to add SSL capabilities to Pan) on Centos. Had Pan native SSL support, this wouldn't have been a problem. Hence the question: Q: Is there a good freeware NNTP client with a Centos