[Bug 1282226] New: Incorrect Commands for Verifying Checksums on Windows 10

bugzilla at redhat.com bugzilla at redhat.com
Sun Nov 15 16:52:10 UTC 2015


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 at redhat.com
          Reporter: ajstewart426 at gmail.com
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: pbokoc at redhat.com, zach at 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.


More information about the docs-qa mailing list