2021-02-15
00:27maor26 has quit [Ping timeout: 265 seconds]
01:04snalty has quit [Ping timeout: 240 seconds]
01:07kettenis has quit [Ping timeout: 240 seconds]
01:19kettenis has joined #asahi-dev
02:08riker77 has quit [Ping timeout: 264 seconds]
02:12riker77 has joined #asahi-dev
02:31dougall has joined #asahi-dev
02:56bgb has joined #asahi-dev
02:57bgb has left #asahi-dev [#asahi-dev]
03:05bgb has joined #asahi-dev
03:14PhilippvK has joined #asahi-dev
03:14phiologe has quit [Ping timeout: 260 seconds]
03:27bgbmarcan: how did you get mini hdmi output showed on your host screen by just typing "hdmi" shell cmd?
03:29KindOne has quit [Ping timeout: 240 seconds]
03:33KindOne has joined #asahi-dev
04:56Necrosporus has quit [Killed (orwell.freenode.net (Nickname regained by services))]
04:56Necrosporus has joined #asahi-dev
04:57narmstrong has quit [Ping timeout: 240 seconds]
04:58bgb has quit [Ping timeout: 272 seconds]
04:58hatf0 has quit [Read error: Connection reset by peer]
04:58jkkm has quit [Read error: Connection reset by peer]
04:58bgb has joined #asahi-dev
04:58eric_engestrom has quit [Ping timeout: 240 seconds]
04:58titanous has quit [Read error: Connection reset by peer]
04:58narmstrong has joined #asahi-dev
04:58hatf0 has joined #asahi-dev
04:58eric_engestrom has joined #asahi-dev
04:58jkkm has joined #asahi-dev
04:58titanous has joined #asahi-dev
05:15bgb has quit [Ping timeout: 246 seconds]
05:16bgb has joined #asahi-dev
05:20bgb has quit [Ping timeout: 240 seconds]
05:30bgb has joined #asahi-dev
06:15bgb has quit [Ping timeout: 256 seconds]
06:16bgb has joined #asahi-dev
06:21bgb has quit [Ping timeout: 246 seconds]
07:11VinDuv has joined #asahi-dev
07:28bgb has joined #asahi-dev
07:32bgb has quit [Ping timeout: 240 seconds]
07:34bgb has joined #asahi-dev
07:38bgb has quit [Ping timeout: 256 seconds]
07:40VinDuv has quit [Quit: Leaving.]
08:07arndtarzeau: the most likely path at the moment is that I'll create a separate branch in https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/ and pull in material for 5.13 as soon as it's been sufficiently reviewed and marcan sends it to soc@kernel.org. It will then show up in https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/ a day later, and in torvalds/linux.git during the 5.13 merge window
08:08arndhttp://phb-crystal-ball.org/ projects 5.13-rc1 for 2021-05-09, and the official 5.13 for 2021-07-04
08:09arndmarcan: no, don't cc soc@kernel.org on patches unless I they have been reviewed and are ready to get picked up
08:11arndno, if you get a bounce, please forward that to me at arnd@kernel.org and arnd@arndb.de (in case one of the two bounces as well)
08:12marcan<linux+soc@armlinux.org.uk> is bouncing, I figured you'd have gotten them too since I think replies CCed soc@ too
08:19marcanrunning the devicetree checks now.... and I need to decide if I set up DKIM first or not :)
08:53amw has quit [Ping timeout: 240 seconds]
09:00nhlism[m] has quit [Quit: Idle for 30+ days]
09:10thresh has quit [Remote host closed the connection]
09:10thresh has joined #asahi-dev
09:14Chainsaw has quit [Remote host closed the connection]
09:18odmir has quit [Read error: Connection reset by peer]
09:18thestr4ng3r has quit [Quit: ZNC 1.8.1 - https://znc.in]
09:19the-mentor has quit [Quit: Ping timeout (120 seconds)]
09:19thestr4ng3r has joined #asahi-dev
09:19odmir has joined #asahi-dev
09:19the-mentor has joined #asahi-dev
09:20snalty has joined #asahi-dev
09:20Gaelan_ has joined #asahi-dev
09:21Gaelan has quit [Read error: Connection reset by peer]
09:25maor26 has joined #asahi-dev
10:11arndj`ey: the process is to send an email to sfr to ask him to add a branch. What I did specifically is to have a 'for-next' branch and I merge all of my branches into that
10:15arndmarcan: do you have a git tree somewhere other than github.com that you can use for sending pull requests? For the initial merge, separate patches will be fine, but in general, I prefer pull requests, and github is slightly annoying: it's often really slow for pulling kernel trees for some reason, and its generally less trusted than an tree on kernel.org or one you host yourself
10:16marcanI can set something up real quick; I have git.marcan.st but that's on the wrong continent, I can make git.asahilinux.org happen :)
10:16arndmarcan: note that you can ask for a kernel.org account that allows you to host git trees and one email alias there once you are listed in the MAINTAINERS file and have a sufficiently connected gpg key
10:18marcanthat works too, though my gpg key isn't terribly well connected (and honestly I should probably rethink that thing and make a new one, it's kind of old)
10:19arndmarcan: ok either one of those is fine for pull requests, or you keep using separate patches until you have a kernel.org account
10:20j`eyarnd: is the mailing list process still the same with pull requests? just that you also have a branch on git somewhere?
10:21arndj`ey: yes, you just send an email with the subject containing [GIT PULL] instead of [PATCH], and the body generated by 'git request pull', and pointing to a tag with gpg signature and a description
10:22marcanoh, it's 4K, it's not *that* old, but I've never been terribly happy with the security of it, especially considering I do better in other places these days (e.g. yubikeys)
10:22marcanbut SSH and U2F let me use many yubikeys, while I can only have one gpg key... and I don't want to mix GPG and SSH usage...
10:23j`eyarnd: I see, I'd only seen that (so far) for requesting Linus to pull, not indudvidual series that needed review
10:24arndj`ey: review is always by email on the list, the pull request is what you'd send once the series is fully reviewed and ready to be merged. I usually do some final checks on the pull request to make sure the contents match up with the description, and the signature is valid then
10:28marcanyeah, for signing kernel tags honestly that's probably the easiest way, it would just be a key dedicated-ish to that; I just don't want to make that "my" gpg key for email/etc, because then that ties me to the physical thing
10:29marcanI should dig up that ROCA-vulnerable yubikey from a drawer somewhere; those are fine if you import keys externally, which I would want to do to keep an offline backup anyway (I don't mind having a backup, I have a pretty safe place for that stuff, as long as I don't have to access it normally)
10:35arndmarcan: regarding signatures on the key, the document I linked to says you need at least one signature from someone who is connected to torvalds, but IIRC the requirement for getting a kernel.org account is three such signatures. If you have trouble finding kernel folks to sign your kernel locally, we can probably arrange for me to sign your kernel through some video chat
10:44arndmarcan: no, I'm happy to apply the patches from email, or by applying with the same amount of care when I get a pull request
10:45marcanI'll send out v2 shortly then, and spend some time this week giving a bit of thought to this
10:46arndand once I pulled from you once, I would generally also assume it's fine if future pull requests are signed by the same key. The 'one connected signature' requirement is specifically if you send a pull request to torvalds yourself
10:47arndmaybe check if any of the people that signed your old key are already on the kernel keyring
11:02bgb has joined #asahi-dev
11:07bgb has quit [Ping timeout: 240 seconds]
11:23maximus64I also used yubikey for my gpg key and I keep my master key offline on air gap computer. Downside to this is everytime you need to renew or sign other keys, I have to do it on the offline computer
11:29bgb has joined #asahi-dev
11:30Necrosporus has quit [Ping timeout: 246 seconds]
11:37bgb has quit [Ping timeout: 264 seconds]
11:56bgb has joined #asahi-dev
12:05bgb has quit [Ping timeout: 265 seconds]
12:49bgb has joined #asahi-dev
13:08bgb has quit [Ping timeout: 240 seconds]
13:10bgb has joined #asahi-dev
13:17bgb has quit [Ping timeout: 265 seconds]
13:56modwizcodeI've tried a few times to maintain a key and I always lose it, but I don't have much reason to use it for anything.
13:57modwizcodeI think my current key is actually safe, when keybase came out I setup everything so that worked. So keybase has an encrypted copy of my key and I think I have a backup printout and the password I actually remember.
13:57modwizcodeI think that's how that all works
13:57modwizcodeGPG is kind of meaningless without signatures on your key and people to use it with
14:15bgb has joined #asahi-dev
14:15bgb has left #asahi-dev [#asahi-dev]
14:27marcan_ has joined #asahi-dev
14:28marcan_ has quit [Client Quit]
14:38Necrosporus has joined #asahi-dev
14:47maor26 has quit [Ping timeout: 265 seconds]
15:23svenI have an offline master key with subkeys on yubikeys (signing/authentication ones generated on the device, encryption key imported with an offline backup). the only two things I used it for are ssh and encrypted backups
15:24hir0 has joined #asahi-dev
15:27hir0 has quit [Quit: hir0]
15:35sven- has joined #asahi-dev
15:37sven has quit [Ping timeout: 246 seconds]
15:37sven- is now known as sven
15:38hir0 has joined #asahi-dev
16:16bisko has joined #asahi-dev
17:13bisko has quit [Quit: Textual IRC Client: www.textualapp.com]
17:32Glanzmannmarcan: If you have a yubikey with the broken random number generator, you could apply for a new. This is how I got two new yubikeys for free.
17:34Glanzmannmarcan: I had for a very long time my gpg key, and still have, but no longer use it, on a yubikey. I did with three keys, one master, one for authentication, one for signature. I still use it for ssh also. I sometimes have to work on windows. where there is no good gpg agent forwarding, so I can't use gnupg remotely. If I should send you my notes, let me know.
17:35GlanzmannIf you guys need help with mutt, let me know. I wrote 17 years ago or so the mutt header cache and I'm a mutt power user. I also configured vim to strip consecutive empty lines out and do other stuff that is helpful for inline answering.
17:39GlanzmannNitrokeys are nice, I read about them earlier, I think, but they did not support 4Kbit RSA which I sue for quite a while.
17:39marcanbut it makes sense to use it for a master key with a backup, because then you're generating keys externally anyway, so the bug does not matter
17:39GlanzmannMy old one broke down, so I replaced it with a new one. the one that you put in the usb slot and does not look out.
17:40GlanzmannI only remeber, that when you gernate keys on it, they're weak. But I would never do it, because devices break or get lost.
17:41marcanI also use them for OATH TOTP and for that, I always put the seeds into two, so I have a backup
17:43VinDuv has joined #asahi-dev
17:56marcanGlanzmann: re nitrokey, it's not fully open source; not the proper secure element ones anyway
17:57marcansame proprietary NDA'd SE as everything else, also the open code for the SE is written in... BASIC.
18:01nkaretnikov has quit [Ping timeout: 264 seconds]
18:02eric_engestrom has quit [Ping timeout: 272 seconds]
18:02nkaretnikov has joined #asahi-dev
18:02titanous has quit [Ping timeout: 264 seconds]
18:02eric_engestrom has joined #asahi-dev
18:02titanous has joined #asahi-dev
18:03HeN has quit [Ping timeout: 260 seconds]
18:04HeN has joined #asahi-dev
18:04marcanthe first semi serious one I've seen so far is solo v2: https://www.kickstarter.com/projects/conorpatrick/solo-v2-safety-net-against-phishing
18:04marcanthat one is, as far as I can tell, fully open source, and using a micro which claims some amount of security
19:05hir0 has quit [Ping timeout: 265 seconds]
19:29marcanand it's updatable (though only by them if you get the "normal" version, by you if you get the "hacker" version)
19:29marcanand supposedly you can provision secureboot yourself for the latter, i.e. make it only run code you sign
19:32hir0 has joined #asahi-dev
20:32hir0 has quit [Quit: hir0]
20:40hir0 has joined #asahi-dev
20:42hir0 has quit [Client Quit]
20:50VinDuv has quit [Quit: Leaving.]
21:34leah2 has quit [Ping timeout: 264 seconds]
21:43leah2 has joined #asahi-dev
22:16sbingner has quit [Ping timeout: 258 seconds]
22:25sbingner has joined #asahi-dev
22:54JTL has quit [Quit: WeeChat 2.9]
22:54JTL has joined #asahi-dev
22:54JTL has quit [Client Quit]
22:55JTL has joined #asahi-dev
22:59JTL is now known as JLT
23:29amw has joined #asahi-dev
23:32JLT is now known as JTL