/srv/irclogs.ubuntu.com/2016/05/19/#ubuntu-kernel.txt

=== tai271828_ is now known as tai271828
=== pkern_ is now known as pkern
=== JanC is now known as Guest23785
=== JanC_ is now known as JanC
rtgtseliot, have you built nVidia against a 4.6 kernel yet ? we've got one for you in the yakkety pocket of https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa13:00
tseliotrtg: I have built 361 with a patch for 4.6, and I'll use that kernel for testing now, thanks13:38
rtgtseliot, great!13:38
tseliotrtg: ok, the patch seems to need more work. I'll let you know when it's ready14:15
rtgtseliot, ack14:23
Laneyanyone know of a guide that'll tell me how to make dkms sign modules it builds?20:39
apwLaney, sign them with what20:42
Laneythis key that I made20:42
Laneyand then added to the mok thingy20:42
apwLaney, i know of no existing mecahnaism for that20:42
Laneywl.ko is now signed so I'm at least online :)20:42
Laneybut the next kernel will I guess not have that20:43
apwno indeed, but having the signing key on the machine seems like a lawed security position20:43
Laneyit's at least root only20:44
LaneyI haven't thought about this *that* much20:44
rtgLaney, https://docs.google.com/document/d/1Z1_jR3MmxuvqolQH4PORkJCgENkb2Tlw4FVA-sHqdMw20:44
apwrtg, i think he has done the equivalent of that20:45
Laneyyeah20:45
rtgI think cyphermox is working on the user space components for DKMS signing20:45
Laneyokay, so not there yet20:46
apwis there any sane configuration where you have the signing key on disk?  if you do you might as well just turn secure boot of at MOK ?20:46
LaneyI should read aout the arguments around this signing stuff20:46
LaneyI suppose it's something like -20:54
LaneyThe key database is 'secure' even in the face of the system being rooted20:54
Laneyand so an attacker that has root wouldn't be able to make the kernel load things if they don't have the signing key20:55
apwin theory, the practice is much less clear20:55
Laneythen you have to never let the private key touch the machine20:56
apwright and that part is what makes the dkms side difficult20:57
Laneyquite an interesting problem20:58
Laneywould be keen to see the spec cyphermox is working to if there is one20:58
Laneyalso I managed to get upgraded to a kernel which refused to load wl.ko20:58
apwi am unclear of the bigger picture inthe plan20:58
Laneywithout knowing that it was going to happen in advance, so I rebooted and had no network20:59
Laneythat was a bit sad20:59
apwyes, out of tree drivers are not first class citizens in a lot of ways,secure boot is one of them20:59
apwthoughyou should have been told to turn off secure boot because dkms was installed20:59
apwbut perhaps that is only done as we transition from no dkms -> dkms installed21:00
apwhmmm21:00
Laneyperhaps update-manger or the release upgrader would have done that21:00
apwthe dkms asking you to disable secureboot via mok happens as part of dkms installing even at the command line21:01
apwbut perhaps not on upgrades or something21:01
LaneyI can't rule out that I missed or ignored it either21:02
* Laney checks dkms21:02
rtgLaney, I've gotten a couple of reports of basically the same thing happening21:02
Laneyrtg: Hmm21:08
LaneyIt's confusing now because cyphermox moved to a new script in yakkety21:08
Laneyand I didn't have a new enough shim-signed to have the "update-secureboot-policy" thing installed21:08
Laneyso I wouldn't have been prompted to disable it21:08
Laney*however* I should have seen the old debconf questions21:09
rtgLaney, I think upgrading Wily to Xenial definitely has issues21:09
Laneywhich have now been unregistered by the new dkms21:09
Laneyso probably out of luck to find out what happened to me21:09
apwLaney, man its a minefiled21:09
Laneywarrants some testing for sure21:09
Laneyget that davmor2 on it21:09
Laneyapw: Be glad you're not on the front line of this one :)21:10
cyphermoxLaney: what's the issue?21:13
* cyphermox reads backlog21:14
Laneyhey cyphermox 21:14
LaneyI may not have been asked to disable SB but can't prove it any more21:14
Laneyand also was wondering if there's a story about signing for dkms21:15
cyphermoxLaney: you're not the first to mention it; I remember Steve pinged me a few weeks ago about not being prompted on upgrade, but being prompted afterwards when it probably should not, but that was also unreproducible21:16
cyphermoxLaney: tbh I don't know how to sign the modules, do we have a userland too to do that?21:17
LaneyThere's some script shipped by the kernel21:17
cyphermoxwell, I suppose we do, the question is more, do we ship it and is it usable by the common mortal21:17
cyphermoxright21:17
Laneysudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der /lib/modules/4.4.0-23-generic/updates/dkms/wl.ko21:17
rtgapw has update sbsign to include the module signing tool21:17
apwsbsigntool includes kmodsign in the versions in -proposed21:18
cyphermoxI haven't really looked into that yet -- the story to start with was to either have free things and all signed with our kernel package, or have third-party drivers and disable shim validation21:18
cyphermoxah, great21:18
cyphermoxLaney: the SB disabling should only prompt if it can see that you're booting with secure boot enabled and that it's not already disabled21:19
Laneyyeah I am in that situation21:19
Laneyright chaps21:20
Laneythanks for educating me a bit while I was cooking me dinner21:20
Laneyit is now ready - ttyl :)21:20
cyphermoxLaney: ping me later and we can chat more about it21:20
Laneysure21:20
Laneysee you!21:20

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!