1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
---
title: Multi-Key Database Support
sidebar:
label: Multi-Key Database
---
GpgFrontend introduces **Multi-Key Database Support**, providing users with a
flexible and organized way to manage multiple key databases. This feature is
ideal for users who require separate cryptographic environments for different
projects, organizations, or levels of security.
## Features and Benefits
### Key Features
1. **Multiple Key Databases**: Manage distinct key databases for specific
purposes or contexts.
2. **Flexible Switching**: Easily switch between databases for different
operations without affecting other configurations.
3. **Customizable Management**: Add, edit, reorder, or remove databases as
needed.
### Benefits
- **Improved Security**: Isolate sensitive keys in dedicated databases to
minimize exposure.
- **Enhanced Organization**: Maintain separate databases for better operational
clarity.
- **Streamlined Workflows**: Quickly switch between databases for various
projects or encryption tasks.
## Accessing the Multi-Key Database Feature
### Opening the GnuPG Controller
To manage multiple key databases, follow these steps:
1. **Access the Advanced Menu**
- Click on the **Advanced** menu in the top navigation bar.
- Select **Open GnuPG Controller** from the dropdown options.
2. **Navigate to the Key Database Tab**
- In the **GnuPG Controller** window, switch to the **Key Database** tab.
- Here, you will find a list of all configured key databases.
## Managing Key Databases
The **Key Database** tab allows you to perform the following operations:
### 1. Adding a New Key Database
- Click the **Add New Key Database** button.
- Specify a name and path for the new database. This will create an isolated
environment for new keys.
### 2. Editing and Reordering Key Databases
- Right-click on a database entry to view options like:
- **Move Up/Move Down**: Reorder the database list.
- **Move to Top**: Prioritize a database by moving it to the top. If a database is at the top, it is considered as the Default Key Database.
- **Edit**: Rename or modify the path of an existing database.
- **Remove**: Delete a database from the configuration.
> **Note**: Any changes to the key database settings will require an application
> restart to take effect.
### 3. Switching Between Databases
- Use the **Key Toolbox** dropdown in the main interface to switch between
configured databases.
- Select the desired database, and the corresponding keys will be displayed.
## Use Cases for Multi-Key Databases
1. **Project Isolation**
- Maintain separate databases for different projects to avoid accidental
cross-use of keys.
2. **Organizational Separation**
- Keep departmental or team-specific keys isolated to ensure they are only
accessible to authorized personnel.
3. **Enhanced Security for Sensitive Keys**
- Store high-security keys in a dedicated database, minimizing the risk of
exposure during routine operations.
## Tips for Effective Multi-Key Database Usage
1. **Name Databases Clearly**
- Use descriptive names for each database to make it easier to identify their
purpose.
2. **Regular Backups**
- Backup each database regularly to prevent loss of critical keys. Store
backups in secure, encrypted locations.
3. **Audit Database Usage**
- Periodically review the contents and usage of each database to ensure
proper organization and security.
4. **Isolate Sensitive Operations**
- For highly sensitive keys, consider using a dedicated device or environment
to manage their database.
5. **Avoid Overloading Databases**
- Distribute keys evenly across multiple databases instead of overloading a
single one. This enhances performance and organization.
|
