Now really sure that it'll help you, but in Kazakhstan digital signatures can be legally significant (have equal significance as hand-written signatures) in case if several requirements are met.
One of the requirements is that certificate has to be issued by accredited CA. And there is one such CA - National CA (https://pki.gov.kz/), it issues such certificates for free.
Also there is a service that allows anyone to sign any file using a certificate issued by National CA - https://sigex.kz, thus making it legally significant. It's free for use (except for heavy RPS enterprise users and the ones, how need support).
So in Kazakhstan you can do e-docs signed by e-signs totally for free.
I'm talking about a broad range of scenarios where it's impossible to use standard tools, like this one:
- You need to transfer some data from your machine to the one you do not trust (e.g. kiosk). USB drive is a bad idea in such situation, logging in to any service on an untrusted machine is even worse. One could create a temporary email account for this purpose, but it's a burden.
In case when remote control capabilities are not required, one could use jitsi (https://jitsi.org) video conferencing service which provides screen sharing capabilities (implementation depends on the web browser).
The main advantage is that there is no need to install any software neither on the remote machine nor on the local one.
There is a cloud hosted free version https://meet.jit.si which does not even require registration.
Yes, 19" rack-mount server chassis would be a perfect solution, but it is not mandatory. The previous best bet were ORWL devices but I never managed to use them because of several nasty bugs.
An idea to wrap equipment in some kind of a sealant is interesting, but I suppose that we'll face overheating problems in this case.
There is no need to automagically wipe data or to explode anything: sensitive data is protected by encryption, during system startup key are loaded from external removable storage. But I have to be sure that software was not tampered with while server was offline.
What bothers me a lot, is that no one talked about a possible leak of private npm repositories accounts. Keys (along with repository urls) are usually stored in .npmrc along with all other stuff.
The fact that npmjs.com revoked access token has no effect on private repositories access tokens. I would recommend everyone, who uses private npm repositories, to investigate a possibility of credentials leak.
It would be great if you could elaborate on this: "Sending to an Unbuffered Channel Returns As Soon As the Target Receiver Is Ready"
As far as I understand, the problem is that the printing goroutine is forced to exit when the main goroutine exits. This way it's unknown if all the submitted work was done.
It seems to me that the caption is a bit misleading, it implies that the problem occurs only with "Unbuffered" channels.
I'm not shure that it is a good idea to create (and use) such packages as 'parse-any-structed-file'. If you know what you need, then you can use an optimized implementation.