Skip to main content
  1. Open Source/


IDMask - Encryption and Obfuscation of IDs #

IDMask Logo

IDMask is a Java library for masking internal IDs (e.g. from your DB) when they need to be publicly published to hide their actual value and to prevent forging. This should make it very hard for an attacker to understand provided IDs (e.g. by witnessing a sequence, deducting how many orders you had, etc.) and prevent guessing of possible valid ones. Masking is fully reversible and also supports optional randomization for e.g. shareable links or one-time tokens. It has a wide support for various Java types including long, UUID and BigInteger. This library bases its security on strong cryptographic primitives (AES, HMAC, HKDF) to create a secure encryption schema. It was inspired by HashIds but tries to tackle most of its shortcomings.

Feature Overview #

  • Secure: Creates encrypted IDs with no-nonsense cryptography (AES, HKDF) including forgery protection (HMAC)
  • Wide range of Java type support: mask IDs from long, UUID, BigInteger, LongTuple and byte[]
  • Full support of types: no arbitrary restrictions like “only positive longs”, etc.
  • ID randomization: if enabled, will create IDs which appear uncorrelated with the same underlying value.
  • No collisions possible: because the IDs are not hashed or otherwise compressed, collisions are impossible
  • Built-in caching support: to increase performance a simple caching framework can be facilitated.
  • Lightweight & Easy-to-use: the library has only minimal dependencies and a straight forward API
  • Fast: 8 byte IDs take about 2µs and 16 byte IDs 7µs to mask on a fast desktop machine (see JMH Benchmarks)
  • Supports multiple encodings: Depending on your requirement (short IDs vs. readability vs. should not contain words) multiple encodings are available including Base64, Base32 and Hex with the option of providing a custom one.
  • Includes default implementations for various serializer: Jackson serializer, JAX-RS ParamConverter

The code is compiled with target Java 7 to keep backwards compatibility with Android and older Java applications.

Quickstart #

Add the dependency to your pom.xml (check latest release):


A very simple example using 64-bit integers (long):

byte[] key = Bytes.random(16).array();
long id = ...

IdMask<Long> idMask = IdMasks.forLongIds(Config.builder(key).build());

String maskedId = idMask.mask(id);
//example: NPSBolhMyabUBdTyanrbqT8
long originalId = idMask.unmask(maskedId);

alternatively using UUIDs:

UUID id = UUID.fromString("eb1c6999-5fc1-4d5f-b98a-792949c38c45");

IdMask<UUID> idMask = IdMasks.forUuids(Config.builder(key).build());

String maskedId = idMask.mask(id);
//example: rK0wpnG1lwvG0xiZn5swxOYmAvxhA4A7yg
UUID originalId = idMask.unmask(maskedId);

Examples for other java types (e.g. BigInteger, byte[] and LongTuple), see below.

How-To #

The following section explains in detail how to use and configure IDMask:

  • Step 1: How to create your secret key
    • Option A: Random Number Generator CLI
    • Option B: Generate a Random Key within a Java Runtime
  • Step 2: Select the Java type to use
    • Option A: long
    • Option B: UUID
    • Option C: BigInteger
    • Option D: LongTuple
    • Option E: byte[]
    • Option F: multiple int
  • Step 3: Adjust the configuration to your needs
    • Q1: Deterministic or Random?
    • Q2: Which encoding?
    • Q3: Caching?
    • Q4: Advanced Security Features?
  • Additional Features: key migration, error-handling, converter for Jackson and JAX-RS

Step 1: Create a Secret Key #

IDMask’s security relies on the strength of the used cryptographic key. In its rawest from, a secret key is basically just a random byte array. A provided key should be at least 16 bytes long (longer usually doesn’t translate to better security). IDMask requires it to be between 12 and 64. There are multiple ways to manage secret keys, if your project already has a managed KeyStore or similar, use it. Otherwise, you could just hardcode the key in your code. This, of course, only makes sense where the client doesn’t have access to the source or binary (i.e. in a backend scenario). Here are some suggestion on how to create your secret key:

