Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1024995

Bug#968603: memcached should enable TLS by default

From Tomas Korbar <tkorbar@redhat.com>
Newsgroups linux.debian.bugs.dist
Subject Bug#968603: memcached should enable TLS by default
Date 2020-09-14 10:40 +0200
Message-ID <AOSbM-8rV-3@gated-at.bofh.it> (permalink)
References <AF94d-6dh-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi Chriss,
I'm the maintainer of memcached on Fedora and RHEL,

On Thu, 10 Sep 2020 22:58:03 -0000 "Chris Lamb" <lamby@debian.org>
wrote:
> Hi Moises,
>
> > We run the tests afterward on a dedicated machine..
>
> The question here is not when or where these tests are run - can you
> reproduce these test failures at all on this other machine? I can
> reproduce them locally here (NB. with TLS enabled during the build).
>
> If you can/cannot, sharing the test log would be a good next step.
I can not. The testsuite on Fedora does not hang. I remember a
situation similar to this. When i first enabled tls in Fedoras memcached
the testsuite hanged because test certificates had short key and
Fedora has hardened crypto environment, thus memcached crashed
during testing and suite was not prepared for that.

I can show you a test log from Fedora Rawhide where we have 1.6.7.
https://tkorbar.fedorapeople.org/test.log

I will try to install debian VM and reproduce this.

>
> > ...we do not run memcacheds test suite during build because it is
cpu
> > load dependent and not stable enough for us to rely on it during
build.
>
> As an unrelated remark, if the tests are CPU-load dependent (and
> therefore non-deterministic) I would suggest you file that as an
> upstream issue. A randomly-failing testsuite is, as I am sure you are
> aware, not good software engineering practice.
>
Yeah, i know that the suite is not ideal but i did not yet get to
handle that. It is stable on normal build machines
but if you run it on some powerful server CPU then techniques
like "sleep(0.5)" starts to fail. I will keep in mind to fix this.
> Thanks for looking into this so far.
>
> Regards,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
>        `-
>
>
Regards.

Back to linux.debian.bugs.dist | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#968603: memcached should enable TLS by default Moises Guimaraes de Medeiros <moguimar@redhat.com> - 2020-08-18 14:40 +0200
  Bug#968603: Acknowledgement (memcached should enable TLS by default) Moises Guimaraes de Medeiros <moguimar@redhat.com> - 2020-08-18 17:10 +0200
  Bug#968603: memcached should enable TLS by default "Chris Lamb" <lamby@debian.org> - 2020-09-09 13:50 +0200
  Bug#968603: memcached should enable TLS by default Moises Guimaraes de Medeiros <moguimar@redhat.com> - 2020-09-10 15:40 +0200
    Bug#968603: memcached should enable TLS by default "Chris Lamb" <lamby@debian.org> - 2020-09-11 01:10 +0200
  Bug#968603: memcached should enable TLS by default Tomas Korbar <tkorbar@redhat.com> - 2020-09-14 10:40 +0200
    Bug#968603: memcached should enable TLS by default "Chris Lamb" <lamby@debian.org> - 2020-09-14 12:30 +0200
      Bug#968603: memcached should enable TLS by default Tomas Korbar <tkorbar@redhat.com> - 2020-09-14 14:40 +0200
        Bug#968603: memcached should enable TLS by default "Chris Lamb" <lamby@debian.org> - 2020-09-15 01:00 +0200
          Bug#968603: memcached should enable TLS by default Tomas Korbar <tkorbar@redhat.com> - 2020-09-15 10:00 +0200
            Bug#968603: memcached should enable TLS by default "Chris Lamb" <lamby@debian.org> - 2020-09-15 15:40 +0200
              Bug#968603: memcached should enable TLS by default Tomas Korbar <tkorbar@redhat.com> - 2020-09-16 09:50 +0200

csiph-web