Well so there are 2 fixes for the encryption table...one PR restores the original "broken" behavior. Which is merged and in master. This other one changes the API to produce

-1

when there is an error hitting the API, which is not yet merged. IMHO I would love it if we could do a 3.2.10 with what is in master right now. The reason I ask is the battery table I wrote at Querycon has not been in a release viable osquery yet (there has been a blocking regression in every release since the table was merged) So if we just cut a 3.2.10 on master now, that would be super helpful since it looks like 3.3.0 is a ways away.