Recent Unique Product Features

  • Integrating KMIP, PKCS 11, and SSH

    Introduction P6R has implemented a PKCS 11 Baseline Consumer as part of a SSH server’s Public Key Authentication protocol (i.e., RFC 4252). This implementation provides centralized Public Key management for SSH installations via the use of KMIP. With our PKCS 11 Consumer, the SSH server looks up a user’s Public Key on a remote KMIP […]

  • P6R’s PKCS 11 Provider

    This document was updated on 14 February 2017. Introduction P6R has implemented the 2.40 Version of the PKCS 11 specification. Our library meets the requirements for conformance of a PKCS 11 Extended Provider and Authentication Token (see PKCS11 Cryptographic Token Interface Profiles Version 2.40, 16-Sep-2014, OASIS Committee Specification 01). Currently, our library supports seven types […]

  • Detailed differences between KMIP 1.0 and 1.1

    This document was updated on 23 August 2014. As part of the process of modifying our KMIP 1.0 protocol implementation to support the new KMIP 1.1 specification we compared the two specifications and listed all of differences in the following document.   Once we had this information we updated our KMIP 1.0 implementation to take the […]

  • P6R KMIP Toolkit Introduction

    This document was updated on 22 Feb 2014. See the related product page SKC. P6R has taken a unique approach in its KMIP toolkit design by supporting the translation of a KMIP binary message into a standard DOM tree.  This approach builds on existing P6R technology that supports parsing JSON into DOM trees.  The result […]

  • A Smart Pointer for p6COM

    Introduction p6ComPtr<> is a smart pointer implementation designed for use with p6COM, P6R’s lite implementation of the Component Object Model. p6COM is the basis for our cross platform server framework as well as the library loader for our library products. p6ComPtr<> is a tool to help prevent component leaks and simplify the use and management […]

  • There is more than one way to evaluate a regular expression

    P6R’s RGX™ 1.0 Regular Expression Engine has some unique features that make it stand out from the crowd. One such feature is its regex-oriented tracing. Several others are described below. First, we have added a new global modifier ‘P6MOD_FULLLOOKBEHIND’. This modifier allows the look behind meta character sequences ‘(?<=’ & ‘(?<!’ to match anywhere in […]

  • Do You Know What Your Regular Expressions Are Doing?

    It can be difficult to derive the correct regular expression for the problem you are trying to solve. There are many internet sites (e.g., Regular Expression Tester) and PC applications that help to construct what seems to be the right expression. However, how do you know that that expression is working properly in a production […]

  • XML to JSON and Back

    1. The Problem There is no standard way of translating an XML document into its JSON equivalent.  An acceptable translation scheme should be lossless (i.e., not lose any of the XML specific information).  Also a translation scheme should ensure that if the JSON document is converted back into XML that important XML aspects of the […]

  • Rule Throttling

    This article describes an advanced feature of P6R’s rule engine. (See our XJR SDK.) An introduction to that rule engine can be found at An XPath Enabled Rule Engine. The current article addresses the issue “how effective are my rules”? Rule Execution Statistics Passing the ‘P6RULE_KEEPSTATS’ flag into the p6IRuleEngine::initialize() method enables a powerful run-time […]

  • <xsl:output method=’json’/>

    Other articles on this site have described the JSON support we have added to our XSLT 2.0 and XPath 2.0 products (see A SAX-like Parser for JSON, XSLT and XPath for JSON, and our XJR SDK.). In this article, we describe two additional extensions to our XSLT 2.0 and DOM parser products to support the […]