• 9tr6gyp3@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    4 hours ago

    I think they want to, but Microsoft has made it expensive for open source developers who do this as a hobby and not as a job to sign their software. I know not too long ago, this particular dev was asking its users to install a root certificate on their PC so that they wouldn’t have to deal with Microsofts method of signing software, but that kind of backfired on them.

    • yetAnotherUser@discuss.tchncs.de
      link
      fedilink
      arrow-up
      2
      ·
      2 hours ago

      Yes, but from what I understand this refers to the automatic update functionality and not Microsoft’s own .exe signature verification thing.

      Couldn’t you do it like this:

      • Put hardcoded key into N++
      • If a new release is available: Download, then verify signature
      • If the signatures match, do whatever Windows requires to install an update

      That should work, shouldn’t it?

      • 9tr6gyp3@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 hours ago

        No, because you wouldn’t be able to execute the updated exe without a valid signature. You would essentially brick the install with that method, and probably upset Microsoft’s security software in the process.

        • yetAnotherUser@discuss.tchncs.de
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          23 minutes ago

          I meant the old .exe would check the signatures before initializing the official Windows way to update. Effectively have this run whenever you start the application:

          main() {
              if (update_available()) {
                  exe_path = download_update()
                  if (signature(exe_path) == SIGNATURE) {
                      install_update(exe_path)
                      restart()
                  } else {
                      put_up_a_warning_or_something()
                      delete(exe_path)
                  }
              }
          # Rest of the application
          # ...
          }
          

          The only thing I have no idea how to implement would be the install_update(path) function. But surely this is one way to install updates without signatures recognized by Microsoft, right?

          And if for some reason you aren’t allowed to sign the .exe because this breaks something, then place an unsigned .exe in a signed zip folder.

    • TeamAssimilation@infosec.pub
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      4 hours ago

      Let’s Encrypt is a trusted, established alternative, it could replace Microsoft for long-lived software certificates.

      Or tarnish its name associating it with malware and bad actors, who knows?