On 2017-08-07 21:00:05 [+0200], Salvatore Bonaccorso wrote:
> Hi Sebastian
Hi Salvatore,
> Thanks for review. The reason I did that is indeed, to have a patch
> which is most acceptable for upstream to include, independent on
> Debian, although upstream since I initially pinged never replied to my
On Mon, Aug 07, 2017 at 09:00:05PM +0200, Salvatore Bonaccorso wrote:
> Hi Sebastian
>
> On Mon, Aug 07, 2017 at 07:15:19PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> > > Control: severity important
> >
> > as in SSL not working anymo
Hi Sebastian
On Mon, Aug 07, 2017 at 07:15:19PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> > Control: severity important
>
> as in SSL not working anymore in unstable for libesmtp.
>
> > Hi Jeremy,
> Hi Salvatore,
>
> > Please find at
On 2017-08-07 14:26:07 [+0200], Salvatore Bonaccorso wrote:
> Control: severity important
as in SSL not working anymore in unstable for libesmtp.
> Hi Jeremy,
Hi Salvatore,
> Please find attached a (refreshed) patch which is still valid to add
> the proper support for TLSv1.1+
Description: Add
Control: severity important
Hi Jeremy,
Cc'ing the OpenSSL maintainers.
On Mon, Nov 21, 2016 at 07:42:17AM +0100, Salvatore Bonaccorso wrote:
> Hi Jeremy,
>
> On Thu, Oct 13, 2016 at 06:20:49PM -0400, Jeremy T. Bouse wrote:
> > Upstream has been completely MIA for several years now. I've not real
Hi Jeremy,
On Thu, Oct 13, 2016 at 06:20:49PM -0400, Jeremy T. Bouse wrote:
> Upstream has been completely MIA for several years now. I've not really
> checked to determine if there's actually anything dependent on libesmtp
> and have contemplated archive removal as I am not taking over as
> upstr
Upstream has been completely MIA for several years now. I've not really
checked to determine if there's actually anything dependent on libesmtp
and have contemplated archive removal as I am not taking over as
upstream and the project itself has appeared to be lifeless and I've
merely been keeping t
Hi Jememy,
Since almost now a year I try to get that patch forwarded and I have
it locally running without problems. I do not get a reply from
upstream author.
Are you in contact with upstream/have an alternative contact address?
The freeze for Debian stretch is approaching in meanwhile really f
Control: tags -1 + patch
Hi,
Okay I understand the wontfix reasoning, though I would still want to
point out that it will be become more and more important in future to
not only support TLSv1. I have put a tentative patch together and am
CC'ing upstream author as well.
The patch adds as well a c
Hi Jeremy,
On Thu, Oct 22, 2015 at 09:25:29AM -0400, Jeremy T. Bouse wrote:
> severity 802658 wishlist
> tags 802658 + wontfix
I'm interested in the reasoning about the "wontfix". Do you think
Upstream will not take a patch approaching this? Or are there other
reasons/am I missing something?
Tha
Source: libesmtp
Version: 1.0.6-1
Severity: normal
Hi
libesmtp currently only supports TLSv1:
smtp-tls.c:
199 /* The decision not to support SSL v2 and v3 but instead to use only
200 TLSv1 is deliberate. This is in line with the intentions of RFC
11 matches
Mail list logo
