TlsCertificate
Added in version 2.28.
Superclasses: Object
A certificate used for TLS authentication and encryption.
This can represent either a certificate only (eg, the certificate
received by a client from a server), or the combination of
a certificate and a private key (which is needed when acting as a
TlsServerConnection
).
Constructors
- class TlsCertificate
- classmethod new_from_file(file: str) TlsCertificate
Creates a
TlsCertificate
from the data infile
.As of 2.72, if the filename ends in
.p12
or.pfx
the data is loaded bynew_from_pkcs12()
otherwise it is loaded bynew_from_pem()
. See those functions for exact details.If
file
cannot be read or parsed, the function will returnNone
and seterror
.Added in version 2.28.
- Parameters:
file – file containing a certificate to import
- classmethod new_from_file_with_password(file: str, password: str) TlsCertificate
Creates a
TlsCertificate
from the data infile
.If
file
cannot be read or parsed, the function will returnNone
and seterror
.Any unknown file types will error with
NOT_SUPPORTED
. Currently only.p12
and.pfx
files are supported. Seenew_from_pkcs12()
for more details.Added in version 2.72.
- Parameters:
file – file containing a certificate to import
password – password for PKCS
12
files
- classmethod new_from_files(cert_file: str, key_file: str) TlsCertificate
Creates a
TlsCertificate
from the PEM-encoded data incert_file
andkey_file
. The returned certificate will be the first certificate found incert_file
. As of GLib 2.44, ifcert_file
contains more certificates it will try to load a certificate chain. All certificates will be verified in the order found (top-level certificate should be the last one in the file) and theTlsCertificate
:issuer property of each certificate will be set accordingly if the verification succeeds. If any certificate in the chain cannot be verified, the first certificate in the file will still be returned.If either file cannot be read or parsed, the function will return
None
and seterror
. Otherwise, this behaves likenew_from_pem()
.Added in version 2.28.
- Parameters:
cert_file – file containing one or more PEM-encoded certificates to import
key_file – file containing a PEM-encoded private key to import
- classmethod new_from_pem(data: str, length: int) TlsCertificate
Creates a
TlsCertificate
from the PEM-encoded data indata
. Ifdata
includes both a certificate and a private key, then the returned certificate will include the private key data as well. (See theTlsCertificate
:private-key-pem property for information about supported formats.)The returned certificate will be the first certificate found in
data
. As of GLib 2.44, ifdata
contains more certificates it will try to load a certificate chain. All certificates will be verified in the order found (top-level certificate should be the last one in the file) and theTlsCertificate
:issuer property of each certificate will be set accordingly if the verification succeeds. If any certificate in the chain cannot be verified, the first certificate in the file will still be returned.Added in version 2.28.
- Parameters:
data – PEM-encoded certificate data
length – the length of
data
, or -1 if it’s 0-terminated.
- classmethod new_from_pkcs11_uris(pkcs11_uri: str, private_key_pkcs11_uri: str | None = None) TlsCertificate
Creates a
TlsCertificate
from aPKCS ``11`
<https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/os/pkcs11-base-v3.0-os.html>`_ URI.An example
pkcs11_uri
would bepkcs11:model=Model;manufacturer=Manufacture;serial=1;token=My``%20Client````%20Certificate`
;id=``%01```Where the token’s layout is:
Object 0: URL: pkcs11:model=Model;manufacturer=Manufacture;serial=1;token=My``%20Client````%20Certificate``;id=``%01``;object=private``%20key``;type=private Type: Private key (RSA-2048) ID: 01 Object 1: URL: pkcs11:model=Model;manufacturer=Manufacture;serial=1;token=My``%20Client````%20Certificate``;id=``%01``;object=Certificate``%20for````%20Authentication``;type=cert Type: X.509 Certificate (RSA-2048) ID: 01
In this case the certificate and private key would both be detected and used as expected.
pkcs_uri
may also just reference an X.509 certificate object and then optionallyprivate_key_pkcs11_uri
allows using a private key exposed under a different URI.Note that the private key is not accessed until usage and may fail or require a PIN later.
Added in version 2.68.
- Parameters:
pkcs11_uri – A PKCS ``11`` URI
private_key_pkcs11_uri – A PKCS ``11`` URI
- classmethod new_from_pkcs12(data: Sequence[int], password: str | None = None) TlsCertificate
Creates a
TlsCertificate
from the data indata
. It must contain a certificate and matching private key.If extra certificates are included they will be verified as a chain and the
TlsCertificate
:issuer property will be set. All other data will be ignored.You can pass as single password for all of the data which will be used both for the PKCS
12
container as well as encrypted private keys. If decryption fails it will error withBAD_CERTIFICATE_PASSWORD
.This constructor requires support in the current
TlsBackend
. If support is missing it will error withNOT_SUPPORTED
.Other parsing failures will error with
BAD_CERTIFICATE
.Added in version 2.72.
- Parameters:
data – DER-encoded PKCS
12
format certificate datapassword – optional password for encrypted certificate data
Methods
- class TlsCertificate
- get_dns_names() list[Bytes] | None
Gets the value of
TlsCertificate
:dns-names.Added in version 2.70.
- get_ip_addresses() list[InetAddress] | None
Gets the value of
TlsCertificate
:ip-addresses.Added in version 2.70.
- get_issuer() TlsCertificate | None
Gets the
TlsCertificate
representingcert
’s issuer, if knownAdded in version 2.28.
- get_not_valid_after() DateTime | None
Returns the time at which the certificate became or will become invalid.
Added in version 2.70.
- get_not_valid_before() DateTime | None
Returns the time at which the certificate became or will become valid.
Added in version 2.70.
- get_subject_name() str | None
Returns the subject name from the certificate.
Added in version 2.70.
- is_same(cert_two: TlsCertificate) bool
Check if two
TlsCertificate
objects represent the same certificate. The raw DER byte data of the two certificates are checked for equality. This has the effect that two certificates may compare equal even if theirTlsCertificate
:issuer,TlsCertificate
:private-key, orTlsCertificate
:private-key-pem properties differ.Added in version 2.34.
- Parameters:
cert_two – second certificate to compare
- list_new_from_file(file: str) list[TlsCertificate]
Creates one or more
TlsCertificate
from the PEM-encoded data infile
. Iffile
cannot be read or parsed, the function will returnNone
and seterror
. Iffile
does not contain any PEM-encoded certificates, this will return an empty list and not seterror
.Added in version 2.28.
- Parameters:
file – file containing PEM-encoded certificates to import
- verify(identity: SocketConnectable | None = None, trusted_ca: TlsCertificate | None = None) TlsCertificateFlags
This verifies
cert
and returns a set ofTlsCertificateFlags
indicating any problems found with it. This can be used to verify a certificate outside the context of making a connection, or to check a certificate against a CA that is not part of the system CA database.If
cert
is valid,NO_FLAGS
is returned.If
identity
is notNone
,cert
’s name(s) will be compared against it, andBAD_IDENTITY
will be set in the return value if it does not match. Ifidentity
isNone
, that bit will never be set in the return value.If
trusted_ca
is notNone
, thencert
(or one of the certificates in its chain) must be signed by it, or elseUNKNOWN_CA
will be set in the return value. Iftrusted_ca
isNone
, that bit will never be set in the return value.GLib guarantees that if certificate verification fails, at least one error will be set in the return value, but it does not guarantee that all possible errors will be set. Accordingly, you may not safely decide to ignore any particular type of error. For example, it would be incorrect to mask
EXPIRED
if you want to allow expired certificates, because this could potentially be the only error flag set even if other problems exist with the certificate.Because TLS session context is not used,
TlsCertificate
may not perform as many checks on the certificates asTlsConnection
would. For example, certificate constraints may not be honored, and revocation checks may not be performed. The best way to verify TLS certificates used by a TLS connection is to letTlsConnection
handle the verification.Added in version 2.28.
- Parameters:
identity – the expected peer identity
trusted_ca – the certificate of a trusted authority
Properties
- class TlsCertificate
- props.certificate: Sequence[int]
The DER (binary) encoded representation of the certificate. This property and the
TlsCertificate
:certificate-pem property represent the same data, just in different forms.Added in version 2.28.
- props.certificate_pem: str
The PEM (ASCII) encoded representation of the certificate. This property and the
TlsCertificate
:certificate property represent the same data, just in different forms.Added in version 2.28.
- props.dns_names: Sequence[None]
The DNS names from the certificate’s Subject Alternative Names (SANs),
None
if unavailable.Added in version 2.70.
- props.ip_addresses: Sequence[None]
The IP addresses from the certificate’s Subject Alternative Names (SANs),
None
if unavailable.Added in version 2.70.
- props.issuer: TlsCertificate
A
TlsCertificate
representing the entity that issued this certificate. IfNone
, this means that the certificate is either self-signed, or else the certificate of the issuer is not available.Beware the issuer certificate may not be the same as the certificate that would actually be used to construct a valid certification path during certificate verification. RFC 4158 explains why an issuer certificate cannot be naively assumed to be part of the the certification path (though GLib’s TLS backends may not follow the path building strategies outlined in this RFC). Due to the complexity of certification path building, GLib does not provide any way to know which certification path will actually be used. Accordingly, this property cannot be used to make security-related decisions. Only GLib itself should make security decisions about TLS certificates.
Added in version 2.28.
- props.issuer_name: str
The issuer from the certificate,
None
if unavailable.Added in version 2.70.
- props.not_valid_after: DateTime
The time at which this cert is no longer valid,
None
if unavailable.Added in version 2.70.
- props.not_valid_before: DateTime
The time at which this cert is considered to be valid,
None
if unavailable.Added in version 2.70.
- props.password: str
An optional password used when constructed with GTlsCertificate:pkcs12-data.
Added in version 2.72.
- props.pkcs11_uri: str
A URI referencing the
PKCS ``11`
<https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/os/pkcs11-base-v3.0-os.html>`_ objects containing an X.509 certificate and optionally a private key.If
None
, the certificate is either not backed by PKCS ``11`` or theTlsBackend
does not support PKCS ``11``.Added in version 2.68.
- props.pkcs12_data: Sequence[int]
The PKCS
12
formatted data used to construct the object.See also:
new_from_pkcs12()
Added in version 2.72.
- props.private_key: Sequence[int]
The DER (binary) encoded representation of the certificate’s private key, in either
PKCS ``1`
format <https://datatracker.ietf.org/doc/html/rfc8017>`_ or unencryptedPKCS ``8`
format. <https://datatracker.ietf.org/doc/html/rfc5208>`_ PKCS ``8`` format is supported since 2.32; earlier releases only support PKCS ``1``. You can use theopenssl rsa
tool to convert PKCS ``8`` keys to PKCS ``1``.This property (or the
TlsCertificate
:private-key-pem property) can be set when constructing a key (for example, from a file). Since GLib 2.70, it is now also readable; however, be aware that if the private key is backed by a PKCS ``11`` URI – for example, if it is stored on a smartcard – then this property will beNone
. If so, the private key must be referenced via its PKCS ``11`` URI,TlsCertificate
:private-key-pkcs11-uri. You must check both properties to see if the certificate really has a private key. When this property is read, the output format will be unencrypted PKCS ``8``.Added in version 2.28.
- props.private_key_pem: str
The PEM (ASCII) encoded representation of the certificate’s private key in either
PKCS ``1`
format <https://datatracker.ietf.org/doc/html/rfc8017>`_ (”BEGIN RSA PRIVATE KEY
”) or unencryptedPKCS ``8`
format <https://datatracker.ietf.org/doc/html/rfc5208>`_ (”BEGIN PRIVATE KEY
”). PKCS ``8`` format is supported since 2.32; earlier releases only support PKCS ``1``. You can use theopenssl rsa
tool to convert PKCS ``8`` keys to PKCS ``1``.This property (or the
TlsCertificate
:private-key property) can be set when constructing a key (for example, from a file). Since GLib 2.70, it is now also readable; however, be aware that if the private key is backed by a PKCS ``11`` URI - for example, if it is stored on a smartcard - then this property will beNone
. If so, the private key must be referenced via its PKCS ``11`` URI,TlsCertificate
:private-key-pkcs11-uri. You must check both properties to see if the certificate really has a private key. When this property is read, the output format will be unencrypted PKCS ``8``.Added in version 2.28.
- props.private_key_pkcs11_uri: str
A URI referencing a
PKCS ``11`
<https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/os/pkcs11-base-v3.0-os.html>`_ object containing a private key.Added in version 2.68.
Virtual Methods
- class TlsCertificate
- do_verify(identity: SocketConnectable | None = None, trusted_ca: TlsCertificate | None = None) TlsCertificateFlags
This verifies
cert
and returns a set ofTlsCertificateFlags
indicating any problems found with it. This can be used to verify a certificate outside the context of making a connection, or to check a certificate against a CA that is not part of the system CA database.If
cert
is valid,NO_FLAGS
is returned.If
identity
is notNone
,cert
’s name(s) will be compared against it, andBAD_IDENTITY
will be set in the return value if it does not match. Ifidentity
isNone
, that bit will never be set in the return value.If
trusted_ca
is notNone
, thencert
(or one of the certificates in its chain) must be signed by it, or elseUNKNOWN_CA
will be set in the return value. Iftrusted_ca
isNone
, that bit will never be set in the return value.GLib guarantees that if certificate verification fails, at least one error will be set in the return value, but it does not guarantee that all possible errors will be set. Accordingly, you may not safely decide to ignore any particular type of error. For example, it would be incorrect to mask
EXPIRED
if you want to allow expired certificates, because this could potentially be the only error flag set even if other problems exist with the certificate.Because TLS session context is not used,
TlsCertificate
may not perform as many checks on the certificates asTlsConnection
would. For example, certificate constraints may not be honored, and revocation checks may not be performed. The best way to verify TLS certificates used by a TLS connection is to letTlsConnection
handle the verification.Added in version 2.28.
- Parameters:
identity – the expected peer identity
trusted_ca – the certificate of a trusted authority