> Do you remember what triggered the installation of tmp2-abrmd?
The most likely is I have just installed it manually late 2017, or
2018 when I started playing with the tpm2 setup for FDE following
guidance from some documentation. I will not recall any more details
after so much time.
> I thought these days in-kernel resource management was preferred? Any
> reason you were using abrmd?
I just still had it installed already for a long time since times where most
places were suggesting using it and never dropped.
Thank you for fixing it!
Package: systemd
Version: 252-2
Severity: important
X-Debbugs-Cc: marekrusinow...@gmail.com
Dear Maintainer,
In systemd 252 a new tool systemd-pcrphase got included that
measures PCR values at different boot stages. When tpm2-abrmd is
installed in the system, the sysinit stage of that tool
Christoph Biedl wrote:
> In case you haven't noticed yet, that was fixed in clevis 15-3 a few
> days ago. There's alreaddy 15-4 which should reach testing in two days.
I've updated the system with clevis tpm2 setup today and all works
fine end to end with 15-4.
Thank you!
Marek
Hi Christoph,
The upstream.work-around-missing-dev-fd-links.patch doesn't
work for the tpm2 pin yet.
You replaced exec with a child process but in this case the on_exit trap
continues to run and the decryption with tpm2 pin will always fail with
Delete temporary files failed!
You need to clean
Hi,
> Also, I'd be glad to learn
> about success (failure as well) - as I currently have no hardware with
> TPM support around and swtpm creates a lot of strange error messages
> I cannot follow, I'm currently somewhat blind.
I've built the source version you uploaded (need to report one bug in
Package: clevis-tpm2
Version: 13-2
Severity: important
Dear Maintainer,
It looks like currently the clevis-tpm2 is incompatible with
tpm2-tools package in unstable (5.0-1). After trying to encrypt
something with tpm2 I get:
The tpm2 pin requires tpm2-tools version 3 or 4
It looks like it was
I have this problem too and opened a duplicate #939773 earlier with some
investigation. Rephrasing my investigation from that duplicate:
In this kernel MOK key gets inserted into the .platform keyring (I see
CONFIG_INTEGRITY_PLATFORM_KEYRING is set to true in the kernel config) which
isn't used
Sorry, this is a duplicate of #935945
and
builtin_trusted_keyring to verify modules signatures.
Thank you,
Marek Rusinowski
Hi
I have run into the same problem. I can't add anything, only video of how
it looks like on my system: https://youtu.be/4Fxuzm-FvbE
Marek
On Thu, 23 Jul 2015 21:19:08 +0200 Roland Kammerer dev@gmail.com
wrote:
I suffer from the same problem (gdm3/3.14.1-8). Today I updated to the
current version in sid (gdm3/3.14.2-1) but no change.
$ lspci |egrep VGA
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U
On Fri, 21 Nov 2014 00:06:11 -0800 Vincent Cheng vch...@debian.org wrote:
On Wed, Nov 19, 2014 at 4:36 AM, Marek Rusinowski
marekrusinow...@gmail.com wrote:
On Fri, 12 Sep 2014 13:13:43 +0200 Christian Lachner
christian.lach...@gmail.com wrote:
Hello everybody,
jkwong888 at https
On Fri, 2014-11-21 at 00:56 -0800, Vincent Cheng wrote:
Hi Marek,
On Fri, Nov 21, 2014 at 12:38 AM, Marek Rusinowski
marekrusinow...@gmail.com wrote:
On Fri, 21 Nov 2014 00:06:11 -0800 Vincent Cheng vch...@debian.org wrote:
On Wed, Nov 19, 2014 at 4:36 AM, Marek Rusinowski
marekrusinow
bumblebee 3.2.1-7
xserver-xorg 1:7.7+7
xserver-common 2:1.16.1.901-1
And unfortunately after appending those lines nothing changed. I have got
same error and I'm unable to run programs using optirun.
Marek Rusinowski
Hi
Unfortunatelly I have this same problem, it looks like I have this same
version of driver, bumblebee etc.
$ lspci | grep NVIDIA
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GTX
660M] (rev a1)
Best Regards,
Marek Rusinowski
Duplicate of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756164
'
PS. I hope I'm reporting this to correct place, in correct form etc.
Best Regards,
Marek Rusinowski
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures
18 matches
Mail list logo
