Hi, any update for this? It's been many months and I would still dearly love this feature.

https://bugs.debian.org/906609#30 segfault should be fixed...

I'm going to go ahead and make the executive decision of un-assigning myself from this ticket - feel free to assign back if there is a "Next Action" for me of course, but I do not have an obvious step to proceed.

Alas, I don't know who has bandwidth to do it and do not have control over their inbox. :)

(curious why this assigned to me, @mladen.pejakovic ?)

(Now? Ie. with the openpgp-smartcard branch, no?)

https://bugs.debian.org/909567

https://github.com/evilsocket/opensnitch/pull/207

@kyle.rankin Did you see https://bugs.debian.org/903163#135 ? :)

(Also needs python3-grpc package in Debian)

Ah, of course. Thanks!

So, I can't exactly figure out exactly which USB device, etc. I need to disable this for (presumbly the "root hub", but I can't reproduce that bit).. plus I managed to reproduce this with the internal trackpad so I've gone ahead and disabled application of the Powertop profile for now in purism-power-optimisations version 0.5.3.

megadown is now in PureOS, so closing. Thanks. Let me know if you need to update a new version, naturally.

Great stuff; this helps in tracking it down. On it..

Example logging output

Hi @johenry, thanks for filing this issue. Whilst I can't reproduce this, like
@mak I suspect this might be be the powertop parts of the purism-power-optmisations. After you reboot and you /cannot/ reproduce, can you try running powertop --auto-tune as root and let me know whether this causes the issue to return?

Today I've gotten two different explanations

Kyle, alas I think you are regrettably missing a lot of back-and-forth on this issue. The UK Librem 13 does have this issue in the sense that I needed to apply a /keyboard firmware/ update to fix it. No systemd patch could have possibly fixed it. There is nothing for me to apply now given that I applied the "BIOS"-level update.

Resolving.

Dear all,

Done :)

@mladen.pejakovic For what purpose? (What can he do here that I cannot?)

Thanks @jonas.smedegaard. Want me to handle this? (I see I remain assigned..)

(NB. reply on that Debian bug report)

Tempted to close this issue as there is no clear "next action". Any objections?

@mladen.pejakovic Hey hey, what's the status of this? I'm just wondering what my next steps here — the ticket is currently assigned to me, but I have no obvious 'next action' as far as I can tell.

It's in debian testing now.

See also: https://a13xp0p0v.github.io/2018/07/07/kconfig-hardened-check.html

Testing migration can be tracked here:

@kyle.rankin I have followed up to the bug (CC'd you)

• I contacted another FTP team member so this has been ACCEPTED in good time.

@vivia.nikolaidou Uploaded.

I just got confused because mentors.debian.net complains that 4.2.1 is too new

Just had a look - thanks! So, if you're running Lintian from sid then I don't understand why you still have:

@vivia.nikolaidou Please go ahead and drop the "contrib" etc. and let me know where I can do the review/upload. (Note that the very latest lintian is for 4.2.1... but I assume you are running Lintian from Debian sid...)

@vivia.nikolaidou Gentle ping :)

Also working on grpcio module packaging in the Python Modules team.

@vivia.nikolaidou What's the latest on this? Would love to get this settled up either way!

(Feel free to re-use this ticket if there is not already one.)

https://bugs.debian.org/906609

WIP here: https://salsa.debian.org/lamby/pkg-opensnitch

Blocked due to FBTFS in Debian on mips and s390x. Filed Debian bug.

@vivia.nikolaidou Remind me again why this is headed for contrib? AIUI this is "just" a generic downloader for the mega.nz sites, similar in kind to youtube-dl or even wget. I do see "closed protocol" given as a justification but it is not different (alas) than any of the third-party cloud infrastructure / Google / Yahoo / Dropbox APIs which are 100% free software.

(And sure, was just clarifying the "floating" pronoun there...)

have Purism redistribute it (not as part of PureOS, but) from the puri.sm domain.

Alas, I'm afraid I don't 100% follow that conversation. What does @jonas.smedegaard mean by "same hosting" - as in, upload directly to *PureOS* or for it to go via Debian.

I can still reproduce this with the image in https://downloads.puri.sm/playground/2018-08-10/

Also confirmed, as expected, with https://downloads.puri.sm/playground/2018-08-10/.

Restarting the installer, here is a screenshot of the checkbox

Wouldn't spend too long on the manpage -it is not 100% required.

And possibly some extra golang packages... :)

This will also require the packaging of (at least) the grpcio-tools Python package.

In T327#9870, @kyle.rankin wrote:

assumed that getting this packaged into PureOS would be faster than into Debian

Any update on this? :)

The first step here would be to getting it into Debian. I can handle this if you like; please assign me the ticket.

I get massive CPU activity and a black VBox screen.

Why are you deleting the package every time?

Because I'm not changing the version number.

Why are you deleting the package every time? That does not seem the usual approach or at least it has never been required before.

I did not see you had updated mentors.debian.net - there is no notificatin system there. Can you ensure that you ping back here when you post on there?

updated…

Sorry, I don't see it on https://mentors.debian.net/packages/index.

@vivia.nikolaidou Excellent question. I suggest you upload it directly to mentors.debian.net - that way you follow the process "just like" a regular contributor. I can comment on the package there.

Very good ideas. Indeed, I believe there is already a ticket regarding this but I can't find it right this second... feel free to create another. :)

Hi @seandiggity. Try pureos with no password. :)

Thanks. I have subscribed to this bug.

[Assinging ticket back]

Ah. That bit was unclear. :p

What are you expecting instead?

Oh neat. (But would we not get that patch/change if we just merged systemd?)

Jumping somewhat to a reasoned conclusion, given that the security for the most-common devices in/around the free software ecosystem (ie. Thinkpads) do not provide much security there has been a correspeonding lack of activity and effort put into the software.

As promised, I did a bit of research into these. The general consensus is that fingerprint readers are essentially insecure devices that give a false sense of security.

In T486#8954, @mladen.pejakovic wrote:

Yes, there was a typo. :)

So, I have a UK device and am not seeing this subsequent remapping. What, exactly, should I be looking for?

Sorry, I just realized I never replied: L15 is not affected, and only OSes with latest systemd are affected.

Fixed in https://source.puri.sm/pureos/core/pureos-meta/commit/d5c4459a71290fa0b0570e0d76b6b272d9fcf6f5

Hi all, just to clarify some things:

@francois Thanks. Shall we close this one up then? :)

(IIRC my question around adduser.conf was to ensure new users had it, but not sure)

Given that this is a) the default terminal and b) is *horrifically* ugly, this is giving new users a truly terrible first impression. :(