C For C's Sake
C For C's Sake
Oh, and Mindy [found a bug](https://github.com/cfcs/ocaml-pf/commit/40d416e97869828b73bc4fdf68c9e87ed03ebeb3) in that example code; if `provided_octets > 4` then it would complain.
It has only happened a few times, usually there are no problems. I do not have a trace, I can try to get one in case it happens again. There...
This is really a corner case, and something other libraries might forget to handle properly. Issuing an OTR error to provoke a new key exchange might be the best solution?
@aantron Thanks for taking the time to look into this! Let me know if I can do something to help debugging.
Ah, thank you! The `Lwt.fail` lead seems promising! I think the original crash in this case originates from `xenstore` (based on the error message immediately prior to the crash): https://github.com/mirage/ocaml-xenstore/blob/master/core/xs_protocol.ml#L671...
What is xxHash?
@wrouesnel you can do that already, distinguishing by hostname! (I was wondering the same the other day) :) @alexeymuranov how do you determine if the password entered by the user...
@alphapapa for that there's `rsync`. EDIT: And file permissions / attributes. BTW, what is the difference between "hardware failure" and "bitrot"?
If you are using ZFS, why not just use `zfs send` snapshots?
XScreensaver is a security disaster. There is a long discussion / evaluation here: https://github.com/QubesOS/qubes-issues/issues/963 It's my personal opinion that spending time on prettifying a lock screen is great, but the...