THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
package main | |
import ( | |
"bufio" | |
"crypto/tls" | |
"io" | |
"log" | |
"net" | |
"net/url" | |
"os" |
using namespace Microsoft.Exchange.Management.AdminApiProvider | |
using namespace Microsoft.Exchange.Management.ExoPowershellSnapin | |
using namespace System.Collections.Generic | |
using namespace System.Net.Http | |
using namespace System.Net.Http.Headers | |
using namespace System.Threading. | |
<# | |
I made this as a way to overcome some limitations with very complicated filter queries that exceed the REST limit, while being able to run them in parallel without resorting to runspaces | |
#> |
Oh hey, this rant of mine is making the rounds.
After I wrote this, one of the Matrix leads commented on it, which prompted me to look at their code. I have since found, uh, 4 3 different cryptographic issues in Matrix's Olm and Megolm code.
Expect a blog post on Dhole Moments at some point in August.
One of them is extremely bad, and will put a lot of burden on Matrix users to mitigate effectively. False alarm: I was mistaken about this one. I'll include it in the write-up, though.