public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Cc: Bernhard Landauer <oberon@manjaro.org>
Subject: Re: [ANNOUNCE] v4.9.30-rt20
Date: Sun, 28 May 2017 01:59:49 +0200	[thread overview]
Message-ID: <20170528015949.2dc4ae46@archlinux.localdomain> (raw)
In-Reply-To: <20170528014737.01da53e6@archlinux.localdomain>

On Sun, 28 May 2017 01:47:37 +0200, Ralf Mardorf wrote:
>On Sun, 28 May 2017 00:32:15 +0200, Bernhard Landauer wrote:
>>the whole point in signing archives at all is that I want to know 
>>who's key it is before accepting it.
>>It doesn't make much sense to just blindly accept an unknown key  
>
>Hi Bernhard,
>
>without doubts this is a valid point. I suspect that most, if not all
>important keys, for me suffer from missing validation. The "web of
>trust" is the weak point of signing. However, a download from a https
>page + a key that perhaps isn't validated by a web of trust, in
>combination with contact to upstream and/or distro communities, e.g. by
>mailing lists, isn't that bad. It's not absolutely secure, but still
>ok, assuming that the kernel is used e.g. for audio productions, that
>don't require hardcore security.
>
>Regards,
>Ralf

PS:

Not that long ago, did a validated key protect anybody from
Heartbleed ;)? In the end you still need to trust upstream.

      reply	other threads:[~2017-05-27 23:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 16:32 [ANNOUNCE] v4.9.30-rt20 Sebastian Andrzej Siewior
2017-05-27 17:19 ` Bernhard Landauer
2017-05-27 17:33   ` Sebastian Andrzej Siewior
2017-05-27 17:36     ` Bernhard Landauer
2017-05-27 21:55       ` Ralf Mardorf
2017-05-27 22:32         ` Bernhard Landauer
2017-05-27 23:47           ` Ralf Mardorf
2017-05-27 23:59             ` Ralf Mardorf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170528015949.2dc4ae46@archlinux.localdomain \
    --to=ralf.mardorf@alice-dsl.net \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=oberon@manjaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox