Skip to main content

Share a private key without using passwords

If you follow security best practices, you are not re-using the same password for multiple purposes. As a consequence you end up with a long list of passwords that you need to secure and manage. Although the use of a password vault certainly improved the experience, I still try to avoid the usage of passwords as much as possible.

Today I want to share a ā€˜trick’ I discovered that allows you to share(export/import) a PFX file without using passwords.

No clue what a pfx is? Let me explain that first…

A PFX file, also known as a PKCS#12 file, is a binary format used to store certificates and their associated private keys. It combines 2 parts:

  1. A certificate part: A certificate is a digital document that contains information about an entity (such as a person, organization, or server). It is used for authentication, encryption, and secure communication. Certificates are issued by a Certificate Authority (CA).
  2. A private key part: The private key is a cryptographic key that corresponds to the public key in the certificate. It is kept secret and is used for decrypting data encrypted with the public key, as well as for signing and authenticating messages.

A PFX file is typically password-protected to ensure security.They are commonly used for importing/exporting certificates between systems, such as web servers, application servers, and client devices.

Of course this means another password we need to add to our list!

The good news is that on a domain controlled Windows machine, you can use a passwordless approach.

$a = Get-ChildItem -Path cert:\localMachine\my

Export-PfxCertificate -Cert $a[1] -FilePath C:\myexport.pfx -ProtectTo "domain\username"

By using the –ProtectTo argument when exporting the certificate, I can import it using the specified account without requiring a password.

Set-Location -Path Cert:\LocalMachine\My

Import-PfxCertificate -FilePath C:\mypfx.pfx

More information

Export-PfxCertificate (pki) | Microsoft Learn

Import-PfxCertificate (pki) | Microsoft Learn

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...