mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] OpenSSH patches
Date: Wed, 29 Jul 2015 22:05:25 +0200	[thread overview]
Message-ID: <20150729200525.GA6119@pqgruber.com> (raw)
In-Reply-To: <20150714100347.GC30722@pengutronix.de>

On Tue, Jul 14, 2015 at 12:03:47PM +0200, Michael Olbrich wrote:
> On Tue, Jul 07, 2015 at 10:52:52AM +0200, Clemens Gruber wrote:
> > what do you think about my recent OpenSSH patches (not the version bumps) but
> > enabling the sandbox per default (to use seccomp if available) and the switch
> > from DSA to Ed25519. ArchLinux and current Debian both generate Ed25519 pubkeys
> > by default and add them as HostKey to sshd_config.
> > They keep DSA and ECDSA but as they fall apart completely if the random numbers
> > used are not good, I am not sure this is a good idea for embedded systems where
> > entropy is often very scarce. Ed25519 is not that sensitive to entropy problems.
> 
> I looked at what Debian is doing, and I liked it: Basically, the postinst
> script checks the sshd_config and generated the needed keys. I think we can
> do the same in the ssh rc-once script.
> Then we can choose more restrictive defaults. Then those that need other
> keys just need to overwrite sshd_config in the BSP.
> 
> Michael

Hi Michael,

what do you think about my recent patch (openssh: improve rc.once.d script and
harden sshd_config) from July 17th? I tried to follow what Debian is doing for
key generation and I also hardened the default config.

Regards,
Clemens

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-07-29 20:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  8:52 Clemens Gruber
2015-07-07  9:13 ` Bruno Thomsen
2015-07-07  9:35   ` Clemens Gruber
2015-07-14 10:03 ` Michael Olbrich
2015-07-29 20:05   ` Clemens Gruber [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=20150729200525.GA6119@pqgruber.com \
    --to=clemens.gruber@pqgruber.com \
    --cc=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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