freeipa.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove unused imports	Martin Basti	2015-12-23	1	-1/+0
\| \| \| \| \| \| \|	This patch removes unused imports, alse pylint has been configured to check unused imports. Reviewed-By: Jan Cholasta <jcholast@redhat.com>
*	ipa-client-install: add support for Ed25519 SSH keys (RFC 7479)	Petr Spacek	2015-12-01	1	-0/+2
\| \| \| \| \| \|	https://fedorahosted.org/freeipa/ticket/5471 Reviewed-By: Martin Basti <mbasti@redhat.com>
*	Handle binascii.Error from base64.b64decode()	Petr Viktorin	2015-10-22	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In Python 3, the base64.b64decode function raises binascii.Error (a ValueError subclass) when it finds incorrect padding. In Python 2 it raises TypeError. Callers should usually handle ValueError; unless they are specifically concerned with handling base64 padding issues). In some cases, callers should handle ValueError: - ipalib.pkcs10 (get_friendlyname, load_certificate_request): callers should handle ValueError - ipalib.x509 (load_certificate, get_): callers should handle ValueError In other cases ValueError is handled: - ipalib.parameters - ipapython.ssh - ipalib.rpc (json_decode_binary - callers already expect ValueError) - ipaserver.install.ldapupdate Elsewhere no error handling is done, because values come from trusted sources, or are pre-validated: - vault plugin - ipaserver.install.cainstance - ipaserver.install.certs - ipaserver.install.ipa_otptoken_import Reviewed-By: Tomas Babej <tbabej@redhat.com>
*	ipapython.ssh: Port to Python 3	Petr Viktorin	2015-10-07	1	-6/+9
\| \| \| \| \| \| \| \| \|	Sort out the accepted types. Handle Python 3's stricter separation between bytes and unicode. Reviewed-By: David Kupka <dkupka@redhat.com> Reviewed-By: Jan Cholasta <jcholast@redhat.com> Reviewed-By: Martin Basti <mbasti@redhat.com>
*	Alias "unicode" to "str" under Python 3	Jan Cholasta	2015-09-17	1	-0/+5
\| \| \| \| \| \| \| \| \|	The six way of doing this is to replace all occurences of "unicode" with "six.text_type". However, "unicode" is non-ambiguous and (arguably) easier to read. Also, using it makes the patches smaller, which should help with backporting. Reviewed-By: Petr Viktorin <pviktori@redhat.com>
*	Add support for RFC 6594 SSHFP DNS records.	Jan Cholasta	2013-02-01	1	-3/+12
\| \| \| \|	https://fedorahosted.org/freeipa/ticket/2642
*	Drop ipapython.compat.	Jan Cholasta	2013-02-01	1	-2/+1
\|
*	SSHPublicKey.fingerprint_dns_sha1 should return unicode value.	Jan Cholasta	2012-09-20	1	-1/+1
\|
*	Use OpenSSH-style public keys as the preferred format of SSH public keys.	Jan Cholasta	2012-09-06	1	-0/+199
	Public keys in the old format (raw RFC 4253 blob) are automatically converted to OpenSSH-style public keys. OpenSSH-style public keys are now stored in LDAP. Changed sshpubkeyfp to be an output parameter, as that is what it actually is. Allow parameter normalizers to be used on values of any type, not just unicode, so that public key blobs (which are str) can be normalized to OpenSSH-style public keys. ticket 2932, 2935