quapka

After the merge of #23 all of the kwargs from `pytds.connect()` should be supported. `extra_params` is not one of those, so it's still not supported.

Hi, have you made any progress so far, @stusmall? I might take a look.

Ok, and what is the intended way of running the fuzzer? I've built the `hfuzz` and tried to running it without a success: ```bash $./target/release/handshake_reader This executable hasn't been built...

Oh, I see. ``` $ cargo install honggfuzz ``` And I also needed `sudo apt-get install binutils-dev`. Now: ``` $ cargo hfuzz run handshake_reader ``` works. I suppose worth adding...

An attempt to analyze the errors a bit more: ```fish --> pytest | grep '^E' | sort | uniq -c 40 E noise.exceptions.NoiseProtocolNameError: Unknown pattern in Noise Protocol name, given...

> Thanks for the report! That documentation wasn't there when the stop commands were first added (and, annoyingly, their suggested deterministic-but-random method of getting a token doesn't seem easily possible...

Hi folks, is there a problem in adding a security policy?

I see, @tyranron. When is the release expected or is there a secure communication channel in the meantime? Adding a security policy should not [actually take much time](https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository). :slightly_smiling_face:

> (I used to manage security updates for macOS and Firefox FWIW) @LegNeato that is a resume worth mentioning IMHO. It is the maintainers/code-owners decision how such issues should be...

From a quick look around I don't see how the CI failures relate to my changeset.