Replace HTTP links with HTTPS ones: Documentation/filesystems
Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Deterministic algorithm: For each file: If not .svg: For each line: If doesn't contain `\bxmlns\b`: For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`: If both the HTTP and HTTPS versions return 200 OK and serve the same content: Replace HTTP with HTTPS. Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> Link: https://lore.kernel.org/r/20200621133552.46371-1-grandmaster@al2klimov.de Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
d3603f4c30
commit
c69f22f25f
|
@ -76,7 +76,7 @@ Creating HFS filesystems
|
|||
|
||||
The hfsutils package from Robert Leslie contains a program called
|
||||
hformat that can be used to create HFS filesystem. See
|
||||
<http://www.mars.org/home/rob/proj/hfs/> for details.
|
||||
<https://www.mars.org/home/rob/proj/hfs/> for details.
|
||||
|
||||
|
||||
Credits
|
||||
|
|
|
@ -7,7 +7,7 @@ Read/Write HPFS 2.09
|
|||
1998-2004, Mikulas Patocka
|
||||
|
||||
:email: mikulas@artax.karlin.mff.cuni.cz
|
||||
:homepage: http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi
|
||||
:homepage: https://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi
|
||||
|
||||
Credits
|
||||
=======
|
||||
|
|
|
@ -10,12 +10,12 @@ purposes of authentication.)
|
|||
|
||||
RPCGSS is specified in a few IETF documents:
|
||||
|
||||
- RFC2203 v1: http://tools.ietf.org/rfc/rfc2203.txt
|
||||
- RFC5403 v2: http://tools.ietf.org/rfc/rfc5403.txt
|
||||
- RFC2203 v1: https://tools.ietf.org/rfc/rfc2203.txt
|
||||
- RFC5403 v2: https://tools.ietf.org/rfc/rfc5403.txt
|
||||
|
||||
and there is a 3rd version being proposed:
|
||||
|
||||
- http://tools.ietf.org/id/draft-williams-rpcsecgssv3.txt
|
||||
- https://tools.ietf.org/id/draft-williams-rpcsecgssv3.txt
|
||||
(At draft n. 02 at the time of writing)
|
||||
|
||||
Background
|
||||
|
|
|
@ -69,7 +69,7 @@ pathname that is just slashes have a final component. If it does
|
|||
exist, it could be "``.``" or "``..``" which are handled quite differently
|
||||
from other components.
|
||||
|
||||
.. _POSIX: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12
|
||||
.. _POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_12
|
||||
|
||||
If a pathname ends with a slash, such as "``/tmp/foo/``" it might be
|
||||
tempting to consider that to have an empty final component. In many
|
||||
|
@ -376,7 +376,7 @@ table, and the mount point hash table.
|
|||
Bringing it together with ``struct nameidata``
|
||||
----------------------------------------------
|
||||
|
||||
.. _First edition Unix: http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/u2.s
|
||||
.. _First edition Unix: https://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/u2.s
|
||||
|
||||
Throughout the process of walking a path, the current status is stored
|
||||
in a ``struct nameidata``, "namei" being the traditional name - dating
|
||||
|
@ -1265,7 +1265,7 @@ Symlinks are different it seems. Both reading a symlink (with ``readlink()``)
|
|||
and looking up a symlink on the way to some other destination can
|
||||
update the atime on that symlink.
|
||||
|
||||
.. _clearest statement: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_08
|
||||
.. _clearest statement: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_08
|
||||
|
||||
It is not clear why this is the case; POSIX has little to say on the
|
||||
subject. The `clearest statement`_ is that, if a particular implementation
|
||||
|
|
|
@ -246,15 +246,15 @@ If you don't already understand what shared libraries, devices, and paths
|
|||
you need to get a minimal root filesystem up and running, here are some
|
||||
references:
|
||||
|
||||
- http://www.tldp.org/HOWTO/Bootdisk-HOWTO/
|
||||
- http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html
|
||||
- https://www.tldp.org/HOWTO/Bootdisk-HOWTO/
|
||||
- https://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html
|
||||
- http://www.linuxfromscratch.org/lfs/view/stable/
|
||||
|
||||
The "klibc" package (http://www.kernel.org/pub/linux/libs/klibc) is
|
||||
The "klibc" package (https://www.kernel.org/pub/linux/libs/klibc) is
|
||||
designed to be a tiny C library to statically link early userspace
|
||||
code against, along with some related utilities. It is BSD licensed.
|
||||
|
||||
I use uClibc (http://www.uclibc.org) and busybox (http://www.busybox.net)
|
||||
I use uClibc (https://www.uclibc.org) and busybox (https://www.busybox.net)
|
||||
myself. These are LGPL and GPL, respectively. (A self-contained initramfs
|
||||
package is planned for the busybox 1.3 release.)
|
||||
|
||||
|
|
|
@ -433,9 +433,9 @@ will then have to be provided beforehand in the normal way.
|
|||
References
|
||||
==========
|
||||
|
||||
[CRYPTSETUP2] http://www.saout.de/pipermail/dm-crypt/2017-November/005745.html
|
||||
[CRYPTSETUP2] https://www.saout.de/pipermail/dm-crypt/2017-November/005745.html
|
||||
|
||||
[DMC-CBC-ATTACK] http://www.jakoblell.com/blog/2013/12/22/practical-malleability-attack-against-cbc-encrypted-luks-partitions/
|
||||
[DMC-CBC-ATTACK] https://www.jakoblell.com/blog/2013/12/22/practical-malleability-attack-against-cbc-encrypted-luks-partitions/
|
||||
|
||||
[DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst
|
||||
|
||||
|
|
|
@ -1431,13 +1431,13 @@ Resources
|
|||
version.)
|
||||
|
||||
Creating Linux virtual filesystems. 2002
|
||||
<http://lwn.net/Articles/13325/>
|
||||
<https://lwn.net/Articles/13325/>
|
||||
|
||||
The Linux Virtual File-system Layer by Neil Brown. 1999
|
||||
<http://www.cse.unsw.edu.au/~neilb/oss/linux-commentary/vfs.html>
|
||||
|
||||
A tour of the Linux VFS by Michael K. Johnson. 1996
|
||||
<http://www.tldp.org/LDP/khg/HyperNews/get/fs/vfstour.html>
|
||||
<https://www.tldp.org/LDP/khg/HyperNews/get/fs/vfstour.html>
|
||||
|
||||
A small trail through the Linux kernel by Andries Brouwer. 2001
|
||||
<http://www.win.tue.nl/~aeb/linux/vfs/trail.html>
|
||||
<https://www.win.tue.nl/~aeb/linux/vfs/trail.html>
|
||||
|
|
Loading…
Reference in New Issue