techdoc

commit messages

created on

October 10, 2026

I’ve had discussions with teammates about Git commit messages once in a while and there are discussions about it on the web. This article summarizes the general approach, and when and how to deviate from it (if you feel like doing so). ...

display filter

created on

October 10, 2026

a list of display filters expressions for wireshark...

password hashes

created on

September 15, 2026

the structure of password hashes A hash has three or four components delimited by special characters like $ : ...

HPKP

created on

August 28, 2026

HPKP (HTTP Public Key Pinning) is an obsolete security mechanism defined in RFC 7469. HPKP worked with the TOFU principle (Trust on First Use). The first time a browser visited a site, it received a Public-Key-Pins HTTP header containing SHA-256 hashes of SPKI (Subject Public Key Info). On later visits, the browser computed the SPKI fingerprints of the presented certificate chain. At least one of the presented public key hashes had to match the stored pin set. If it failed, the browser treated the error as non-recoverable and blocked the connection. Implementations required at least one active pin and one backup pin (not currently in use) to prevent lockouts during certificate renewals. ...

commit messages

created on

October 10, 2026

I’ve had discussions with teammates about Git commit messages once in a while and there are discussions about it on the web. This article summarizes the general approach, and when and how to deviate from it (if you feel like doing so). ...

display filter

created on

October 10, 2026

a list of display filters expressions for wireshark...

password hashes

created on

September 15, 2026

the structure of password hashes A hash has three or four components delimited by special characters like $ : ...

HPKP

created on

August 28, 2026

HPKP (HTTP Public Key Pinning) is an obsolete security mechanism defined in RFC 7469. HPKP worked with the TOFU principle (Trust on First Use). The first time a browser visited a site, it received a Public-Key-Pins HTTP header containing SHA-256 hashes of SPKI (Subject Public Key Info). On later visits, the browser computed the SPKI fingerprints of the presented certificate chain. At least one of the presented public key hashes had to match the stored pin set. If it failed, the browser treated the error as non-recoverable and blocked the connection. Implementations required at least one active pin and one backup pin (not currently in use) to prevent lockouts during certificate renewals. ...