Jeff Burdges

I'd presume the AEAD nonces prevent the worst dangers, but maybe TLS 1.3 remarks about storing 0-RTT states, like avoid doing so unless you know you'll update them.

We cannot claim rustls remains secure if state can be serialized because existing discussions assumed deletion. Among the plausible concerns, you find mess like - Adversaries might cause nonce reuse...

I mostly chimed in above just to say that cargo [patch] looks quite good for "I want to modify this code in a way that breaks all its contracts but...

In what repo is your code @est31 ?

Appears the recent discussion is here : https://github.com/libgit2/libgit2/issues/3058

It's much worse than leaking unprocessed data. I'd expect serialzied state breaks the primitives in "most" ways. It's fine if used in non-adversarial ways of course, like if the same...

Yes, we should not build upon chains we know to be invalid, or that have lost dispute votes, but the other question is what to do with chains where someone...

You've presumably seen https://github.com/filecoin-project/neptune by now. There surely exist tools for serializing rust types into rust code. If such a tool replaces `Cow::Owned(Box)` with `Cow::Borrowed(&'static [T])` then one could avoid...

Is there ever a need to generate parameters dynamically in Rust code? If so, then someone could translate the sage script of course, and then `Cow` tricks help. I suppose...

There is an [uneval](https://github.com/Cerberuser/uneval) crate that produces Rust code using serde. It'll work on code using `Vec` I think, but then requires `lazy_static` or similar. It'd requires post processing for...