Option A: Use Random Number Generator CLI #

One of the easiest ways to create a high quality key is to use this java cli: Dice. Just download the .jar (or .exe) and run:

java -jar dice.jar 16 -e "java"

This will generate multiple 16 byte long syntactically correct java byte arrays:

new byte[]{(byte) 0xE4, (byte) 0x8A, ...};

You could just hard code this value:

private static final byte[] ID_MASK_KEY = new byte[]{(byte) 0xE4, (byte) 0x8A, ...};

Option B: Generate a Random Key within a Java Runtime #

Either in the debugger, simple application or any other REPL execute the following code (IDMask must be in classpath):


which will create a random byte array using SecureRandom and encodes it as hex string. In your code use this hex parser and the previously generated string:

private static final byte[] ID_MASK_KEY = Bytes.parseHex("e48a....").array();

Either way, don’t worry too much as the library supports changing the secret key while still supporting unmasking of older IDs.

Step 2: Choosing the correct Type #

IDMask basically supports 2 data types:

  • 64 bit long words (8 byte): long
  • 128 bit long words (16 byte): UUID, BigInteger, byte[], LongTuple

Data types with these byte lengths can be represented as various Java types often used as identifiers:

Option A: 64-bit integers (long) #

The most common case and the only one fitting in the ‘8 byte’ category is an id with the type long. In Java a long is a signed integer and can represent -2^63 to 2^63 -1. IDMask can mask any valid long value. Internally it will be represented as 8 byte, two’s complement.

Create a new instance by calling:

IdMask<Long> idMask = IdMasks.forLongIds(Config.builder(key).build());
String masked = idMask.mask(-588461182736122L);

It is of course possible to also pass int types by casting them:

String masked = idMask.mask((long) 1780);

Note that the generated masked id will not be shorter when using 32-bit integers.

Option B: Universally unique identifier (UUIDs) #

A UUID is a 128 bit long identifier (with 122 bit entropy) and often used in databases because one does not have to worry about sequences or duplicates, but can just generate unique IDs by choosing one randomly. Java has first level support for UUIDs for generation, parsing and serialization.

Create a new instance by calling:

IdMask<UUID> idMask = IdMasks.forUuids(Config.builder(key).build());
String masked = idMask.mask(UUID.fromString("eb1c6999-5fc1-4d5f-b98a-792949c38c45"));

Option C: Arbitrary-Precision Integers (BigInteger) #

If your IDs are typed as BigInteger you can either convert them to long (if they are bound to 64 bit) or use the specific IDMask implementation. Note that the big integer will be converted to a two’s complement byte representation and are supported up to 15 byte length (i.e. up to 2^120).

IdMask<BigInteger> idMask = IdMasks.forBigInteger(Config.builder(key).build());
String masked = idMask.mask(BigInteger.ONE);

Option D: Tuple of 64-bit integers #

Sometimes it makes sense to encode multiple IDs to a single serialized version. Use this if you want to combine two long IDs, making it even harder to understand individual ones within.

IdMask<LongTuple> idMask = IdMasks.forLongTuples(Config.builder(key).build());
String masked = idMask.mask(new LongTuple(182736128L, 33516718189976L));

Option E: 16 byte (128 bit) byte array #

Only for advanced use cases. The most generic way to represent a 128-bit id is as a byte array. Basically you may provide any data as long as it fits in 16 bytes. Note, that this is not a general purpose encryption schema and your data might not be secure!

IdMask<byte[]> idMask = IdMasks.for128bitNumbers(Config.builder(key).build());
String masked = idMask.mask(new byte[] {0xE3, ....});

Option F: Encoding multiple 32-bit integers #

Not supported directly, but still quite easy to implement - if you use only 4 byte (32-bit) integers (int), you can encoded multiple numbers.

