GpgFrontend Portable is not really portable

[shamsuddin82]

GpgFrontend Portable is not functioning as a truly portable application due to the following issues:

1. Key Database Location:

• The application defaults to saving the key database on the C: drive, which defeats the purpose of portability. It should ideally save all data within its own directory or allow users to specify a custom directory.

2. Configuration Persistence:

• There's no option to change the default key database directory path, and even if a new key database is created, this setting does not persist when the application is run on another machine.

• The configuration for the new key database does not retain when moving the portable version to a different device. This means settings and databases are not carried over, which undermines the utility of having a portable version.

Expected Behavior:

• GpgFrontend should save all necessary data (including keys, configurations, and settings) within its own directory to ensure true portability.

• Alternatively, there should be an option to manually set the storage path for the key database, with this configuration being saved and recognized across different machines when using the portable version.

Current Impact:

• This issue significantly hampers my ability to use the same key database across multiple devices, which is critical for my workflow.

Suggested Solutions:

• Implement a feature to save all data within the application's directory or provide a setting to specify where data should be stored.

• Ensure that all settings, including the database path, are saved in a way that they are recognized by the portable version regardless of the machine it's run on.

Additional Information:

• GpgFrontend Portable Version: 2.1.6

• Operating Systems Tested: Windows 11

Thank you for considering this enhancement to make GpgFrontend truly portable.

Best regards!