Our knowledge base is a comprehensive resource designed to help you get the most out of our products. It includes getting started articles that guide you through initial setup, detailed information on specific features, and troubleshooting resources to assist you with any issues you may encounter. Explore our knowledge base to find helpful information about our products and answers to common questions.
Latest Articles
Getting Started with IPWorks Auth JWT
07/07/2017 - Introduction to the /n software IPWorks Auth JWT component
SecureBlackbox 16: FTPS (FTP over SSL) vs. SFTP (SSH File Transfer Protocol)
07/07/2017 - Comprehensive comparison of FTPS and SFTP
SecureBlackbox 16: Why SecureBlackbox is a Superior Alternative to BouncyCastle
07/02/2017 - Why you should choose SecureBlackbox's professionally developed security components over BouncyCastle
SecureBlackbox 16: Does the price include the European VAT?
06/29/2017 - Does the price include the European VAT?
SecureBlackbox 16: Do I have to pay when distributing your components with my product?
06/29/2017 - Do I have to pay when distributing your components with my product?
SecureBlackbox 16: Is a single-developer license "named" or transferrable?
06/29/2017 - Is a single-developer license "named" or transferrable?
SecureBlackbox 16: Which License Do I Need?
06/29/2017 - I need to develop a project for my client. What kind of license do I need to buy?
SecureBlackbox 16: Basics of PAdES (PDF Advanced Electronic Signatures)
06/27/2017 - Basics of PAdES (PDF Advanced Electronic Signatures)
SecureBlackbox 16: CAdES and Digital Signatures
06/27/2017 - CAdES is a new standard for advanced digital signature. It was introduced by the European Directive on a community framework for Electronic Signatures, which extends the previous standard, CMS, specifying several additional profiles.
SecureBlackbox 16: Introduction to XAdES (XML Advanced Electronic Signatures)
06/27/2017 - In this article we are talking about signing XML documents, though the same mechanism of XML signature can be used to sign any type of data. XML signature may be detached from or attached to signed data. In the latter case, the signature is said to be enveloping when it contains the signed data within itself, or may be enveloped when it comprises a part of the document containing the signed data.