Firepit

Latest version: v2.3.33

Safety actively analyzes 631215 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 10 of 12

1.1.0

Not secure
Concurrency fixes: you should now be able to create separate storage objects per thread and `cache()` bundles concurrently.

1.0.18

Not secure
- Make sure rename_view can overwrite an existing view
- query: fix handling of comparing lists to null
- Add missing ujson dependency
- github actions shenanigans

1.0.17

Not secure
- PostgreSQL: switch from `BIGINT` to `NUMERIC` to handle unsigned 64-bit ints. We need to eventually do something smarter since lots of numeric fields (like `src_port` and `dst_port`) don't require anything more than `INTEGER`.
- Add optional batchsize keyword param to cache() for performance tuning

1.0.16

Not secure
Fixes 17: CardinalityViolation: ON CONFLICT DO UPDATE command cannot affect row a second time

1.0.15

Not secure
Multiple PostgreSQL fixes:
- IncompatibleType/DependentObjectsStillExist exception when redefining a viewname
- port values of 0 turned into NULL
- STIX patterning `NOT MATCHES` operator not working (always returns nothing)

1.0.14

Not secure
- postgresql: create UNLOGGED tables for faster insertion. Since the data is presumably stored elsewhere (i.e. either the files you pass to `cache()` or the original systems you got your data from) this seems like a reasonable tradeoff.
- markroot: mark entire trees; i.e. when a process references a file and another process (i.e. it's parent), mark both the child process AND it's binary_ref file as "roots". This is useful when trying to reconstruct the original observations (via SQL LEFT OUTER JOIN - when joining the `observed-data` table to the SCO tables, add the condition `AND x_root IS NOT NULL`. This, combined with the DISTINCT clause, should be enough to prevent any "duplicate" rows resulting from the join.

Page 10 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.