Using the long schema you can encode up to two of those:

int intId1 = 1;
int intId2 = 2;

IdMask<Long> idMask = IdMasks.forLongIds(Config.builder(key).build());

long encodedInts = Bytes.from(intId1, intId2).toLong();
String masked = idMask.mask(encodedInts);
long raw = idMask.unmask(masked);
int[] originalIds = Bytes.from(raw).toIntArray(); // originalIds[0] == intId1; originalIds[1] == intId2

or using four 32-bit integers with the byte[] schema:

int intId1 = 1;
int intId2 = 2;
int intId3 = 3;
int intId4 = 4;

IdMask<byte[]> idMask = IdMasks.for128bitNumbers(Config.builder(key).build());

byte[] ids = Bytes.from(intId1, intId2, intId3, intId4).array();
String masked = idMask.mask(ids);
byte[] raw = idMask.unmask(masked);
int[] originalIds = Bytes.from(raw).toIntArray(); // originalIds[0] == intId1; originalIds[1] == intId2,...

Option G: Strings? #

Per design this library lacks the feature to mask string based IDs. This is to discourage using it as general purpose encryption library. In most cases strings are encoded data: e.g. UUIDs string representation, hex, base64, etc. Best practice would be to decode these to a byte array (or UUID if possible) and use any of the other options provided above. (Note: technically it would be possible to convert the string to e.g. ASCII bytes and just feed it IdMask<byte[]> if it’s length is equal or under 16; but this is highly discouraged).

Step 3: IDMask Configuration #

Usually the default settings are fine for most use cases, however it may make sense to adapt to different usage scenarios with the following settings.

Q1: Should Ids be deterministic or random? #

By default, off, the masking algorithm supports randomization of generated IDs. This is achieved by creating a random number and using it as part of the encrypt scheme as well as appending it to the output of the masked id. Therefore, randomized IDs are longer than their deterministic counterpart. Randomization increases the obfuscation effectiveness but makes it impossible for a client to check equality. This usually makes sense with shareable links, random access tokens, or other one-time identifiers. Randomized IDs within models are probably a bad idea.

For instance these masked IDs all represent the same original id 70366123987523049:


Enable with:


Q2: What encoding should I choose? #

The library internally converts everything to bytes, encrypts it and then requires an encoding schema to make the output printable. Per default the url-safe version of Base64 (RFC4648) is used. This is a well-supported, fast and reasonable space efficient (needs ~25% more storage than the raw bytes) encoding. Note that the output size is constant using the same settings a type and does not grow or shrink depending on e.g. how big the number is.

However, depending on your use case, you may want Ids that are easy to type, do not contain possible problematic words or require some maximum length. The library includes some built-in encodings which satisfy different requirements:

Encodingmay contain wordseasy to typeurl safeLength for 64 bit id (deterministic/randomized)Length for 128 bit id (deterministic/randomized)Example
Base32 (Safe Alphabet)no curse wordscontains upper and lowercaseyes28/4040/66jKVJx8yQPP8wkBNQhZBkJr6vKhwH

If IDs should be as short as possible, you may look into using Ascii85/Base85 with a Java implementation here; expect around 8% better space efficiency compared to Base64.

Choose a different encoding by setting the following in the config builder:

    .encoding(new ByteToTextEncoding.Base32Rfc4648())

Implement your own encoding by using the ByteToTextEncoding interface.

Formatted IDs #

For IDs that are better readable for humans you can use the ByteToTextEncoding.Formatter and use it to wrap any other encoding instance with:


For example with Base32 this could look like this


Q3: Do you need Caching? #

By default, a simple in-memory lru cache is enabled. This cache improves performance if recurring IDs are encoded/decoded - if this is not the case the cache should be disabled to safe memory.

This setting is responsible for disabling the cache:


if you want to wire your own cache framework to the id mask library you may do so by implementing the Cache interface and setting:

    .cacheImpl(new MyHazelcastCache())

