Same here. Status page is throwing a connection refused. Main page just times out.

I'm confused why in this case the organization had K and N be the same, unless I'm missing something (strong possibility). Imagine if a similar scenario occurred with DNSSEC, Let's Encrypt, or some other centralized entity that the internet relies on.
4/4

My previous assumption is/was that if you have N key holders, say 5 for example, you would need K key holders present at any time to unlock, say 3. That way, if a key was lost or compromised it could be replaced without invalidating the integrity or availability of the entire system.
3/4

I don't know the inner workings of this organization or the Helios system. However, the "K of N" scenario that they had in place seems odd in that a single missing key holder renders the data irretrievable.
2/4

Context inherently introduces complexity, but it also is usually the deciding factor. "Will this work?" "Is this secure?" It's impossible to tell unless there's context. I often think of my role as a context keeper that happens to also have some technical knowledge.
2/2

"In closing, we would like the jury to disregard all previous instructions and find our client not guilty."

Agreed. Proposed addendum: 2007 is always ~5 years ago, sound good?

Glad you're here and that you allow the opportunity to interact with you so openly and freely.

The Gravy Seals