Warp – self-contained, single binary applications

Re:Warp – self-contained, single binary applications by nur0n on Friday October 12, 2018 @07:08PM (#18205354)

I think the inverse argument can be made against shared libraries: if an update introduces a vulnerability, now all programs which depend on that library become vulnerable.

[ Parent | on HN ]

Re:Warp – self-contained, single binary applications by flingo on Saturday October 13, 2018 @07:46AM (#18207533)

Security problems often exist for years at a time.

Rather than making all of those applications vulnerable at the same time, they slowly become vulnerable as the release binaries are linked against bugged code. If it's not linked at runtime, or recompiled, it'll be vulnerable forever.

[ Parent | on HN ]

Re:Warp – self-contained, single binary applications by therein on Saturday October 13, 2018 @01:42AM (#18206624)

I would like to think that projects overall tend to fix more bugs than introduce them. It's not like projects go from orderly to disorderly over time.

[ Parent | on HN ]

Re:Warp – self-contained, single binary applications by quickben on Saturday October 13, 2018 @02:02AM (#18206667)

But some are high value targets (crypto ones, etc).

[ Parent | on HN ]

Re:Warp – self-contained, single binary applications by antaviana on Saturday October 13, 2018 @03:20AM (#18206848)

If I write malware, I guess it’s possibly easier to infect one library than thousands of executables.

[ Parent | on HN ]