(Keep in mind the md5() function returns its result as a hex string.)

So for example, the first part of the hex string comes from L_JEK (above).

In UTF-8 mode , " \x{...} " is allowed, where the contents of the braces is a string of hexadecimal digits.

This is the LANMAN hash of the user´s password, encoded as 32 hex digits.

A character is encoded by replacing it with a percent sign followed by its two-digit hexadecimal encoding.

This is the LANMAN hash of the user's password, encoded as 32 hex digits.

Amiga software executable Hunk files running on Amiga classic 68000 machines all started with the hexadecimal number $000003f3, nicknamed the "Magic Cookie.

The hex string is composed of random hexadecimal characters [0-9a-f] and its length is between 32 and 128 characters.

If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string.

An additional valid NAI is the following -- shown here as a hex string, as this document can only contain ASCII characters:

In practice this means that e.g. any address starting with hexadecimal ca (such as ca:ff:ee:12:34:56) can be used as a locally administered address.

Both of them usually take the form of a relatively short hexadecimal string (or multiple if that is the case) so my intuition tells me they use the same principle.

We can create these types of identifiers in Logstash by using the fingerprint filter plugin to generate a UUID or hash and a Ruby filter to create a hex-encoded string representation of the timestamp.