Open James-Pickett opened 5 months ago
I suspect we'll need to encode it. Can we could use base64 and not hex?
I suspect we'll need to encode it. Can we could use base64 and not hex?
@directionless , is there a function for base64 encoding in sqlite? I did some googling, but could find anything outside of sqlite extensions.
Osquery ships a to_base64
and from_base64
@directionless , looks like these the to_base64
is not available to use in ATC creation. So far the only way I've found to get binary columns from ATCs is the hex
func
Huh. So I guess ATC doesn't expose the osquery sql extensions.
Naive question, when you did this without the hex, I assume it was a straight join. I'm wondering if it would work if the ATC was still bare, but our raw_data allowed a base64 in, and we joined there. I don't have the right words, but I think there are 2 places this is getting passed as a string, and I'm trying to isolate where the issue is.
Though saying that.... There's high odds the ATC implementation doesn't handle binary data correctly. I wonder if we can fix that.
using an ATC config such as this
will result in an error for a query such as
because the
dataclass_properties
column is binary dataone possible solution is to adjust the ATC config to pass the binary column as hex like:
and then decode the hex with inside launcher before parsing the plist