Libtaxii

Latest version: v1.1.119

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

Scan your dependencies

Page 3 of 5

1.1.107

Not secure
--------------------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.106...1.1.107>`__

- Fix 184 - Use proxy for both HTTP and HTTPS (nadavc)
- Fix 187 - Handle numeric values in taxii_default_query (stkyle)
- Update Example Query documentation (stkyle)
- Fix 189 - Update how constants are used and referenced (stkyle)
- Show HTTP error code in StatusMessage.message (ahippo)
- Python 3 compatibility (rjprins)

1.1.106

Not secure
-------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.105...1.1.106>`__

- Thank you to the multiple contributors for this release: traut, gtback, wbolster, and MarkDavidson, and thank you to those who filed issues that were fixed in this release.
- Timestamp labels can now be provided as a string or as a python datetime object. Previously, only datetime objects were permitted.
- Some big changes to TAXII Client command line args. Deprecated URL components (e.g., --host, --port) in favor of specifying a single url (--url)
- Added a TAXII Inbox 1.0 client
- Decreased the likelihood of future message ID collisions
- A variety of improvements in the following areas: data validation, typos, documentation, DRY-ness, overall repo quality (thanks gtback)
- Multiple code cleanup changes (Thanks in part to traut of IntelWorks)

1.1.105

Not secure
-------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.104...1.1.105>`__

- Fixed multiple XML parsing related vulnerabilities (Thanks guidovranken of IntelWorks for the vulnerability research!)

1.1.104

Not secure
-------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.103...1.1.04>`__

- Fixed a bug where libtaxii did not properly handle XML values for Extended Headers
- Added checking for required status detail keys in Status Messages
- Improved data validation in various places, fixed various bugs, and improved documentation
- Improved filename generation in scripts (Thanks guidovranken!)

1.1.103

Not secure
-------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.102...1.1.103>`__

In terms of code organization, there are a few big changes beginning to
take place in this version of libtaxii. Constants and commonly used classes/functions
are being moved to common locations (libtaxii.constants and libtaxii.common, respectively).
Also, nested classes (e.g., messages_11.DiscoveryResponse.ServiceInstance) have been de-nested
(e.g., is now messages_11.ServiceInstance). All of these changes are intended to make
using libtaxii easier. For the time being, backward compatibility has been maintained, but
many of these changes may result in a backward compatibility breaking change in a future,
major release of libtaxii.

Major changes:

- libtaxii.constants, a new source file, was created. The definition for all constants in libtaxii have been moved to libtaxii.constants. Aliases to the previous definition locations have been retained for backward compatibility and may be removed in a future major release.
- libtaxii.common, a new source file for containing classes and methods common to TAXII, was created. Some common classes and functions have been moved into libtaxii.common, and more will be moved over time. Aliases to the previous classes and functions have been retained for backward compatibility and may be removed in a future major release. (Thanks, gtback!)
- Promoted nested classes to module-level classes in messages_10, messages_11, and taxii_default_query. Aliases to the previous, nested, classes have been retained for backward compatibility and may be removed in a future major release. (Thanks, gtback!)
- A ‘to_text()’ method has been added to all TAXII Message classes. ‘to_text()’ provides a “nicely formatted” human readable representation of a TAXII Message and its components. The ‘to_text()’ method was added to support libtaxii’s scripts. There is no ‘from_text()’ method as this is not intended to be a serialization/deserialization feature, but a readability feature.
- Lowered the required version of lxml to 2.2.3, the latest available on RHEL 6. (Thanks to mblayman for raising this)
- Lowered the required version of python-dateutil to 1.4.1, the latest available on RHEL 6. (Thanks to mblayman for raising this)
- TAXII 1.1 StatusMessages now raise a ValueError when required a Status Detail is not set.
- TAXII XML Validation has a new methodology: See validation.SchemaValidator (http://libtaxii.readthedocs.org/en/latest/api/validation.html#libtaxii.validation.SchemaValidator)
- Related: validate_xml(…) has been deprecated and may be removed in a future major release.

Minor changes:

- Tons of PEP8 improvements (Thanks, gtback!)
- TAXII Scripts have been entirely reorganized to be more DRY.
- Added two constants for Proxy Settings (SYSTEM_PROXY and NO_PROXY). These supersede the need to use either None or ‘noproxy’, which were not as clear to developers.
- Improved documentation, Tox usage, and Travis-CI usage. (Thanks, gtback!)
- SMIME Content Binding added (application/x-pks7-mime)
- For Python 2.6, argparse is now a requirement
- Added constants for TAXII Default Query Parameters and Relationships

Bug fixes:

- In messages_11.PollResponse, the result_part_number parameter is now set by the constructor.

1.1.102

Not secure
-------
`(diff) <https://github.com/TAXIIProject/libtaxii/compare/1.1.101...1.1.102>`__

The biggest change was the addition of scripts to libtaxii. Now when you install libtaxii, you get
a number of scripts that are by default configured to hit the TAXII Test server (taxiitest.mitre.org).
You can specify a number of parameters on the command line to change where/how the scripts connect.
The scripts are:

- discovery_client - Calls a TAXII 1.1 Discovery Service
- fulfillment_client - Calls a TAXII 1.1 Poll Service for Poll Fulfillment
- inbox_client - Calls a TAXII 1.1 Inbox Service. Comes packaged with a STIX document to use by default.
- poll_client - Calls a TAXII 1.1 Poll Service
- poll_client_10 - Calls a TAXII 1.0 Poll Service (Note: Does not work with taxiitest.mitre.org, as taxiitest.mitre.org is TAXII 1.1 only)
- query_client - Calls a TAXII 1.1 Poll Service with a query on IP or File Hash (Note: As of 6/11/2014; Works with the master branch of YETI, and will work with YETI after the next release of YETI)

We also had a number of bug fixes and impprovements for this version of libtaxii:

- Unicode strings work round trip (Hat tip to Ben Yates for reporting the issue)
- Added TONS of documentation (http://libtaxii.readthedocs.org/en/latest/index.html). Big thanks to gtback and slsnow!
- Fixed some issues in ContentBlock.content where certain data was not serializing/deserializing properly
- Streamlined serialization of XML documents to avoid a double-parse in certain cases
- Added a Content Binding ID for STIX XML 1.1.1
- Added an optional pretty_print argument to all to_xml() functions. e.g., to_xml(pretty_print=True)
- Added the three TAXII Default Query Status Type to libtaxii.taxii_default_query
- Fixed a bug where custom Status Types were prohibited
- Added Travis CI

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.