diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-pycef.spec | 277 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 279 insertions, 0 deletions
@@ -0,0 +1 @@ +/pycef-1.11.tar.gz diff --git a/python-pycef.spec b/python-pycef.spec new file mode 100644 index 0000000..36265fc --- /dev/null +++ b/python-pycef.spec @@ -0,0 +1,277 @@ +%global _empty_manifest_terminate_build 0 +Name: python-pycef +Version: 1.11 +Release: 1 +Summary: A very simple CEF parser. +License: MIT +URL: https://github.com/DavidJBianco/pycef +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/20/c9/4d690e94c074536315ba26f7833c5faffe5489bae8624bd2393bd0ba4993/pycef-1.11.tar.gz +BuildArch: noarch + +Requires: python3-future + +%description +# pycef +A very simple CEF parser for Python 2/3 + +I originally wrote this because I wasn't able to find very many good Python CEF parsers out there. I did find [one by Sooshie](https://github.com/sooshie/cef_parser) that got me started (thanks for sharing, sir!), but I elected to produce my own. + +The `parse` function takes a string containing a single CEF record and returns a dict containing the following keys, as defined in the [CEF format documentation](https://community.microfocus.com/t5/ArcSight-Connectors/ArcSight-Common-Event-Format-CEF-Implementation-Standard/ta-p/1645557): + +* CEFVersion +* DeviceVendor +* DeviceVersion +* DeviceEventClassID +* Name +* Severity + +If there are any `key=value` pairs in the "extensions" section (and face it, pretty much every CEF record has these), they'll also be in the dict, with the dict key name the same as the CEF record's key name. If it could not recognize any CEF data, the `parse` function will return `None`. + +_NOTE: Versions 1.10 and earlier used 'DeviceName' and 'DeviceSeverity' instead of just 'Name' and 'Severity'. Those old keys are still present in the returned dictionary for backwards-compatibility reasons, but are likely to be removed in the future without warning._ + +## Example Usage +Parsing a well-formatted CEF record + +```python +>>> import pycef +>>> cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +Parsing a line of CEF from a source with header junk at the front (NOTE: this isn't specific to syslog headers as in the example. The parser just starts wherever 'CEF:0' is found): + +```python +>>> import pycef +>>> cef_syslog = 'Nov 16 21:24:18 arcsightfwd.davidbianco.io CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef_syslog) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +## Logging +`Pycef` uses the standard Python `logging` module. By default, you will not see any logs, but you can easily configure them within your own application. Here's an example: + +```python +import logging + +# We log with the name 'pycef' +logger = logging.getLogger('pycef') + +# set log level to DEBUG to get the most verbose output +logger.setLevel(logging.DEBUG) + +ch = logging.StreamHandler() +ch.setLevel(logging.DEBUG) +formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s') +ch.setFormatter(formatter) +logger.addHandler(ch) + +# well-formatted CEF data will log the parsed values at DEBUG level +cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +d = pycef.parse(cef) +2018-11-23 08:49:39,827 - pycef - DEBUG - Returning values: {'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} + +# Parse errors in the data will log at WARNING level +pycef.parse('kjlk') +2018-11-23 08:47:42,853 - pycef - WARNING - Could not parse record. Is it valid CEF format? +``` + + + + +%package -n python3-pycef +Summary: A very simple CEF parser. +Provides: python-pycef +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-pycef +# pycef +A very simple CEF parser for Python 2/3 + +I originally wrote this because I wasn't able to find very many good Python CEF parsers out there. I did find [one by Sooshie](https://github.com/sooshie/cef_parser) that got me started (thanks for sharing, sir!), but I elected to produce my own. + +The `parse` function takes a string containing a single CEF record and returns a dict containing the following keys, as defined in the [CEF format documentation](https://community.microfocus.com/t5/ArcSight-Connectors/ArcSight-Common-Event-Format-CEF-Implementation-Standard/ta-p/1645557): + +* CEFVersion +* DeviceVendor +* DeviceVersion +* DeviceEventClassID +* Name +* Severity + +If there are any `key=value` pairs in the "extensions" section (and face it, pretty much every CEF record has these), they'll also be in the dict, with the dict key name the same as the CEF record's key name. If it could not recognize any CEF data, the `parse` function will return `None`. + +_NOTE: Versions 1.10 and earlier used 'DeviceName' and 'DeviceSeverity' instead of just 'Name' and 'Severity'. Those old keys are still present in the returned dictionary for backwards-compatibility reasons, but are likely to be removed in the future without warning._ + +## Example Usage +Parsing a well-formatted CEF record + +```python +>>> import pycef +>>> cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +Parsing a line of CEF from a source with header junk at the front (NOTE: this isn't specific to syslog headers as in the example. The parser just starts wherever 'CEF:0' is found): + +```python +>>> import pycef +>>> cef_syslog = 'Nov 16 21:24:18 arcsightfwd.davidbianco.io CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef_syslog) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +## Logging +`Pycef` uses the standard Python `logging` module. By default, you will not see any logs, but you can easily configure them within your own application. Here's an example: + +```python +import logging + +# We log with the name 'pycef' +logger = logging.getLogger('pycef') + +# set log level to DEBUG to get the most verbose output +logger.setLevel(logging.DEBUG) + +ch = logging.StreamHandler() +ch.setLevel(logging.DEBUG) +formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s') +ch.setFormatter(formatter) +logger.addHandler(ch) + +# well-formatted CEF data will log the parsed values at DEBUG level +cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +d = pycef.parse(cef) +2018-11-23 08:49:39,827 - pycef - DEBUG - Returning values: {'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} + +# Parse errors in the data will log at WARNING level +pycef.parse('kjlk') +2018-11-23 08:47:42,853 - pycef - WARNING - Could not parse record. Is it valid CEF format? +``` + + + + +%package help +Summary: Development documents and examples for pycef +Provides: python3-pycef-doc +%description help +# pycef +A very simple CEF parser for Python 2/3 + +I originally wrote this because I wasn't able to find very many good Python CEF parsers out there. I did find [one by Sooshie](https://github.com/sooshie/cef_parser) that got me started (thanks for sharing, sir!), but I elected to produce my own. + +The `parse` function takes a string containing a single CEF record and returns a dict containing the following keys, as defined in the [CEF format documentation](https://community.microfocus.com/t5/ArcSight-Connectors/ArcSight-Common-Event-Format-CEF-Implementation-Standard/ta-p/1645557): + +* CEFVersion +* DeviceVendor +* DeviceVersion +* DeviceEventClassID +* Name +* Severity + +If there are any `key=value` pairs in the "extensions" section (and face it, pretty much every CEF record has these), they'll also be in the dict, with the dict key name the same as the CEF record's key name. If it could not recognize any CEF data, the `parse` function will return `None`. + +_NOTE: Versions 1.10 and earlier used 'DeviceName' and 'DeviceSeverity' instead of just 'Name' and 'Severity'. Those old keys are still present in the returned dictionary for backwards-compatibility reasons, but are likely to be removed in the future without warning._ + +## Example Usage +Parsing a well-formatted CEF record + +```python +>>> import pycef +>>> cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +Parsing a line of CEF from a source with header junk at the front (NOTE: this isn't specific to syslog headers as in the example. The parser just starts wherever 'CEF:0' is found): + +```python +>>> import pycef +>>> cef_syslog = 'Nov 16 21:24:18 arcsightfwd.davidbianco.io CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +>>> d = pycef.parse(cef_syslog) +>>> d +{'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} +``` + +## Logging +`Pycef` uses the standard Python `logging` module. By default, you will not see any logs, but you can easily configure them within your own application. Here's an example: + +```python +import logging + +# We log with the name 'pycef' +logger = logging.getLogger('pycef') + +# set log level to DEBUG to get the most verbose output +logger.setLevel(logging.DEBUG) + +ch = logging.StreamHandler() +ch.setLevel(logging.DEBUG) +formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s') +ch.setFormatter(formatter) +logger.addHandler(ch) + +# well-formatted CEF data will log the parsed values at DEBUG level +cef = 'CEF:0|pycef|python CEF tests|1|2|Test event 1|3| field1=value1 field2=value2 field3=value3' +d = pycef.parse(cef) +2018-11-23 08:49:39,827 - pycef - DEBUG - Returning values: {'DeviceVendor': 'pycef', 'DeviceProduct': 'python CEF tests', 'DeviceVersion': '1', 'DeviceEventClassID': '2', 'Name': 'Test event 1', 'Severity': '3', 'CEFVersion': '0', 'field1': 'value1', 'field2': 'value2', 'field3': 'value3'} + +# Parse errors in the data will log at WARNING level +pycef.parse('kjlk') +2018-11-23 08:47:42,853 - pycef - WARNING - Could not parse record. Is it valid CEF format? +``` + + + + +%prep +%autosetup -n pycef-1.11 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-pycef -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 1.11-1 +- Package Spec generated @@ -0,0 +1 @@ +482ce4db0ee42baf456be3db023bf5e0 pycef-1.11.tar.gz |