Some have rolled their eyes at the "paranoid" requirement from the #Debian community of in-person gpg key signing as a step to become a Debian developer, and it's often been a real barrier.

But I'm reminded of it at the #OSSummit keynote today as the #Linux Foundation's Jim Zemlin talks about the xz vulnerability and identity verification of developers.

It was never paranoia. It doesn't solve everything, and people can still be dishonest, but it was never excessive paranoia.

@pleia2 to be honest, i don't see the point of it. a threat actor can send somebody from their group to go get their signing key signed by other developers, after all.
@ariadne It's true, but there are a lot of additional barriers there, including visas, travel, and generally the extra layer of complexity that representing yourself in person brings (basically all the reasons people have brought up against it over the years). This may not mean much when a huge investment is made by a state actor already, but it's something.

@pleia2 @ariadne I guess the concern would be that a nation state actor with significant resources has much *more* of an ability to deal with most of those barriers than a genuine volunteer contributor usually does.

(While someone without such resources mostly isn't going to be doing an elaborate long-term attack like this.)

So it's not paranoid, but it's unclear how much it would help.

@ids1024 @pleia2 @ariadne You have to come out into the open. Meet people who might then be able to identify you. So it fixes an identity more to one person.

@waldi @ids1024 @pleia2 does it though? i am sure an alphabet soup agency can just designate one physical person to run point on any in-person interactions with the APT.

i guess i am just not convinced that this has any meaningful defense against APTs who can likely issue fake travel docs any time they want.

what the cross-signing *does* help with is ensuring that no single party controls all of the signing keys used for Debian. but in practice, the reason why that is important is largely tied to how Debian-like distributions ingest source code to create debs.

(and nothing stops an APT from just going through mentors.debian.org just like nothing stops an APT from just submitting PRs to aports and finding a useful person to unwittingly merge them into Alpine)

@ariadne @waldi @pleia2 It would probably be most useful if the people meeting had communicated a lot online. In the case of xz, if "Jia Tan" met in person with Lasse Collin, and they talked much about plans with xz, it may become suspicious if "Jia" doesn't act very knowledgeable about xz, or even their own work, and speaks quite differently from how they do online.

So it may be hard to send someone else. Which is at least some kind of barrier.

I'm not familiar with how this works in Debian.

@ids1024 @ariadne @waldi @pleia2 There are definitely people in Debian who'll only sign keys of people they know non-superficially (i.e. not just waving a passport at them or something). Practices vary, though - it's a big project.
@cjwatson @ids1024 @waldi @pleia2 yeah like every other web of trust system it ultimately comes down to a decision made by the individual participant in any given moment.