Hi Rodrigo, On Tue, May 21, 2024 at 12:53:10PM GMT, Rodrigo Campos wrote: > On 5/21/24 12:31 PM, Alejandro Colomar wrote: > > On Tue, May 21, 2024 at 11:08:58AM GMT, Rodrigo Campos wrote: > > > There is no online html version of this, right? Not even after the recent > > > 6.8 release? > > > > Yes, there is. We publish a PDF book for each release at: > > <https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/book/> > > <https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/book/man-pages-6.8.pdf> > > > > with a copy also available at my own server: > > <https://www.alejandro-colomar.es/share/dist/man-pages/6/6.8/man-pages-6.8.pdf> > > > > And if you want to check an online version of git HEAD (like this case, > > since the patch was applied after the release), it's available in my own > > sever: > > Nah, the patch was included in 6.8 :) True. cgit confused me. :) > > <https://www.alejandro-colomar.es/share/dist/man-pages/git/HEAD/man-pages-HEAD.pdf> > > > > You will find that my SSL cert is self-signed. It's documented here: > > <https://www.alejandro-colomar.es/ssl>. You can use HTTP links to avoid > > it, or add my certificate to your browser exceptions. > > Oh, thanks. Pointing to a specific release is not very useful for > documentation, as I want it to point to the latest version so users can see > which fs support idmap mounts on which kernels, I don't want to update the > link every time there is a man-pages release. > > Also, in 2024 pointing to a site with self-signed cert is not something I'm > not willing to do in the Kubernetes documentation. I guess you meant s/not something I'm not willing/something I'm not willing/ Is then HTTP okay for you? MY website works with HTTP just fine, and doesn't try to switch to HTTPS (but browsers these days got dumber and may force HTTPS). Or do you need something from me? It wasn't clear to me from your response. I might be able to set up hardlinks in <kernel.org> with kup(1) to have <.../man-pages-latest.pdf> if HTTP doesn't work for you. I'd need to manually update it at every release, though (but I guess it's not that bad). > I understand your issues > with CA, but self-signed for this context is definitely not better. > > And don't worry, if a CA does indeed impersonate you, no one will realize it > as the cert will just be trusted. I see the 'Connection not secure' logo as a security feature. :D If I see my website as trusted, it's actually the other way around. Of course, only those who remember me using a self-signed cert will notice. But that's true of any impersonation. Anyway, hopefully nobody will trust my website at all, because there's nothing important in it, other than the git(1) repos and the documents, all of which are PGP-signed. This is just my grain of sand to take down the CA system. > Maybe only users that remember you use > self signed might suspect, but maybe they will think you use a signed cert > already ;) Even if I ever switch to a signed cert, I will provide my detached signature to it. If a cert doesn't have a PGP signature from me, suspect. ;) > > Thanks a lot anyways! > Rodrigo Have a lovely day! Alex -- <https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
