Bug 1217734 - Insecure network installation instructions
Summary: Insecure network installation instructions
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: install-guide
Version: devel
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-01 12:50 UTC by e
Modified: 2024-05-21 09:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-21 09:21:52 UTC
Embargoed:


Attachments (Terms of Use)

Description e 2015-05-01 12:50:45 UTC
Description of problem:

The install guide specifies to download the kernel/initrd for PXE boots over an unencrypted connection and skips any form of verification.

Version-Release number of selected component (if applicable):
N/A

How reproducible:
100%

Steps to Reproduce:
1. Follow instructions:

https://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/pxe-kernel.html

(note the wget URLs)

Actual results:
If just a single network between my machine being booted and the Red Hat download server is malicious, then my machine could get 0wned :( (and I would probably be none the wiser)

Expected results:
To be able to securely install an operating system in 2015 on my new hard drive in a single evening without crying in despair.

And to not have a deep dark fear that the instructions on the previous page
are also horribly insecure:

https://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/pxe-bootloader.html

(I really hope those stage2 and root lines verify the image that is downloaded)

Comment 1 Petr Bokoc 2024-05-21 09:21:52 UTC
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.


Note You need to log in before you can comment on or make changes to this bug.