Some certificate generation libraries can generate certificates that are invalid. Some tools will allow you to work with them, and some won't.
Octopus Deploy uses a common certificate library called Bouncy Castle to parse and work with certificates. Recent versions of this have improved validation of certificates, which has, unfortunately, limited the usability of some certificates that don't strictly comply with the specification.
corrupted stream detected malformed integer
This error implies that a certificate violates the X.690 spec, section 8.3.2.
If you receive this error when creating a deployment, please review the certificate's variables on the project, and try to view each one in Library ➜ Certificates. One of them will either fail to load, or show the message:
Invalid Certificate: This certificate was unable to be parsed and may be in an invalid format. Please modify any references to use a new, valid certificate, and use the REST API to delete the certificate in question.
This error may also appear on the variables page:
An error occurred on the mapping CertificateResource.CertificateDataFomat = Certificate.CertificateDataFormat [attempted value was (unknown)]: corrupted stream detected malformed integer. Please review the certificates in Library ➜ Certificates to find the invalid one, update any usages to use a new valid certificate, and delete the old certificate via the REST API.
Please see BC-CSharp issue #156 for further information.
If deleting the certificate is not an option, Bouncy Castle supports an environment variable that can be set to disable the strict validation. Set an environment variable
Org.BouncyCastle.Asn1.AllowUnsafeInteger to 'true' for the Octopus Server process and a looser validation will be applied, allowing this certificate to be used. However, Bouncy Castle authors have noted that this is not ideal and may pave the way for an exploit based around a faulty encoding in the future.
Unable to parse certificate 'cert name' (id: some-id): corrupted stream detected malformed integer
This is the same root cause as the message above, however, it includes details about which certificate is in error. Please update any uses to a new valid certificate, and use the REST API to delete the certificate in question.
problem parsing cert: Org.BouncyCastle.Security.Certificates.CertificateException: Failed to read certificate ---> System.ArgumentException: version 1 certificate contains extra data
This can happen when certificates include extension data without specifying the certificate format of v3. If the version is omitted, then v1 is implied. Since only v3 certificates are allowed to have this additional data, this leads to an invalid certificate. Please see BC-CSharp issue #158 for further information.
Please review the certificates in Library ➜ Certificates to find the invalid one, update any usages to use a new valid certificate, and delete the old certificate via the REST API.
Need support? We're here to help.