You want to understand why Alpine exists, you get to do some research. There is a lot of innovation happening past the typical these days. Typical systems are neither secure nor scalable. It shouldn’t surprise you a min container distribution exists. Hell, instantiation latency
-
-
I'm not surprised, I even see the benefit, but for our not so small use case, it borders on the irrelevant. Not worth accepting the risk of less than stellar security game.
1 reply 0 retweets 1 like -
Replying to @andreasdotorg @siosm
Look, this bug begins and ends at not using https. The scene that doesn’t see that is the scene with the stale game.
1 reply 0 retweets 0 likes -
It actually continues with extracting the archive before verifying the checksum.
1 reply 0 retweets 2 likes -
Replying to @andreasdotorg @siosm
No. The moment you parse a byte that didn’t come from the secure channel, you’re fucked. No exceptions. That includes the sum to check. It’s not saving you. Sorry.
1 reply 0 retweets 0 likes -
Replying to @dakami
Absolutely not. A package with a secure signature is a secure channel. You know, these days, not just using Uptane, which integrates well with package managers and solves all those problems, is something I don't understand.
2 replies 0 retweets 2 likes -
Replying to @andreasdotorg
No. It’s not. That is what the data is saying. Attempts to make secure packages don’t, in practice, work any better than signed JavaScript on HTTP pages, for the same reasons, as they’re the same thing. It’s just rolling your own crypto. Use TLS.
1 reply 0 retweets 1 like -
Replying to @dakami
A couple of really smart people did implement Uptane. Go have a look at it.
1 reply 0 retweets 1 like -
-
Replying to @dakami @andreasdotorg
“Use Uptane” is notably not “roll your own crypto” so we don’t necessarily disagree here.
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.