Thomas Patzke
112 lines
4.2 KiB
Python
112 lines
4.2 KiB
Python
# Setup module for Sigma toolchain
|
|
# derived from example at https://github.com/pypa/sampleproject/blob/master/setup.py
|
|
from setuptools import setup, find_packages
|
|
# To use a consistent encoding
|
|
from codecs import open
|
|
from os import path
|
|
|
|
here = path.abspath(path.dirname(__file__))
|
|
|
|
# Get the long description from the README file
|
|
with open(path.join(here, 'README.md'), encoding='utf-8') as f:
|
|
long_description = f.read()
|
|
|
|
setup(
|
|
name='Sigma',
|
|
|
|
# Versions should comply with PEP440. For a discussion on single-sourcing
|
|
# the version across setup.py and the project code, see
|
|
# https://packaging.python.org/en/latest/single_source_version.html
|
|
version='0.1',
|
|
|
|
description='Tools for the Generic Signature Format for SIEM Systems',
|
|
long_description=long_description,
|
|
|
|
# The project's main homepage.
|
|
url='https://github.com/Neo23x0/sigma',
|
|
|
|
# Author details
|
|
author='Thomas Patzke',
|
|
author_email='thomas@patzke.org',
|
|
|
|
# Choose your license
|
|
license='LGPLv3',
|
|
|
|
# See https://pypi.python.org/pypi?%3Aaction=list_classifiers
|
|
classifiers=[
|
|
# How mature is this project? Common values are
|
|
# 3 - Alpha
|
|
# 4 - Beta
|
|
# 5 - Production/Stable
|
|
'Development Status :: 3 - Alpha',
|
|
|
|
# Indicate who your project is intended for
|
|
'Intended Audience :: Developers',
|
|
'Intended Audience :: Information Technology',
|
|
'Intended Audience :: System Administrators',
|
|
'Topic :: Security',
|
|
'Topic :: Internet :: Log Analysis',
|
|
|
|
# Pick your license as you wish (should match "license" above)
|
|
'License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3)',
|
|
|
|
# Specify the Python versions you support here. In particular, ensure
|
|
# that you indicate whether you support Python 2, Python 3 or both.
|
|
'Programming Language :: Python :: 3.4',
|
|
'Programming Language :: Python :: 3.5',
|
|
'Programming Language :: Python :: 3.6',
|
|
|
|
# Other attributes
|
|
'Environment :: Console',
|
|
],
|
|
|
|
# What does your project relate to?
|
|
keywords='security monitoring siem logging signatures elasticsearch splunk ids sysmon',
|
|
|
|
# You can just specify the packages manually here if your project is
|
|
# simple. Or you can use find_packages().
|
|
# packages=find_packages(exclude=['contrib', 'docs', 'tests']),
|
|
packages=['sigma'],
|
|
|
|
# Alternatively, if you want to distribute just a my_module.py, uncomment
|
|
# this:
|
|
# py_modules=["my_module"],
|
|
|
|
# List run-time dependencies here. These will be installed by pip when
|
|
# your project is installed. For an analysis of "install_requires" vs pip's
|
|
# requirements files see:
|
|
# https://packaging.python.org/en/latest/requirements.html
|
|
python_requires='~=3.3',
|
|
install_requires=['PyYAML'],
|
|
|
|
# List additional groups of dependencies here (e.g. development
|
|
# dependencies). You can install these using the following syntax,
|
|
# for example:
|
|
# $ pip install -e .[dev,test]
|
|
extras_require={
|
|
'test': ['coverage', 'yamllint'],
|
|
},
|
|
|
|
# If there are data files included in your packages that need to be
|
|
# installed, specify them here. If using Python 2.6 or less, then these
|
|
# have to be included in MANIFEST.in as well.
|
|
# package_data={
|
|
# 'sample': ['package_data.dat'],
|
|
# },
|
|
|
|
# Although 'package_data' is the preferred approach, in some case you may
|
|
# need to place data files outside of your packages. See:
|
|
# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
|
|
# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
|
|
data_files=[('config', ['tools/config/elk-windows.yml', 'tools/config/elk-linux.yml', 'tools/config/elk-defaultindex.yml', 'tools/config/splunk-windows-all.yml', 'tools/config/splunk-windows-all.yml'])],
|
|
|
|
# To provide executable scripts, use entry points in preference to the
|
|
# "scripts" keyword. Entry points provide cross-platform support and allow
|
|
# pip to create the appropriate form of executable for the target platform.
|
|
# entry_points={
|
|
# 'console_scripts': [
|
|
# 'sample=sample:main',
|
|
# ],
|
|
# },
|
|
)
|