Chaskiel Grundman

Apart from the CSRF thing, the most significant problem I see here is that you are embedding microsoft's (OASIS WS-Security) attribute mappings, which are not the same as the ones...

I am pretty sure this is one of the issues from #1443. I believe that either https://github.com/autolab/Autolab/pull/1443/commits/8d76c19173975c69991e4a961f7e0c1bafe63632 or the combination of https://github.com/cg2v/Autolab/commit/057493b3e518376d54fa62dc74b4ac7ba46353a5 and https://github.com/cg2v/Autolab/commit/752a44f942fe65168de0de003060d073c09817ea should fix this issue

Rasberry Pi is ARM, not i386. You can possibly try https://github.com/prasmussen/gdrive/releases/download/2.1.1/gdrive_2.1.1_linux_arm64.tar.gz instead. If you can upgrade your go to 1.16 (not 1.17 or newer), then go get may work. It...

@StephanieG60 That looks like a cross compiler issue. https://github.com/golang/go/issues/16801. You need to set the CC variable to the gcc (or clang) cross compiler for your pi build environment.

I happened to be investigating this exact rule today, and was wondering about the |'s myself. The cause of the strange output is that the signature has a sequence `(0D|0A)`...

I have a partial implementation of this feature at https://github.com/cg2v/dkim/tree/interceptor_wrap_dkim_header It has no new tests, and fails the Dkim::InterceptorTest#test_same_output_as_direct_usage because I implemented the change in mail/dkim_field.rb and the output no...

It doesn't assert against a fixed result that includes an unwrapped header, but against a call to Dkim.sign that generates one. If most people use Dkim.sign, then you need a...

Probably not. Nothing related to this issue has caused any actual problems for my deployment in recent memory

The python->perl change was a result of what was in the sample container (it only has python 3), assuming that the containers used in production would be similarly minimal, and...

The timeout mismatch happened because there were zombie processes after autodriver did its first kill, and the wrapper, which is pid 1, didn't wait for them. Apparently, when a shell...