I 'know' whissi, but i have never met them and may never meet them.) How do you generate a WoT when your web members never meet? Its nominally against the tradition of meeting people in person and verifying their identity (to establish a trust signature.) The procedure for signing is typically quite variable and so we tend to impose an onerous one (e.g. I think the struggle is that there is limited interest in our side in making this work. > dont you know each other ? would _really_ help me. > well, it would if you would trust for example: > I'm afraid I can't say much beyond "WoT doesn't really work ". > (In reply to Michał Górny from comment #6) > (2) You could easily just trust BB572E0E2D182910 but my assumption is that so i do not have a path down to the signing key of the ISO The signing key above is only self signed, and the L1 key does not sign this key. > output.but I have no idea what your conclusion is. > My impression is that you concluded something based on the list-sigs > (1) Why do you think you can't verify the key via WoT? (In reply to Alec Warner from comment #2) (2) You could easily just trust BB572E0E2D182910 but my assumption is that you expect some other procedure? My impression is that you concluded something based on the list-sigs output.but I have no idea what your conclusion is. (1) Why do you think you can't verify the key via WoT? > sig BB572E0E2D182910 Gentoo Linux Release Engineering > sig 3 BB572E0E2D182910 Gentoo Linux Release Engineering > uid Gentoo Linux Release Engineering (Automated Weekly > i only get a key which is not verifiable in WOT. > i am trying to verify the install iso file. Sig BB572E0E2D182910 Gentoo Linux Release Engineering (Automated Weekly Release Key)
Sig 3 BB572E0E2D182910 Gentoo Linux Release Engineering (Automated Weekly Release Key)
Uid Gentoo Linux Release Engineering (Automated Weekly Release Key) I only get a key which is not verifiable in WOT. I am trying to verify the install iso file.
0 kommentar(er)
