Skip to main content

How to change expiration date of GPG subkey

How to change expiration date of GPG subkey


Changing the expiration date for a subkey in your GPG (GNU Privacy Guard) keypair can be done using the gpg --edit-key command. Please keep in mind that you'll need to have the private key for the subkey to make changes to its expiration date. 

Steps:

Open a terminal or command prompt.

1) Start the key editing session by running:


gpg --edit-key your_key_id

2) Replace your_key_id with the ID or fingerprint of your keypair.

List your subkeys by typing:


list

This command will display a list of subkeys associated with your keypair.

3) Select the subkey you want to modify by typing:


key 1

Replace 1 with the number that corresponds to the subkey you want to edit, based on the list from the previous step.
First key would be 0, then 1, then 2..

4) Set the expiration date for the subkey. You can do this by using the expire command:


expire

5) You will be prompted to enter a new expiration date for the subkey. You can set the expiration date in a relative format (e.g., "+1y" for one year from today) or an absolute date (e.g., "2024-12-31"). Enter the desired expiration date.

After setting the new expiration date, save your changes by typing:


save

You may be prompted to enter your passphrase to save the changes. This step is essential to confirm your authorization to modify the key.

6) To confirm that the expiration date has been updated, you can list the key's details by running:


list

This will display the updated expiration date for the subkey.







If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...