th4s

Results 34 issues of th4s

### Introduction The purpose of this write-up is to give a short overview of the current state. #290 gives a more involved overview and introduction into this topic. For both...

research

This PR adds OLE and ROLE to mpz by introducing two new crates and creates the building blocks, like e.g. traits and module structure, for future OLE flavors and additional...

This PR reimplements the share-conversion crates building upon `mpz-ole` and using the new threading approach of `context` injection. - It implements semi-honest `M2A` using OLE with errors. - It implements...

This PR adds `SharedROLEeProvider` and `SharedROLEeEvaluator` which offer preprocessed ROLEs and can make use of `mpz_common::sync::Mutex`

When running `cargo test --all-features` on my machine, I currently get some strange error: ![Screenshot_2023-09-16_19-27-02](https://github.com/privacy-scaling-explorations/mpz/assets/24564138/0af71a4f-5dcd-4210-a83e-5d050ecb0e76) **lldb stack** ``` * thread #9, name = 'chou_orlandi::t', stop reason = signal SIGABRT *...

The current API requires some mappings and conversions which should be encapsulated and exposed. For example currently you have to do [this](https://github.com/tlsnotary/tlsn/blob/a2334ee94afe410dec7aa88c5f92bb1c93183735/tlsn/tlsn-core/tests/api.rs#L55C1-L61) which is a bit cumbersome.

Modify the [current implementation](https://github.com/tlsnotary/tlsn/blob/dev/mpc/share-conversion-aio/src/gf2_128/recorder.rs#L44-L72) so that each individual OT choice is checked for correctness. Currently only the end result is checked. Furthermore add a commitment to the sender's rng seed,...

enhancement
good first issue

The current replay functionality added by tlsnotary/tlsn#131 allows to detect malicious behavior of the sender. However, we need a thorough analysis if the current implementation is sufficient. This involves to...

enhancement

Some bandwidth can be saved if we assume that the random block which the receiver holds after the Random OT setup is already an AES key. Then the only thing...

enhancement

It is currently possible to inject authorization headers into HTTP requests using [Credentials](https://github.com/thojest/ethane/blob/6703c62ae6a1082ed6d41c6e0f16fc0c77e57006/src/transport/mod.rs#L29) when creating a connector over [websocket](https://github.com/thojest/ethane/blob/6703c62ae6a1082ed6d41c6e0f16fc0c77e57006/src/connector/mod.rs#L45) or [http](https://github.com/thojest/ethane/blob/6703c62ae6a1082ed6d41c6e0f16fc0c77e57006/src/connector/mod.rs#L33). This also means it would be possible to use...

good first issue
technical