George Brighton
George Brighton
Firstly, thanks for creating the `ApplicationSet` resource - it saves us a lot of duplication, and we find it incredibly useful. This is a feature request/design doc for a new...
We currently - accidentally - use cipher suite 3 (RAKP-HMAC-SHA1/HMAC-SHA1-96/AES-CBC-128). 17 (RAKP-HMAC-SHA256/HMAC-SHA256-128/AES-CBC-128) is newer, but less compatible.
Currently implemented in `V2Sessionless` only.
Folks currently have to know to look in `cmd`.
It's harder to forget to call `.Close()` when you are given a function explicitly when dialling a BMC or creating a session. ``` machine, close, err := bmc.DialV2(...) if err...
Needs to be at minimum RTT of "furthest" BMC, plus a few seconds to allow it to respond. The impact of setting it too low is corruption. Effects can be...
The BMC is entitled to omit everything after the completion code (apart from the checksum), so the error should be able the non-normal completion code, not about the missing defining...
It would be good to distinguish between timeouts, incorrect passwords (i.e. RAKP2 HMAC mismatch), and other errors.
Double check you always copy from the DecodeFromBytes slice input and never reference a subslice - it will change, and this will cause corruption.
Features
- Safe - no C(go) - Tested - Instrumented (Prometheus) - Simple (compared to FreeIPMI's FIIDs at least) - More efficient for long-lived processes (avoid repeated forking, cache sessions, so...