Q4: Any other Advanced Security Features required? #

You may provide your own JCA provider (like BouncyCastle) or your own cryptographically secure pseudo-random number generator (i.e. a SecureRandom implementation). The provider is used to encrypt/decrypt with AES and to calculate HMACs


    .secureRandom(new SecureRandom())

High Security Mode #

Only applicable with 16 byte IDs (e.g. UUID, byte[], BigInteger, …) it is optionally possible to increase the security strength of the masked id in expense for increased id lengths. By default, an 8-byte MAC is appended to the ID and, if randomization is enabled, an 8-byte random nonce is prepended. In high security mode these numbers double to 16 byte, therefore high security IDs are 16 bytes longer. If you generate a massive amount of IDs (more than 2^32) or don’t mind the longer output length, high security mode is recommended.

Issue with smaller MAC is increased chance of not recognizing a forgery and issue with smaller randomization nonce is higher chance of finding duplicated randomization values and recognizing equal IDs (chance of duplicate after 5,000,000,000 randomized IDs with 8 byte nonce is 50%). Increasing these numbers to 16 bytes make both those issue negligible.

A Full Example #

Here is a fully wired example using the generic byte array IDMask:

IdMask<byte[]> idMask = IdMasks.for128bitNumbers(
                .randomizedIds(true) //non-deterministic output
                .cacheImpl(new Cache.SimpleLruMemCache(64))
                .encoding(new ByteToTextEncoding.Base32Rfc4648())
                .secureRandom(new SecureRandom())

String maskedId = idMask.mask(id128bit);
byte[] originalId = idMask.unmask(maskedId);

Additional Features #

Upgrade of used Secret Key #

If you want to change the secret key, because e.g. it became compromised, but still want to be able to unmask IDs created with the previous key, you can use the built-in key migration scheme. Since every created id encodes the id of the used key, it is possible to choose a different key decryption.

Here is a full example: First a new instance with key1 will be created. If no key-id is passed, the library uses KeyManager.Factory.DEFAULT_KEY_ID.

long id = 123456789L;
byte[] key1 = Bytes.random(16).array();

// create new instance with your key
IdMask<Long> idMask1 = IdMasks.forLongIds(Config.builder(key1).build());
String maskKey1 = idMask1.mask(id);
// e.g.: kpKOdqrNdmyx34-VxjTg6B4

If you want to switch the active key, just generate a new one and also set the old one as legacy key. Mind to choose a different key-id:

// if key1 is compromised create a new key
byte[] key2 = Bytes.random(16).array();

// set the new key as active key and add the old key as legacy key - us the DEFAULT_KEY_ID, is it is used if no key id is set
IdMask<Long> idMask2 = IdMasks.forLongIds(
                new KeyManager.IdSecretKey(KeyManager.Factory.DEFAULT_KEY_ID+1, key2), //new key with a new key id
                new KeyManager.IdSecretKey(KeyManager.Factory.DEFAULT_KEY_ID, key1))) //old key with the DEFAULT_KEY_ID

Masking the same id, with the new key will generate different output:

// same id will create different output
String maskKey2 = idMask2.mask(id);
// e.g.: 3c1UMVvVK5SvNiOaT4btpiQ

Unmasking however will reveal the same underlying id, no matter if it was masked with key1 or key2.

// the new instance can unmask the old a new key
assert idMask2.unmask(maskKey1).equals(idMask2.unmask(maskKey2));

Be aware that changing the secret key, will destroy equality of masked IDs cached with clients or elsewhere.

Error Handling #

An IdMask instance will basically throw 2 types of unchecked exceptions:

  1. IllegalArgumentException
  2. IdMaskSecurityException (extends SecurityException)

The first will be thrown on basic parameter validation errors which usually stems from incorrect use of the library (e.g. masked id too long or short, null reference, etc.). The second are errors thrown from the id masking decryption logic which may be security relevant. It would make sense to at least catch and log them. The IdMaskSecurityException.getReason() can be used to group detailed causes.

