Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-13160

rapps_new did no checksum verification and the binary ate my dog afterwards

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      tested on 2017-04-30
      reactOS 0.4.5RC1
      Recently we replaced rapps with rapps_new in trunk.

      Story when wanting to test BurnAware Free 9.3:
      -completely fresh ros system installation, first things I did, startup rapps_new
      -The link to "BurnAware 9.3" was outdated, rapps_new downloaded 3.2kb crap instead.
      -Rapps (now new) did not verify any hash
      -and the 3.2kb exe was started via NTVDM (which is another bug)
      -until this point this is currently 100% reproducable, two things below are heavily random:
      ----------
      When I did for the first time, I got even a WIN32K hangup now.
      0.4.5RC1-1installationOfBurnAware9.3fromRappsInvokesNTVDM-thenWin32Khungup.log
      After inevitably reboot my FS was devestated and I got BSOD upon bootup:
      0.4.5RC1-2nextBootupSystemBSOD-eventually-dueTo-FScorruption.log
      -----------

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                learn_more Mark Jansen
                Reporter:
                reactosfanboy reactosfanboy
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: