All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Farrell <djfarrell@gmail.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: JT Moree <moreejt@yahoo.com>, dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] cryptsetup Yubikey challenge-response support
Date: Wed, 15 Apr 2020 00:08:42 -0700	[thread overview]
Message-ID: <CAKO8emaVEKTC3oY1wdQ-Cr1EkFKtUjWAOMNa4D2P2mfmgoQqCw@mail.gmail.com> (raw)
In-Reply-To: <CAKO8embP2_M58_oJhf=L-C98kDvXV9UPC6+jL34n4EuhOf+ydQ@mail.gmail.com>

And the popen mode should be "rw"...

Anyway, I think the idea is clear.

On Tue, 14 Apr 2020 at 23:48, Dan Farrell <djfarrell@gmail.com> wrote:
>
> Oh god it contains the printing out the password for testng...
>
> On Tue, 14 Apr 2020 at 23:37, Dan Farrell <djfarrell@gmail.com> wrote:
> >
> > Hi Milan,
> >
> > I can code ugly just watch!
> >
> > On Sat, 11 Apr 2020 at 09:12, Milan Broz <gmazyland@gmail.com> wrote:
> > > For the upstream cryptsetup, I will strictly reject all contributions that
> > > are distro-specific or introduces direct binding to any hw libraries into
> > > cryptsetup core (either open-source or proprietary).
> >
> > Please take a look at the attached, feel to poke fun at it, it is
> > terrible for all of the reasons.
> >
> > But, if something that did what is achieved in this patch was done
> > properly, would it be even possible to get it merged?
> >
> > Hopefully the attachment comes through...
> >
> > Regards,
> >
> > Dan Farrell

  reply	other threads:[~2020-04-15  7:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <233063842.2717340.1586366160963.ref@mail.yahoo.com>
2020-04-08 17:16 ` [dm-crypt] cryptsetup Yubikey challenge-response support JT Morée
2020-04-10  3:01   ` Dan Farrell
2020-04-11 14:49     ` JT Moree
2020-04-11 16:09       ` Milan Broz
2020-04-11 19:56         ` Arno Wagner
2020-04-11 21:05           ` JT Moree
2020-04-11 22:23             ` Arno Wagner
2020-04-12 13:00               ` [dm-crypt] LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: " Michael Kjörling
2020-04-14 10:56                 ` Milan Broz
2020-04-15 22:25                   ` Arno Wagner
2020-04-14 11:35           ` [dm-crypt] " Milan Broz
2020-04-15 21:47             ` Arno Wagner
2020-04-15  6:37         ` Dan Farrell
2020-04-15  6:48           ` Dan Farrell
2020-04-15  7:08             ` Dan Farrell [this message]
2020-04-15 19:38           ` Milan Broz
2020-04-16  2:03             ` Dan Farrell
2020-04-16 10:36               ` Milan Broz
2020-04-08  8:37 7heo
2020-04-08 10:07 ` Nikolay Kichukov
2020-04-08 16:31   ` Tim Steiner
2020-04-08 22:18     ` Dan Farrell
  -- strict thread matches above, loose matches on Subject: below --
2020-04-08  7:54 Dan Farrell

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=CAKO8emaVEKTC3oY1wdQ-Cr1EkFKtUjWAOMNa4D2P2mfmgoQqCw@mail.gmail.com \
    --to=djfarrell@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    --cc=moreejt@yahoo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.