Hello community, here is the log from the commit of package python-keyczar for openSUSE:Factory checked in at 2013-04-18 15:00:46 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-keyczar (Old) and /work/SRC/openSUSE:Factory/.python-keyczar.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-keyczar", Maintainer is "" Changes: -------- New Changes file: --- /dev/null 2013-04-05 00:01:41.916011506 +0200 +++ /work/SRC/openSUSE:Factory/.python-keyczar.new/python-keyczar.changes 2013-04-18 15:00:49.000000000 +0200 @@ -0,0 +1,37 @@ +------------------------------------------------------------------- +Thu Apr 18 06:19:15 UTC 2013 - [email protected] + +- add LICENSE file to doc + +------------------------------------------------------------------- +Wed Apr 17 09:40:43 UTC 2013 - [email protected] + +- update to version 0.71c: + + Remove hashbangs from code + + Make test files executable + + Add LICENSE file to repo and MANIFEST.in to comply with ASL 2.0 + + Bumped version to 0.71c in setup.py etc. +- added man page +- specfile cleanup + +------------------------------------------------------------------- +Sat Sep 22 10:42:46 UTC 2012 - [email protected] + +- update to version 0.71b + +------------------------------------------------------------------- +Wed Oct 13 21:15:17 CEST 2010 - [email protected] + +- fix too small rsa key size for test case + +------------------------------------------------------------------- +Thu Aug 20 16:35:27 CEST 2009 - [email protected] + +- add patch to show max oaep size + +------------------------------------------------------------------- +Thu Aug 20 13:43:37 CEST 2009 - [email protected] + +- Initial creation of package python-keyczar-0.6b + +------------------------------------------------------------------- New: ---- keyczart.1 python-keyczar-0.71c.tar.bz2 python-keyczar.changes python-keyczar.spec ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-keyczar.spec ++++++ # # spec file for package python-keyczar # # Copyright (c) 2009-2013 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # %define pkgname keyczar Name: python-keyczar Version: 0.71c Release: 1 License: Apache-2.0 Summary: Toolkit for safe and simple cryptography Url: http://www.keyczar.org Group: Development/Languages/Python Source0: %{name}-%{version}.tar.bz2 Source1: keyczart.1 BuildRequires: python-asn1 >= 0.0.8a BuildRequires: python-devel BuildRequires: python-pycrypto Requires: python-asn1 >= 0.0.8a Requires: python-pycrypto BuildRoot: %{_tmppath}/%{name}-%{version}-build %if 0%{?suse_version} %py_requires %if 0%{?suse_version} > 1110 BuildArch: noarch %endif %endif %{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")} %{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib(1)")} %description Keyczar is an open source cryptographic toolkit designed to make it easier and safer for developers to use cryptography in their applications. Keyczar supports authentication and encryption with both symmetric and asymmetric keys. Some features of Keyczar include: - A simple API - Key rotation and versioning - Safe default algorithms, modes, and key lengths - Automated generation of initialization vectors and ciphertext signatures - Keyczar was originally developed by members of the Google Security Team %prep %setup -q find . -name \*.py -exec sed -i 's|#!/usr/bin/python2.4|#!%{_bindir}/python|g' {} \; %build python setup.py build %check export PYTHONPATH=$(pwd)/build/lib cd tests/keyczar_tests python alltests.py %install python setup.py install --prefix=%{_prefix} --root=%{buildroot} # install keyczart.py as an executable binary echo "#!%{_bindir}/python" >> %{buildroot}%{python_sitelib}/keyczar/keyczart.py.new cat %{buildroot}%{python_sitelib}/keyczar/keyczart.py >> %{buildroot}%{python_sitelib}/keyczar/keyczart.py.new mv %{buildroot}%{python_sitelib}/keyczar/keyczart.py.new %{buildroot}%{python_sitelib}/keyczar/keyczart.py chmod +x %{buildroot}%{python_sitelib}/keyczar/keyczart.py mkdir -p %{buildroot}%{_bindir} ln -s ../../%{python_sitelib}/keyczar/keyczart.py %{buildroot}%{_bindir}/keyczart # include man page install -Dm644 %{SOURCE1} %{buildroot}%{_mandir}/man1/keyczart.1 %clean rm -rf %{buildroot} %files %defattr(-,root,root) %doc LICENSE README PKG-INFO doc/ %{_mandir}/man1/keyczart.1* %{python_sitelib}/keyczar %{python_sitelib}/python_keyczar-*.egg-info %{_bindir}/keyczart %changelog ++++++ keyczart.1 ++++++ .TH kEYCZART "1" "April 2013" "http://code.google.com/p/keyczar/"; "User Commands" .SH NAME keyczart \- A Cryptographic Toolkit. .SH SYNOPSIS .B keyczart \fR[\fIcommand\fR] \fR[\fIflags\fR] .SH DESCRIPTION Keyczar's goal is to make it easier for application developers to safely use cryptography. Keyczar defaults to safe algorithms, key lengths, and modes, and prevents developers from inadvertently exposing key material. It uses a simple, extensible key versioning system that allows developers to easily rotate and retire keys. .SH OPTIONS .PP \fBCommands:\fR create addkey pubkey promote demote revoke .PP \fBFlags:\fR location name size status purpose destination version asymmetric crypter .SH COMMANDS and FLAGS \fBcreate\fR \fB\-\-location=\fR/path/to/keys \fB\-\-purpose=\fR(crypt|sign) [\fB\-\-name=\fR"A name"] [\fB\-\-asymmetric=\fR(dsa|rsa)] .br Creates a new, empty key set in the given location. This key set must have a purpose of either "crypt" or "sign" and may optionally be given a name. The optional asymmetric flag will generate a public key set of the given algorithm. The "dsa" asymmetric value is valid only for sets with "sign" purpose. .PP \fBaddkey\fR \fB\-\-location=\fR/path/to/keys [\fB\-\-status=\fR(active|primary)] [\fB\-\-size=\fRsize] [\fB\-\-crypter=\fRcrypterLocation] .br Adds a new key to an existing key set. Optionally specify a purpose, which is active by default. Optionally specify a key size in bits. Also optionally specify the location of a set of crypting keys, which will be used to encrypt this key set. .PP \fBpubkey\fR \fB\-\-location=\fR/path/to/keys \fB\-\-destination=\fR/destination .br Extracts public keys from a given key set and writes them to the destination. The "pubkey" command Only works for key sets that were created with the "--asymmetric" flag. .PP \fBpromote\fR \fB\-\-location=\fR/path/to/keys \fB\-\-version=\fRversionNumber .br Promotes the status of the given key version in the given location. Active keys are promoted to primary (which demotes any existing primary key to active). Keys scheduled for revocation are promoted to be active. .PP \fBdemote\fR \fB\-\-location=\fR/path/to/keys \fB\-\-version=\fRversionNumber .br Demotes the status of the given key version in the given location. Primary keys are demoted to active. Active keys are scheduled for revocation. .PP \fBrevoke\fR \fB\-\-location=\fR/path/to/keys \fB\-\-version=\fRversionNumber .br Revokes the key of the given version number. This key must have been scheduled for revocation by the promote command. WARNING: The key will be destroyed. .br .PP Optional flags are in [brackets]. The notation (a|b|c) means "a", "b", and "c" are the valid choices .SH AUTHOR .PP Arkajit Dey and Stephen Weis .PP Manpage created by Lars Vogdt -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
