[Bug 1266693] New: 3.3.1 Verifying checksums on Windows systems not correct
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1266693
Bug ID: 1266693
Summary: 3.3.1 Verifying checksums on Windows systems not
correct
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: fran_hermida(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Powershell command for getting expected checksum not correct:
$expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern
$image) -split " ")[0].ToLower()
Should be:
$expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern
$image) -split " ")[3].ToLower()
since checksum file content is:
SHA256 (Fedora-Live-Workstation-x86_64-22-3.iso) =
615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months
[Bug 1282226] New: Incorrect Commands for Verifying Checksums on Windows 10
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1282226
Bug ID: 1282226
Summary: Incorrect Commands for Verifying Checksums on Windows
10
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: ajstewart426(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
I tried the instructions for verifying checksums on Windows (section 3.3.1) but
ran into a problem.
Version-Release number of selected component (if applicable):
Fedora 23 iso download, Windows 10 computer
How reproducible:
Follow the instructions detailed in section 3.3.1 of the install-guide on a
Windows 10 computer.
Steps to Reproduce:
1. Download the Fedora checksum file
2. Open a powershell session
3. Change to the directory containing the checksum file
4. Run the following commands:
> $image = "Fedora-Server-DVD-x86_64-21.iso"
> $checksum_file = "Fedora-Server-21-x86_64-CHECKSUM"
> $sha256 = New-Object -TypeName System.Security.Cryptography.sha256CryptoServiceProvider
> $expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern $image) -split " ")[0].ToLower()
> echo "Expected Checksum: $expected_checksum"
Actual results:
"sha256sum"
Expected results:
"a91eca2492ac84909953ef27040f9b61d8525f7ec5e89f6430319f49f9f823fe"
Additional info:
The correct checksum is actually in the fourth and final position of the string
after being split. I recommend replacing the [0] in the instructions with a
[-1], assuming that you are able to recreate this problem. If not, let me know
and I'll try to provide a more detailed report.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months
[Bug 1303428] New: Checksum calculation may lead to memory
exhaustion
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1303428
Bug ID: 1303428
Summary: Checksum calculation may lead to memory exhaustion
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: cspicer(a)redhat.com
Reporter: redhat(a)planetcobalt.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Chapter 3.3.1 of the Installation Guide[1] ("Verifying checksums on Windows
systems") suggests to pass the image as a byte array to the ComputeHash()
method for calculating the SHA-256 checksum:
> $download_checksum = [System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes("$PWD\$image"))).ToLower() -replace '-', ''
This reads the entire image into memory and may thus result in memory
exhaustion (System.OutOfMemoryException), depending on the size of the image
and the available memory in the computer running the verification.
Solution:
Read the image as a stream[2] instead of a byte array.
> $stream = (Get-Item "$PWD\$image").OpenRead()
> $hash = $sha256.ComputeHash($stream)
> $stream.Close()
> $download_checksum = [System.BitConverter]::ToString($hash).ToLower() -replace '-'
[1]:
https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/se...
[2]: https://msdn.microsoft.com/en-us/library/xa627k19.aspx
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months
[Bug 1299138] New: Instructions for verifying ISO on windows don't
work
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1299138
Bug ID: 1299138
Summary: Instructions for verifying ISO on windows don't work
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: high
Assignee: pbokoc(a)redhat.com
Reporter: tlhackque(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/se...
Section 3.3.1 gives a PowerShell procedure for verifying the signature of a
download on windows.
I downloaded Fedora-Server-DVD-x86_64-23 and tried the procedure. It fails due
to the size of the file.
Another method needs to be used.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create this script (copied and pasted from the cited webpage, except for the
Parameter block):
Param(
[Parameter(Mandatory=$True,Position=1)]
[String]$image,
[Parameter(Mandatory=$True,Position=2)]
[String]$checksum_file
)
$sha256 = New-Object -TypeName
System.Security.Cryptography.sha256CryptoServiceProvider
$expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern
$image) -split " ")[0].ToLower()
$download_checksum =
[System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes("$PWD\$image"))).ToLower()
-replace '-', ''
echo "Download Checksum: $download_checksum"
echo "Expected Checksum: $expected_checksum"
if ( $download_checksum -eq "$expected_checksum" ) {
echo "Checksum test passed!"
} else {
echo "Checksum test failed."
}
2. If necessary, execute: Set-ExecutionPolicy RemoteSigned
3. ..\Documents\Scripts\SHA1-Check.ps1 Fedora-Server-DVD-x86_64-23.iso
Fedora-Server-23-x86_64-CHECKSUM
Actual results:
Exception calling "ReadAllBytes" with "1" argument(s): "The file is too long.
This operation is currently limited to supporting
files less than 2 gigabytes in size."
At C:\Users\timothe\Documents\Scripts\SHA1-Check.ps1:10 char:1
+ $download_checksum = [System.BitConverter]::ToString($sha256.ComputeH ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IOException
Expected results:
The checksum is computed.
Additional info:
Also note that the script as written will fail if a path is given, as '.' and
'\' are used in the pattern - which takes a REGEX, where they are special.
Note that Fedora 18
(https://docs.fedoraproject.org/en-US/Fedora/18/html/Burning_ISO_images_to...
an executable from
http://www.labtestproject.com/files/win/sha256sum/sha256sum.exe that can handle
the large file.
While the idea of a powershell script to avoid downloading an unknown
executable is clever, it doesn't work.
Perhaps a signed windows executable can be provided.
Also, the procedure should indicate how to verify the PGP signature on the
CHECKSUM file...
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months
[Bug 1226101] New: $expected_checksum not correct in "Verifying checksums on Windows systems"
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1226101
Bug ID: 1226101
Summary: $expected_checksum not correct in "Verifying checksums
on Windows systems"
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: iam(a)nnutter.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Created attachment 1031533
--> https://bugzilla.redhat.com/attachment.cgi?id=1031533&action=edit
Fedora-Workstation-22-x86_64-CHECKSUM
Description of problem:
When following the steps in "Verifying checksums on Windows systems" the value
of the `$expected_checksum` is 'sha256' because it is splitting the line and
grabbing the first word.
Version-Release number of selected component (if applicable): 22, full URL in
"Additional info".
How reproducible: 100%
Steps to Reproduce:
1. Download Fedora-Live-Workstation-x86_64-22-3.iso.
2. Download Fedora-Workstation-22-x86_64-CHECKSUM.txt.
3. Follow PowerShell instruction from "Verifying checksums on Windows systems".
Actual results:
`$expected_checksum` equals 'sha256'.
PS C:\Users\...\Downloads> $checksum_file =
"Fedora-Workstation-22-x86_64-CHECKSUM.txt"
PS C:\Users\...\Downloads> $image = "Fedora-Live-Workstation-x86_64-22-3.iso"
PS C:\Users\...\Downloads> $expected_checksum = ((Get-Content $checksum_file |
Select-String -Pattern $image) -split " ")[0].ToLower()
PS C:\Users\...\Downloads> $expected_checksum
sha256
Expected results:
`$expected_checksum` equals
'615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf'.
PS C:\Users\...\Downloads> $expected_checksum = ((Get-Content $checksum_file |
Select-String -Pattern $image) -split " ")[3].ToLower()
PS C:\Users\...\Downloads> $expected_checksum
615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf
Additional info:
I've attached the "Fedora-Workstation-22-x86_64-CHECKSUM.txt" since it is not
very large but it's from,
https://getfedora.org/verify
The "Verifying checksums on Windows systems" page is,
https://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/se...
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months
[Bug 1146950] New: Test Bug
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1146950
Bug ID: 1146950
Summary: Test Bug
Product: Fedora Documentation
Version: devel
Component: system-administrator's-reference-guide
Assignee: jhradile(a)redhat.com
Reporter: jhradile(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
This is just a test bug. Please, feel free to ignore it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 2 months