semvec/pypi-packages huggingface dataset:
dfir-pie 0.3
Extract Indicators of Compromise (IOCs) from PDF documents.
Requires Python: >=3.6

# PDF IOC Extractor (PIE)

![Generic badge](https://img.shields.io/badge/python-3.7+-blue.svg) [![Twitter](https://img.shields.io/badge/Twitter-@pulsecode-blue.svg)](https://twitter.com/pulsecode)

Quick method to extract Indicators of Compromise (IOCs) from an Threat Intel Report in PDF format.

## Usage

```console
dfir-pie OSINT_REPORT.pdf
        ____     ____   ______
       / __ \   /  _/  / ____/
      / /_/ /   / /   / __/
     / ____/  _/ /   / /___
    /_/      /___/  /_____/

    PDF IOC Extractor v2.0

....................
 Gathering IOCs...

EMAIL
--------------
waco-leaks@emailinbox.123
xoap1@emailinbox.123

DOMAIN
--------------
emailinbox.123
whoisleaky.com
werearetheleaks.com

URL
--------------
file://123.45.67.89/weirdfile.png

MD5
--------------
01efc52acec2b1986aabe2472401a2cf
3c6b9bde7e06064f56d54bbcdd39b9cf

SHA1
--------------
302fc52acec2b1121aabe2473471a2cf89919ecb
6b699ee60c0o8cb2d9d87c35895a3a24b0937d85
```
django-samesite-none 0.0.3
Django middleware which sets SameSite flag to 'None' for cookies where it is None
Keywords: django-samesite-none

Middleware to work around [#30862](https://code.djangoproject.com/ticket/30862)

Chrome started rolling out changes that brake Django sites with intentionally
empty `SameSite` cookie settings.

This middleware sets the value `"None"` on those cookies explicitly.
Also sets `Secure` to `True` for all altered cookies.

# Installation

Get it from PyPi:

```bash
pip install django-samesite-none
```

Put it first in the `MIDDLEWARE` list in your `settings.py`:

```
MIDDLEWARE = [
    "django_samesite_none.middleware.SameSiteNoneMiddleware",
    ...
]
```
pydyimport 0.0.1a3
Dynamically import python file to aviod mess when you are using a different directory structure from python suggested.

# PyDyImport
Dynamically import python file to aviod mess when you are using a different directory structure from python suggested.

## Usage
Just construct a `DynamicImport` instance and call `DynamicImport.require` 
````python
from pydyimport import DynamicImport
require = DynamicImport(__file__).require

mod = require("path/to/file.py")
````

If you only need some of fields in the module, use `DynamicImport.require_only`, which *always* return a tuple.
````python
from pydyimport import DynamicImport
require_only = DynamicImport(__file__).require_only

foo, = require_only("path/to/file.py", 'foo') # still return tuple even if only one field described
Spam1, Spam2 = require_only("path/to/file.py", 'Spam1', 'Spam2')
````

You can inject environment variables to the modules you will import by the use of `env_injector` option of `DynamicImport`.
````python
from pydyimport import DynamicImport

def meaningless_env_injector(path: str, code: bytes):
    return {
        '__meaning__': 'no',
    }

importer = DynamicImport(__file__, env_injector=meaningless_env_injector)
importer.require("path/to/file.py")
````

You can inject require* functions by `RequireEnvInjector`,
````python
from pydyimport import DynamicImport
from pydyimport.injector import RequireEnvInjector
require = DynamicImport(__file__, env_injector=RequireEnvInjector(next_injector=None))

require('path/to/module.py')
````
or just set `inject_require` `True`.
````python
from pydyimport import DynamicImport
require = DynamicImport(__file__, inject_require=True)

require('path/to/module.py')
````
If your source contains `# inject_require`, the require* functions will automatically inject require* functions to the module.
````python
#!/usr/bin/env python
# inject_require

require('path/to/module.py')
Spam1, foo = require_only('path/to/module2.py', 'Spam1', 'foo')
````


## License
GNU GENERAL PUBLIC LICENSE, version 3 or later.
````
    PyDyImport - dynamically importing and avoid mess in python
    Copyright (C) 2020 thisLight

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.
````
django-terra-utils 0.3.11
Common utils for terra apps.

[![Build Status](https://travis-ci.org/Terralego/django-terra-utils.svg?branch=master)](https://travis-ci.org/Terralego/django-terra-utils)
[![codecov](https://codecov.io/gh/Terralego/django-terra-utils/branch/master/graph/badge.svg)](https://codecov.io/gh/Terralego/django-terra-utils)
[![Maintainability](https://api.codeclimate.com/v1/badges/5e60cc95c683ab4fb31c/maintainability)](https://codeclimate.com/github/Terralego/django-terra-utils/maintainability)

https://django-terra-utils.readthedocs.io/en/latest/

Helpers and default configuration endpoints for terralego application.


0.3.11 (2020-08-25)
-------------------

Update :

* Support django 3.1


0.3.10 (2019-12-13)
-------------------

Update:

* Update documentation
* Support django 3.0


0.3.9 (2019-10-22)
-------------------

New:

* Extract from terra-back helper for X-Accel-Redirect, to serve medias

0.3.8  (2019-10-15)
-------------------

Update :

* Delete TokenGenerator since it was splitted to single package django-token-tools

0.3.7  (2019-10-11)
-------------------

Update :

* Add a TokenGenerator to allow authentication through URL

0.3.5  (2019-09-24)
-------------------

Fixes :

* fix settings call

0.3.1  (2019-09-24)
-------------------

Update :

* add default settings for HOSTNAME and FRONT_URL

0.3.0  (2019-09-23)
-------------------

First release from splitted terracommon.core