diff --git a/django-debreach-2.0.1.tar.gz b/django-debreach-2.0.1.tar.gz new file mode 100644 index 0000000..6919581 Binary files /dev/null and b/django-debreach-2.0.1.tar.gz differ diff --git a/python-django-debreach.spec b/python-django-debreach.spec new file mode 100644 index 0000000..1385aa6 --- /dev/null +++ b/python-django-debreach.spec @@ -0,0 +1,56 @@ +%global pypi_name django-debreach + +Name: python-%{pypi_name} +Version: 2.0.1 +Release: 1 +Summary: Basic/extra mitigation against the BREACH attack for Django projects + +License: BSD +URL: http://github.com/lpomfrey/django-debreach +Source0: https://files.pythonhosted.org/packages/source/d/%{pypi_name}/%{pypi_name}-%{version}.tar.gz +BuildArch: noarch + +BuildRequires: python3-devel +BuildRequires: python3-Django +BuildRequires: python3-setuptools +BuildRequires: python3-sphinx + +%description +Basic/extra mitigation against the BREACH attack for Django projects. + +When combined with rate limiting in your web-server, or by using something +like django-ratelimit, the techniques here should provide at least some +protection against the BREACH attack. + +%package -n python3-%{pypi_name} +Summary: %{summary} +%{?python_provide:%python_provide python3-%{pypi_name}} +Requires: python3dist(django) >= 2.0 +%description -n python3-%{pypi_name} +Basic/extra mitigation against the BREACH attack for Django projects. + +When combined with rate limiting in your web-server, or by using something +like django-ratelimit, the techniques here should provide at least some +protection against the BREACH attack. + +%prep +%autosetup -n %{pypi_name}-%{version} +# Remove bundled egg-info +rm -rf %{pypi_name}.egg-info + +%build +%py3_build +%install +%py3_install +%check +PYTHONPATH=. %{__python3} setup.py test + +%files -n python3-%{pypi_name} +%license LICENSE +%doc README.rst +%{python3_sitelib}/debreach +%{python3_sitelib}/django_debreach-%{version}-py%{python3_version}.egg-info + +%changelog +* Wed Jan 29 2021 liusheng - 2.0.1-1 +- Init package for python-django-debreach