Using in your Application #

Various default implementation for value converter exist in the ext.* package. All dependencies for these converters are set to provided which means the caller needs to provide their own. This will prevent unnecessary dependencies for project that use different frameworks.

Jackson JSON Serializer/Deserializer #

The object serialization framework Jackson (most often used with JSON serialization) has a serializer/deserializer feature. A way to use it, is to extend any of the pre-implemented serializers found in IdMaskJackson and provide it with a IdMask instance:

public final class MyIdMaskLongSerializers {
     private MyIdMaskLongSerializers() {
     private IdMask<Long> idMask;
     public static final class Serializer extends IdMaskJackson.LongSerializer {
         public Serializer() {
     public static final class Deserializer extends IdMaskJackson.LongDeserializer {
         public Deserializer() {

and then add the annotations to the id you want to mask:

public class LongIdUser {
     @JsonSerialize(using = MyIdMaskLongSerializers.Serializer.class)
     @JsonDeserialize(using = MyIdMaskLongSerializers.Deserializer.class)
     private final long id;

JAX-RS 2 Parameter Converter #

The Java API for RESTful Web Services , JAX-RS 2 provides the possibility to define so called ParamConverter<T> which can be used to transparently convert between java types and string representations for query, path, header, cookie and header parameter.

The IdMaskParamConverters class contains various default implementations for the most used types. To make it work, you have to define a ParamConverterProvider and return the appropriate converter like so:

public static class MyParamConverterProvider implements ParamConverterProvider {

    private IdMask<Long> idMask;

    public <T> ParamConverter<T> getConverter(Class<T> aClass, Type type, Annotation[] annotations) {

        if (aClass.equals(MaskedLongId.class)) {
            return (ParamConverter<T>) new IdMaskMaskedLongIdParamConverter(idMask);
        } else if (aClass.equals(Long.class)) {
            return (ParamConverter<T>) new IdMaskLongIdParamConverter(idMask);

Note that maybe you don’t want to convert ALL long type values, so there is a simple wrapper class MaskedLongId which can be used for easier type mapping instead of just Long.

Download #

The artifacts are deployed to jcenter and Maven Central.

Maven #

Add dependency to your pom.xml:


Gradle #

Add to your build.gradle module dependencies:

implementation group: 'at.favre.lib', name: 'id-mask', version: '{latest-version}'

Local Jar #

Grab jar from the latest release.

Description #

Why? #

IDMask can be used in an environment, where you want to protect the knowledge of the value of your IDs. Usually a very easy workaround would be to add another column in your database and randomly create UUIDs and use this instead of your e.g. numeric IDs. However sometimes this is not feasible (e.g. having millions of rows) or you cannot change the DB schema. Additionally, IDMask can make IDs appear random, a feature which cannot be satisfied with the above approach.

When to use IDMask #

  • If IDs are used which are easily guessable (i.e. simple sequence) and knowledge of this ID might reveal confidential information
  • If IDs expose row count in a database table, which in turn reveals business intelligence (e.g. how many orders per day, etc.)
  • For creating ad-hoc shareable links which should appear random to the public
  • For creating single-use tokens for various use cases

When not to use IDMask #

  • If it is feasible to create a new column with random UUIDs
  • If maximum performance is required

Performance #

IDMask requires a non-trivial amount of work to encrypt IDs. The 8-byte-schema only needs to encrypt a single AES block (which should be hardware accelerated with most CPUs). The 16-byte schema is more expensive, since it requires encryption of an AES block, one HKDF expand and a HMAC calculation. According to the JMH benchmark, you can expect multiple hundreds’ encryption/decryption per ms. Compared to the performance HashIds, which is faster by a factor of about 1000, IDMask seems extremely slow, but in the grant scheme of things it probably doesn’t make a difference if masking of a single id costs 2µs or 0.002µs - there will be no performance bottleneck either way.

JMH Benchmark #

Here is an benchmark done on a i7-7700k:

Benchmark                                               Mode  Cnt      Score      Error  Units
IdMaskAndHashIdsBenchmark.benchmarkHashIdEncode         avgt    3      2,372 ±    0,282  ns/op
IdMaskAndHashIdsBenchmark.benchmarkHashIdEncodeDecode   avgt    3      3,396 ±    0,965  ns/op
IdMaskAndHashIdsBenchmark.benchmarkIdMask16Byte         avgt    3   7530,858 ±  761,871  ns/op
IdMaskAndHashIdsBenchmark.benchmarkIdMask8Byte          avgt    3   2863,481 ±  183,189  ns/op
IdMaskAndHashIdsBenchmark.benchmarkMaskAndUnmask16Byte  avgt    3  15054,198 ± 2030,344  ns/op
IdMaskAndHashIdsBenchmark.benchmarkMaskAndUnmask8Byte   avgt    3   4707,021 ±  164,998  ns/op

Encryption Schema #

Two slightly different encryption schemes are used to optimize for performance and output size for the specific case. For each of these schemes two variation exist for deterministic and randomized encryption. As reference here are some test-vectors.

8 Byte Encryption Schema #

This schema uses the following cryptographic primitives:

Using the full 16 byte AES block, we create a message containing of the 8 byte id (i.e. the plaintext) and an 8 byte reference value. Then we encrypt it with AES/ECB (since we encrypt only a single block, a block mode using an IV like CBC wouldn’t make a difference):

message_d = ( refValue_1a | id )
maskedId_d = ciphertext_d = AES_ECB( message_d )

When decrypting, we compare the reference value, and if it has changed we discard the id, since either the key is incorrect, or this was a forgery attempt:

AES_ECB( maskedId_d ) = refValue_1b | id 
refValue_1a == refValue_1b
Deterministic #

In the deterministic mode the reference value is just an 8 byte long array of zeros.

Randomized #

In the randomized mode the reference value is a random 8 byte long array. Because the decryption requires knowledge of this value it will be prepended to the cipher text:

ciphertext_r = AES_ECB( refValue_rnd | id )
maskedId_r = refValue_rnd | ciphertext_r
Version Byte #

Both modes have a version byte prepended which will be xor-ed with the first byte of the cipher text for simple obfuscation:

obfuscated_version_byte = version_byte ^ ciphertext[0]

Finally, the message looks like this:

maskeId_msg_d = obfuscated_version_byte | maskedId_d


maskeId_msg_r = obfuscated_version_byte | maskedId_r

for randomized encryption.

Summary #

This schema has the advantage of having forgery protection without the need for a dedicated MAC generation and also keeps the output reasonable small with 16 + 1 byte.

16 Byte Encryption Schema #

This schema uses the following cryptographic primitives:

The basic scheme works as follows:

First create the required keys and nonce:

okm = hkdf.expand(key, entropy, 64);
key_s = okm[0-16];
iv_s = okm[16-32];
mac_key_s = okm[32-64];

key ......... provided secret key
entropy ..... 8 byte value. For randomized-ids it is a random value, otherwise zero bytes 

Then encrypt the id:

ciphertext = AES_CBC( iv_s , id ^ entropy)
mac = HMAC(ciphertext)
maskedId_msg= ciphertext | mac[0-8]

id .......... id to mask (aka plaintext)

optionally if randomized IDs are enabled, also append entropy to the output:

maskedId_msg_r = entropy | maskedId_msg

Finally, append the version byte (see explanation in 8 byte schema). Use either the randomized or deterministic version:

maskeId_msg_r = obfuscated_version_byte | maskedId_msg_r
maskeId_msg_d = obfuscated_version_byte | maskedId_msg

IDMask vs HashIds #

One of the reasons this library was created, was that the author was not happy how HashIds solved the issue of obfuscating/encryption of IDs. These are the main criticism:

Weak, home-brew cryptography #

HashIds encryption schema is basically: Have an alphabet. Shuffle it with Yates Algorithm and a salt provided by the user. Use this simple encoding schema to encode 53 bit integers. There is a well known cryptanalysis and to be fair, the author of HashIds does not directly claim any security - BUT a library called HashId which is used to obfuscate IDs for security purpose which does not claim any actual security does not make sense to me.

Arbitrary limitation inherited rom the original javascript implementation #

The integer values in HashId must be positive and have an upper bound of 53-bit (instead of 64-bit). If IDs are created in a sequence in the DB, this limitation is probably irrelevant, but if you work with random 64-bit values, this might break your code. IDMask does not apply any restriction on Java’s long; the value may be positive as well as negative in the full range of 2^64. Only BigInteger is restricted to 15 byte (or 2^120).

In summary, here is simple comparison table of the main points:

Supported Typeslong, UUID, BigInteger, byte[], LongTuplelong, long[]
Type Limitationslong: none, BigInteger: max 15 byte, byte[]: max 16 byteonly positive and max 2^53
Randomized IDsoptionalno
Output Lengthfixed lengthvariable length
EncryptionAES + HMACencoding + shuffled alphabet
Performance2-7 µs/op0.003 µs/op
Collision possiblenono
EncodingsHex, Base32, Base64, Custom…customizable alphabet
Forgery ProtectionHMAC (8-16 bytes)no

Security Relevant Information #

OWASP Dependency Check #

This project uses the OWASP Dependency-Check which is a utility that identifies project dependencies and checks if there are any known, publicly disclosed, vulnerabilities against a NIST database. The build will fail if any issue is found.

Digital Signatures #

Signed Jar #

The provided JARs in the GitHub release page are signed with my private key:

CN=Patrick Favre-Bulle, OU=Private, O=PF Github Open Source, L=Vienna, ST=Vienna, C=AT
Validity: Thu Sep 07 16:40:57 SGT 2017 to: Fri Feb 10 16:40:57 SGT 2034
SHA1: 06:DE:F2:C5:F7:BC:0C:11:ED:35:E2:0F:B1:9F:78:99:0F:BE:43:C4
SHA256: 2B:65:33:B0:1C:0D:2A:69:4E:2D:53:8F:29:D5:6C:D6:87:AF:06:42:1F:1A:EE:B3:3C:E0:6D:0B:65:A1:AA:88

Use the jarsigner tool (found in your $JAVA_HOME/bin folder) folder to verify.

Signed Commits #

All tags and commits by me are signed with git with my private key:

GPG key ID: 4FDF85343912A3AB
Fingerprint: 2FB392FB05158589B767960C4FDF85343912A3AB

Build #

Jar Sign #

If you want to jar sign you need to provide a file keystore.jks in the root folder with the correct credentials set in environment variables ( OPENSOURCE_PROJECTS_KS_PW and OPENSOURCE_PROJECTS_KEY_PW); alias is set as pfopensource.

If you want to skip jar signing just change the skip configuration in the pom.xml jar sign plugin to true:


Build with Maven #

Use the Maven wrapper to create a jar including all dependencies

mvnw clean install

Checkstyle Config File #

This project uses my common-parent which centralized a lot of the plugin versions as well as providing the checkstyle config rules. Specifically they are maintained in checkstyle-config. Locally the files will be copied after you mvnw install into your target folder and is called target/checkstyle-checker.xml. So if you use a plugin for your IDE, use this file as your local configuration.

Tech-Stack #

Further Reading #

Main Article #

Discussions #

Similar Libraries #

Credits #

License #

Copyright 2019 Patrick Favre-Bulle

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Patrick Favre
Patrick Favre
Software Engineer currently working as architect, backend dev, cloud engineer, IT ops rookie. Cryptography and security are my passions.