Perhaps this will also fix T803 ?

@jeremiah.foster @mak can we consider the above?

New version of libccid ((1.4.32-1) ) has been released and it includes our upstream packages to include Support for the Librem Key USA (
https://salsa.debian.org/rousseau/CCID/-/tags/ccid-1.4.32)

wondering whether chromium (not the ungoogled variant) complies with FSF endorsement. Discussion ongoing in the forum...

Still there in 1.8.4
It's any custom action. Leaving the command blank, it kicks back "command not configured", but put anything in there and it crashes.

In T818#16690, @SagarPrakash wrote:

In T818#16052, @CarloDz wrote:

Online privacy is some how tricky to handle as things are becoming complicated but nevertheless online privacy tools like tor, vpn, password manager etc. As per the BuyBestVPN, most effected and widely use tool is VPN due to level of encryption and anonymity.

Thank you for sharing the valuable site which actually talks about privacy, security and online privacy tools.

In T818#16052, @CarloDz wrote:

Online privacy is some how tricky to handle as things are becoming complicated but nevertheless online privacy tools like tor, vpn, password manager etc. As per the thevpnexperts, most effected and widely use tool is VPN due to level of encryption and anonymity.

The OEM downloads link is broken. Should probably be replaced with either
https://downloads.puri.sm/9/oem/gnome/
or
https://downloads.puri.sm/amber/oem/gnome/

@mak main issue here is that i can't tell if the correct match string (so i did not use any wildcards) or if there are other devices with the same match that might break.

Like this?
https://github.com/systemd/systemd/pull/11516 or this https://github.com/systemd/systemd/issues/15360

Hmm, I don't have a Librem with a German keyboard so I can't test this and would have to apply this change blindly.
This looks like something that should also go into upstream systemd, right?

Oh btw, this has to be applied to v3 Librems as well, because the fix for the US keyboard breaks the | key on them as well.

Can we retry this with the later Byzantium images? This bug was filed before there was an updated image.

Looks like a lot of the dependencies use old versions.

---------------------------------------------------------------------------------

That is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765936 and documented here documented in /usr/share/doc/libvirt-daemon/README.Debian.gz . It would be best to just set the correct capability in pureos (setcap cap_net_admin+ep /usr/lib/qemu/qemu-bridge-helper)

Thank you for that. It looks like you're using PureOS Amber (at least, that's the version of systemd that is in PureOS Amber).

Debian does talk about this as a configuration option in their wiki: https://wiki.debian.org/PulseAudio, but on cursory inspection, I don't see a bug filed for changing default settings. This may have to go further upstream to PulseAudio itself.

I can't reproduce this on my Librem 13 v3 running Byzantium. But, I will look into seeing how we can change the default.

@jeremiah.foster great! i'd skip amber-phone since it's just an overlay and we want to merge for byzantium anyways.

Amber is now officially in Debian's debootstrap. Next is Byzantium. Do we want to have amber-phone as well?

This is a workaround: https://gitlab.gnome.org/GNOME/epiphany/issues/838 (disable flat-volume option).

Definitely need this, had this fixed already several times, but it seems to get overwritten when doing updates.

systemd should be version 241 in PureOS Amber and 242 in PureOS Byzantium.

Which version of systemd are you using?

From @mak;

There are policy decisions needed

• which key do we sign this with?
• the archive key?
• a new key?

It's difficult to automate due to security boundaries in the infrastructure and code needs to be written for it

@davidpluseipi Yep, this is the same problem. I don't think the package is maintained at the moment, so it's easier to uninstall it.

We can perhaps sign this file: https://downloads.puri.sm/byzantium/gnome/2020-02-15/checksums.sha256sum upon each release.

Closing because we've moved to Amber and this references Green.

I think the user manual mentioned on this page is missing sections that I and other users would find very helpful:

Yeah, i've seen that but that assume the user understands what is going on (and involves user intervention for s.th. that could be automatic).

I know this thread is closed but it's the only place anyone seems to be discussing this. Im happy to open a new issue or post to another.

We have made a wiki entry for users to be able to migrate their profile from ~/.purism/purebrowser to ~/.mozilla/firefox/(randomstringhere).default-esr

I use this:

Now, a bigger issue I see is that the usb key is not required for login. Having it launch the screensaver automatically is cute but not really that helpful. Are there other librem key docs that detail adding more security such as two factor logins? Should we be using the nitro key site?

What about the status of the original request which was to add a package to do this work for the user?

for anyone reading this thread, here are 4 different udev rules you might use to make this work:

There are a few other issues with the docs that could be clarified.

With unbreak i mean it prints the symbols shown on the buttom instead of '#' which left the user pretty stranded when doing math stuff (or wanting to use the pipe symbol in the shell)

Support for the Librem Key has been merged into CCID : https://salsa.debian.org/rousseau/CCID/commit/ebd991f05c1ea2ba55bc431f624c7682c14ca623

Ok, finally managed to send a message to the developer via email that did not bounced back.

@jeremiah.foster I am not sure but I don't think Yamane-san is hanging out on irc

I'd like to set up an OpenQA instance. But it looks like I can't use PureOS or Debian to do so. The only blocker is a MR in Salsa: https://salsa.debian.org/debian/os-autoinst/merge_requests/1/diffs which looks pretty reasonable. @jonas.smedegaard does Hideki Yamane-san hang out in the Debian-perl channel, perhaps we ask him to merge that diff there? Otherwise I'll go ahead and install on SuSE (heaven forbid.)