summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--.gitignore1
-rw-r--r--python-cryptacular.spec148
-rw-r--r--sources1
3 files changed, 150 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..b15800a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/cryptacular-1.6.2.tar.gz
diff --git a/python-cryptacular.spec b/python-cryptacular.spec
new file mode 100644
index 0000000..b878b80
--- /dev/null
+++ b/python-cryptacular.spec
@@ -0,0 +1,148 @@
+%global _empty_manifest_terminate_build 0
+Name: python-cryptacular
+Version: 1.6.2
+Release: 1
+Summary: A password hashing framework with bcrypt and pbkdf2.
+License: MIT
+URL: https://github.com/dholth/cryptacular/
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/42/69/34d478310d6c4451e5ddeabe879b28cc304173e0301b3568eca88ec65112/cryptacular-1.6.2.tar.gz
+BuildArch: noarch
+
+Requires: python3-pytest
+Requires: python3-pytest-cov
+Requires: python3-pbkdf2
+Requires: python3-setuptools
+
+%description
+Hash responsibly::
+ from cryptacular.bcrypt import BCRYPTPasswordManager
+ manager = BCRYPTPasswordManager()
+ hashed = manager.encode('password')
+ if manager.check(hashed, 'password'):
+ pass # let them in
+cryptacular is a collection of strong password hashing functions that
+share a common interface, and a nice way to use bcrypt as a password
+hash. It's designed to make it easy for you to migrate away from your
+half-assed custom password scheme. Compared with popular choices like
+plain text or single rounds of md5 or sha, strong password hashes greatly
+increase the computational cost of obtaining users' passwords from a
+leaked password database.
+cryptacular's interface was inspired by zope.password but cryptacular does
+not depend on zope and implements much stronger algorithms. cryptacular
+also provides a convenient way to recognize and upgrade obsolete password
+hashes on the fly when users log in with their correct password.
+`z3c.bcrypt`_ integrates cryptacular into zope.password.
+http://chargen.matasano.com/chargen/2007/9/7/enough-with-the-rainbow-tables-what-you-need-to-know-about-s.html
+explains why bcrypt is a good idea. Computers are fast now. To protect
+our users against a leaked password database, we should use password
+hashes that take a little longer to check than sha1(salt + hash). bcrypt
+and pbkdf2 have this property. They also have parametric complexity so
+they can be made stronger as computers continue to get faster.
+cryptacular ships with 100% test coverage.
+
+%package -n python3-cryptacular
+Summary: A password hashing framework with bcrypt and pbkdf2.
+Provides: python-cryptacular
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-cryptacular
+Hash responsibly::
+ from cryptacular.bcrypt import BCRYPTPasswordManager
+ manager = BCRYPTPasswordManager()
+ hashed = manager.encode('password')
+ if manager.check(hashed, 'password'):
+ pass # let them in
+cryptacular is a collection of strong password hashing functions that
+share a common interface, and a nice way to use bcrypt as a password
+hash. It's designed to make it easy for you to migrate away from your
+half-assed custom password scheme. Compared with popular choices like
+plain text or single rounds of md5 or sha, strong password hashes greatly
+increase the computational cost of obtaining users' passwords from a
+leaked password database.
+cryptacular's interface was inspired by zope.password but cryptacular does
+not depend on zope and implements much stronger algorithms. cryptacular
+also provides a convenient way to recognize and upgrade obsolete password
+hashes on the fly when users log in with their correct password.
+`z3c.bcrypt`_ integrates cryptacular into zope.password.
+http://chargen.matasano.com/chargen/2007/9/7/enough-with-the-rainbow-tables-what-you-need-to-know-about-s.html
+explains why bcrypt is a good idea. Computers are fast now. To protect
+our users against a leaked password database, we should use password
+hashes that take a little longer to check than sha1(salt + hash). bcrypt
+and pbkdf2 have this property. They also have parametric complexity so
+they can be made stronger as computers continue to get faster.
+cryptacular ships with 100% test coverage.
+
+%package help
+Summary: Development documents and examples for cryptacular
+Provides: python3-cryptacular-doc
+%description help
+Hash responsibly::
+ from cryptacular.bcrypt import BCRYPTPasswordManager
+ manager = BCRYPTPasswordManager()
+ hashed = manager.encode('password')
+ if manager.check(hashed, 'password'):
+ pass # let them in
+cryptacular is a collection of strong password hashing functions that
+share a common interface, and a nice way to use bcrypt as a password
+hash. It's designed to make it easy for you to migrate away from your
+half-assed custom password scheme. Compared with popular choices like
+plain text or single rounds of md5 or sha, strong password hashes greatly
+increase the computational cost of obtaining users' passwords from a
+leaked password database.
+cryptacular's interface was inspired by zope.password but cryptacular does
+not depend on zope and implements much stronger algorithms. cryptacular
+also provides a convenient way to recognize and upgrade obsolete password
+hashes on the fly when users log in with their correct password.
+`z3c.bcrypt`_ integrates cryptacular into zope.password.
+http://chargen.matasano.com/chargen/2007/9/7/enough-with-the-rainbow-tables-what-you-need-to-know-about-s.html
+explains why bcrypt is a good idea. Computers are fast now. To protect
+our users against a leaked password database, we should use password
+hashes that take a little longer to check than sha1(salt + hash). bcrypt
+and pbkdf2 have this property. They also have parametric complexity so
+they can be made stronger as computers continue to get faster.
+cryptacular ships with 100% test coverage.
+
+%prep
+%autosetup -n cryptacular-1.6.2
+
+%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-cryptacular -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed Apr 12 2023 Python_Bot <Python_Bot@openeuler.org> - 1.6.2-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..b2b5b43
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+01d5a0b5267b7f0adb84b861ae334952 cryptacular-1.6.2.tar.gz