From: Martin Becze <mjbecze@riseup.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Documenting Yubikey setup
Date: Thu, 23 Jan 2020 09:22:41 -0500 [thread overview]
Message-ID: <b7adb762-067b-8415-2bd1-4206258f3912@riseup.net> (raw)
In-Reply-To: <877e1tbb91.fsf@gmail.com>
> Did you write something for the cookbook?
The only thing that I know to put in the cookbook is the below snippet.
I think it should be expanded a bit. But I haven't had a chance to
futher explore using Yubikey. I still have some problems using it with
icecat that I need to figure out.
On 1/14/20 11:21 PM, Chris Marusich wrote:
> Hi Martin,
>
> Martin Becze <mjbecze@riseup.net> writes:
>
>> For a user to access a Yubikey an udev rule needs to be added. This can
>> be done by using the udev rules found in libu2f-host package. To use the
>> rules the following should be added to your config.scm
>>
>> (use-modules (gnu packages security-token))
>>
>> ...
>>
>> (define %modified-desktop-services
>> (modify-services %minimal-desktop-services
>> (udev-service-type
>> config =>
>> (udev-configuration (inherit config)
>> (rules (cons libu2f-host
>> (udev-configuration-rules
>> config)))))))
>>
>>
>>
>> Reference
>> https://guix.gnu.org/manual/en/html_node/Base-Services.html
>>
>> ---
>>
>> Of course there is more to say about yubikey but this is all I needed
>> for now.
>
> Did you write something for the cookbook? I've also set up a YubiKey
> using Guix - I actually packaged some of the things like libu2f-host -
> and would be happy to review / add to whatever you've written.
>
next prev parent reply other threads:[~2020-01-23 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 19:58 Documenting Yubikey setup Martin Becze
2019-11-29 20:13 ` Pierre Neidhardt
2019-11-29 20:15 ` Pierre Neidhardt
2019-11-30 1:19 ` Martin Becze
2019-11-30 11:34 ` Pierre Neidhardt
2020-01-15 4:21 ` Chris Marusich
2020-01-23 14:22 ` Martin Becze [this message]
2020-01-23 17:17 ` Brice Waegeneire
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7adb762-067b-8415-2bd1-4206258f3912@riseup.net \
--to=mjbecze@riseup.net \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).