M Hickford

Sage.

If it helps anyone else, I prepared the installers on another computer. * [usintgr.zip](https://github.com/umanovskis/win-kbd-usint-nodead/files/7636239/usintgr.zip)

See https://github.com/trustrachel/python-ntlm3/ and https://pypi.python.org/pypi/python-ntlm3/

I always thought that HTTP/2 and SPDY should be the same colour—or shades of the same colour—because HTTP/2 crystallised from SPDY. Whereas QUIC is wholly different, a transport layer protocol.

Plan is to fix this double-upstream in urllib3 https://github.com/shazow/urllib3/issues/242

Sorry that wasn't clear, there are two NTLM auth protocols, one for websites, one for proxies. They use different HTTP headers `www-authenticate` and `proxy-authenticate`. See http://davenport.sourceforge.net/ntlm.html#ntlmHttpAuthentication That plugin is based...

Before calling compile_native_go_fuzzer in I had to add the following to my [build.sh](https://github.com/transparency-dev/merkle/blob/main/.clusterfuzzlite/build.sh) ```sh go install github.com/AdamKorcz/go-118-fuzz-build@latest go get github.com/AdamKorcz/go-118-fuzz-build/utils ``` It would be helpful to document at https://google.github.io/oss-fuzz/getting-started/new-project-guide/go-lang/#buildsh

> This will be fixed once Go fuzzing is fully integrated into Clusterfuzz. @AdamKorcz do you know an issue in https://github.com/google/clusterfuzz to follow?

GitLab uses doorkeeper. Device flow would be useful for GitLab support in git-credential-manager https://gitlab.com/gitlab-org/gitlab/-/issues/225215 https://github.com/GitCredentialManager/git-credential-manager/issues/589

@irminsul now that https://github.com/exop-group/doorkeeper-device_authorization_grant/ is version 1.0 can this issue be closed?