Mingye Chen
Mingye Chen
Currently the decoy registrar has its own custom dialer. We also have a the [dialer from `tapdance.Dialer`](https://github.com/refraction-networking/gotapdance/blob/82afbf2c0811fe577f3c202adcfd04541bd36324/tapdance/dialer.go#L22) that is used in other registrars and for the connection, so we might...
Currently, the client hard codes some variables in the registrars. Consider putting them in their respective protobuf messages in client conf. |variable|current assignment|usage| |---|---|---| |connection delay|[api](https://github.com/refraction-networking/gotapdance/blob/f2831237dc17c0e55476369cb8d83d451f8275a8/cli/main.go#L134) [bdapi](https://github.com/refraction-networking/gotapdance/blob/f2831237dc17c0e55476369cb8d83d451f8275a8/cli/main.go#L145) [dns](https://github.com/refraction-networking/gotapdance/blob/f2831237dc17c0e55476369cb8d83d451f8275a8/cli/main.go#L151) [bddns](https://github.com/refraction-networking/gotapdance/blob/f2831237dc17c0e55476369cb8d83d451f8275a8/cli/main.go#L157) [decoy](https://github.com/refraction-networking/gotapdance/blob/f2831237dc17c0e55476369cb8d83d451f8275a8/tapdance/conjure.go#L153)|Length...
The DNS registrar currently supports ~90 bytes of data in 1 request. Support larger registrations by fragmenting the registration into two seperate requests.
Compared to firefox 120, changes seem to include: - added `X25519MLKEM768` in keyshare and supported curves - added signed certificate timestamp extension - added compress certificate extension