Posts
4524
Following
316
Followers
478
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1
heck maybe it would be even possible to fixup "knowingly known cryptographic material" that would be fixed up also to the qemu code base to which Intel's and AMD's servers would respond as legitimately.or maybe salt somehow to stamp the fake stamp. like just for infrasturcuture QA type of stuff use.

this is not an issue in the CA part as e.g. AMD already today has a rate-limited attestation paradigm. so yeah i think really would make sense for companies to spend money for fixing up this.
1
0
0
for instance you could run CI test in Gitlab/Github runner running kselftest with confidential computing part just emulated and "unattested".
1
0
0
there is only one thing actually that will fail and it is remote attestion because no legit cryptographic material but remote attestation is irrelevant for kernel testing (for the most part at least).
1
0
0
95% of KVM and 5% qemu emulation in non-performance sensitive task (which neither is in kernel patch or patch set scale when tested as part of review process)
1
0
0

Jarkko Sakkinen

imho at least qemu would need snp and tdx emulation in upstream for like testing patches. i mean most have x86 so even rigged emulation would do the job for trivial patch testing
1
0
0
So apparently (after searching) there is previous work https://patchwork.kernel.org/project/keyrings/cover/20200518172704.29608-1-prestwoj@gmail.com/. So I guess I just use some of it (and make it a separate patch with appropriate credits).
1
0
0
Also a bit unclear what is best bet for authentication but it is a non-concern for RFC.

One possible argument for just authentication value at most would be that LUKS2 already blesses with TPM2 policy and kernel communicates by using null seed derived key. Using policy adds robustness but is it worth of added complexity to have two layers of policy, I really don't know at this point.
1
0
0

Jarkko Sakkinen

Edited 1 year ago
OK, now I have together ASN.1 parsing and new key subtype "tpm2_key_subtype", which is foundations for TPM2 asymmetric keys.

Only compile-tested ;-) This is now bare minimum to trial in QEMU. Lot's of dance relocating necessary bits of trusted keys code to the TPM driver (only ASN.1 parser at this point).
1
0
0
weekend as a kind of freelancer (at least for some time) is the best time for own patches. on plus, you don't have to care anything but the solving problem itself... paid or unpaid i enjoy this ;-)
1
0
1

SDL3 Adds PipeWire Camera Support

Adding to the growing list of features coming with the SDL3 release for this hardware/software abstraction layer commonly used by cross-platform games and other software is PipeWire camera capturing support...
https://www.phoronix.com/news/SDL3-PipeWire-Camera-Capture

0
3
1

Jarkko Sakkinen

#Amaranth sounds like a name of a black/death metal band from Scandinavia but is actually pretty neat hardware (#FPGA) synthesis framework:

https://amaranth-lang.org/docs/amaranth/latest/intro.html
0
0
0

Jarkko Sakkinen

working on RFC patch for TPM2 asymmetric keys (will use null seed encrypted session) for supporting x509: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?h=tpm2_key

https://datatracker.ietf.org/doc/draft-woodhouse-cert-best-practice/
1
0
0
@jmorris FPGA is great optimization for latency/frequency (e.g. audio, router and such) rather than throughput, which can be often achieved just by upgrading the SoC (which is usually cheaper).
0
0
1
And it sort of makes sense too. Communicating complex technical topics through Internet is always a non-trivial task, no matter how it is orchestrated.
0
0
0
What is the most difficult task in kernel development? Emails ;-)

That said,it is still the best available in my opinion :-) Email archives are much nicer to backtrack even multiple years behind than these crazy Git issue trackers. I.e. there is a clear timeline in communications.
1
0
2

Jarkko Sakkinen

Edited 1 year ago
@jmorris off-topic but i have this sound card called "RME BabyFace Pro FS". it has pretty cool idea for FPGA's: the mixer is an FPGA. With this topology it can reach 1 ms latency for audio. And i.e. a firmware update contains also potentially update for the FPGA. Pretty clever hybrid approach IMHO.

Before I got this sound card I was not really sure where application wise it would make sense to have e.g. a SoC combined with FPGA but this product made me understand it a bit better.

I also own one small lattice FPGA. As soon as I get an idea how to use it e.g. with RPi for similar hybrid thing I'll definitely will PoC something. Lattice's have the benefit of having open source FPGA stack and since I also have a SoC FPGA does not have to have too many logic ports.
2
1
1

Jarkko Sakkinen

Edited 1 year ago
@jmorris off-topic but i have this sound card called "RME BabyFace Pro FS". it has pretty cool idea for FPGA's: the mixer is an FPGA. With this topology it can reach 1 ms latency for audio. And i.e. a firmware update contains also potentially update for the FPGA. Pretty clever hybrid approach IMHO.

Before I got this sound card I was not really sure where application wise it would make sense to have e.g. a SoC combined with FPGA but this product made me understand it a bit better.

I also own one small lattice FPGA. As soon as I get an idea how to use it e.g. with RPi for similar hybrid thing I'll definitely will PoC something. Lattice's have the benefit of having open source FPGA stack and since I also have a SoC FPGA does not have to have too many logic ports.
2
1
1

Jarkko Sakkinen

Edited 1 year ago
probably will get some feedback from linus but i'm in middle of changing my process (by request), so i'll just then apply learnings to 6.11 🤷
1
0
1
Show older