Technical support for secrypt customers by telephone, e-mail & remote

Hotline & E-Mail-Support

Customers without support contract please contact:

Hotline: 0900 1 732797
Mon-Fri: 9-12h + 13-15h
(1,99 € per minute from a German landline)

support@secrypt.de

Customers with support contract please use the contact ways mentioned in the contract.

FAQs – Frequently asked questions

Some questions are asked more frequently, e.g. for signature verification with Adobe Reader.

Take a look and see if you can find an answer here!

To the FAQs

Remote-Support

We use the product TeamViewer for secure remote access and remote support.

Download TeamViewer

Support form

For technical questions please contact our support!
(* Mandatory fields)

FAQs – Frequently Asked Questions

What is important when checking a signed PDF document with Adobe Reader?

Use the latest version of Adobe Reader:
You can get “Adobe Acrobat Reader DC” on the website https://get.adobe.com/de/reader/
Older versions of Adobe Reader do not support the current cryptographic algorithms used for signatures.

As of May 2019, Adobe is not supporting signature verification based on elliptic curve cryptography (ECC or ECDSA).
For verification of such signatures we recommend the use of the software digiSeal reader.

How do I integrate an individual signature graphic (e.g. scanned signature, logo) into my PDF document during signing?

To set up your individual PDF signature stamp with digiSeal office (pro), please open the menu item “Options” -> “General Settings…”. 3rd PDF signature”. In the “Graphical representation of signature information in the PDF document” section, you will find the “+” symbol under “Type”. Press this “+” symbol and select a BMP or PNG file with the graphic you want. You can use your scanned signature or your company logo, for example.

How do I select the correct signature format, e.g. signature embedded in PDF or adjacent signature?

digiSeal office (pro) supports the signature formats CAdES, PAdES and XAdES specified by ETSI and recognised within the framework of the eIDAS regulation. These signature formats are further developments and extensions of the CMS (Cryptographic Message Syntax) and PKCS#7 standards.

The PAdES signature format is used to embed the signature in PDF documents.

The XAdES signature format allows the signature to be embedded in XML data.

The CAdES signature format can be applied to any data type.

The configuration of the signature formats can be found under the digiSeal office (pro) menu item “Options” -> “General Settings…” 2nd signature exchange formats”.

By default, signatures for PDF documents in PAdES format are embedded directly in the PDF and for XML data in XAdES format directly in the XML. For all other data types, detached signature files are generated in CAdES format. These signatures have the file extension P7S.

If you do not want to create PDF files with an embedded PAdES signature, but with an adjacent CAdES signature, you must uncheck “PDF documents” in the same dialog in the “Signature exchange formats for specific file formats” area.

Which online connections do I need to verify a signature or the certificate validity status?

When a signature is verified, the certificate validity status is checked online. You may need to configure your firewalls for the protocols used.

The following protocols are used for verification:

1st OCSP / Online Certificate Status Protocol / RFC 2560
The OCSP responders are specified in the certificates to be verified.
Example OCSP responder address: URL: http://ocsp-sha256.d-trust.net
Default port: 80 for HTTP, 443 for HTTPS
HTTP header entries: application/ocsp-request/application/ocsp-response

CRL / Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List Profile / RFC 5280

The CRL responders are specified in the certificates to be verified.

Example CRL responder address:
URL: ldap://directory.d-trust.net/CN=Test%20D-TRUST%20SHA2%20CA,O=D-Trust%20GmbH,C=DE?certificaterevocationlist

Example CRL responder address:
URL: http://www.d-trust.net/crl/test_d-trust_sha2_ca.crl
Standard ports: 80 for HTTP, 443 for HTTPS, 389 for LDAP, 636 for LDAPS
HTTP header entries: application/pkix-crl

Please use packet filters for RFCs 2560 and 5280.
For all protocols, other ports can of course also be specified in the URLs in the certificates. Corresponding rules should only be inserted if necessary.