| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
| |
- reorganized key toolbox content for better flow
- added explanation of key types and usage codes
- included details about key groups
- expanded usage code descriptions with examples
- removed standalone large text file support subsection
|
| |
|
|
|
|
|
| |
- restructured content to focus on workspace organization
- added detailed descriptions for file panel, text editor, and mail editor
- updated operations bar section with current functionality
- improved overall clarity and flow of the documentation
|
| |
|
|
|
|
| |
- removed nested bullet points for clearer step-by-step instructions
- consolidated method descriptions into single-level bullet points
- kept image references in place without changes
|
| |
|
|
|
|
|
| |
- add new section explaining quick file operations via direct selection
- include two screenshots demonstrating the file selection process
- reorganize existing content under new heading
- improve flow between sections
|
| |
|
|
|
|
|
| |
- introduce key group concept and characteristics
- explain how to create and manage key groups
- describe typical use cases and special behaviors
- note limitations and independence from GnuPG keygroups
|
| |
|
|
|
|
|
| |
- fix markdown formatting inconsistencies
- add new section about common subkey misconceptions
- reorganize tips and notes into clearer sections
- update image references to be consistent
|
| |
|
|
|
|
|
| |
- explain what public key certificates contain
- describe importance of certificates for identity binding and trust
- provide example of certificate usage
- improve formatting and readability throughout guide
|
| |
|
|
|
| |
- change h3 headings to h4 for better document hierarchy
- maintain consistent heading levels for user pin and admin pin sections
|
| |
|
|
|
|
|
|
|
| |
- explain what an openpgp smart card is and its advantages
- clarify difference between user pin and admin pin
- define key stubs and their purpose
- answer common questions about key storage and fetching
- add section on handling wrong pin attempts and key synchronization
- explain multi-credential support in devices like yubikey
|
| |
|
|
|
|
|
|
| |
- reformat numbered steps for better readability
- add missing newlines between sections
- fix indentation in settings instructions
- add bullet points for clarity in ASCII/binary format section
- improve folder encryption/decryption steps formatting
|
| |
|
|
|
|
| |
- remove bold formatting from section headings
- ensure consistent heading levels
- maintain proper markdown syntax for subheadings
|
| |
|
|
|
|
| |
- clarify use of developer id certificates and notarization
- add details about hardened runtime protections
- improve explanation of system-level security enforcement
|
| |
|
|
|
|
| |
- change "SecureLevel 0 (Default/Low)" to "SecureLevel 0 (Default)"
- change "SecureLevel 1 (Medium)" to "SecureLevel 1 (Standard)"
- change "SecureLevel 2 (High)" to "SecureLevel 2 (Enhanced)"
|
| | |
|
| |
|
|
|
|
|
| |
- describe signature verification for integrated modules
- explain handling of user-defined/third-party modules
- add security note about custom module directory
- include tip for sensitive environments
|
| |
|
|
|
|
|
| |
- add macOS screenshot example
- wrap note in tip component
- clarify platform differences in interface appearance
- remove old generic interface screenshot
|
| |
|
|
|
|
|
|
| |
- add new section about updating gpgfrontend
- replace beta version info with nightly builds explanation
- add sections for importing/exporting keys, file operations, compatibility
- include details about languages, password handling, smart cards
- add privacy policy and feature request info
|
| |
|
|
|
|
|
|
| |
- add comprehensive guide for OpenPGP smart card management
- describe key sections and features of smart card controller
- explain operations panel functionality
- include typical usage scenarios and security notes
- add screenshot for visual reference
|
| |
|
|
|
|
|
|
| |
- add steps to enable symmetric encryption feature in settings
- clarify symmetric encryption process with new dedicated button
- update current documentation version to v2.1.9
- remove summary table from symmetric encryption guide
- add OpenPGP link in overview glance
|
| |
|
|
|
|
|
|
| |
- clarify self-check mechanism for different platforms
- add details about platform-specific binary signing
- improve security notes and recommendations
- update code signing information for all platforms
- enhance build verification documentation
|
| |
|
|
|
|
|
|
| |
- add order to sidebar labels
- fix markdown formatting and indentation
- improve readability of bullet points
- fix tip section formatting
- standardize code block formatting
|
| |
|
|
|
|
|
| |
- describe the application self-check feature
- explain how it works and how to enable it
- list build requirements and platform compatibility
- include a security note about the feature
|
| |
|
|
|
|
|
| |
- document application data storage approach and security considerations
- explain data object structure and encryption methods
- describe file layout and access patterns
- include security considerations and key rotation support
|
| |
|
|
|
|
|
|
| |
- document automatic key generation and management
- explain encryption algorithms and security levels
- describe key storage and pin protection
- cover key rotation and data migration
- include troubleshooting and best practices
|
| |
|
|
|
|
|
|
| |
- document securelevel configuration options (0-2)
- explain openssl secure memory features
- describe gpgfrontend's memory security commitment
- include system requirements for securelevel 2
- add caution and tip notes for users
|
| |
|
|
|
|
|
| |
- describe portable mode features and benefits
- explain how to enable portable mode via ENV.ini
- include notes about first launch and platform support
- provide details on disabling portable mode
|
| |
|
|
|
|
|
|
| |
- rename file from sync-all-public-keys.md to sync-public-keys.md
- add order 4 to sidebar
- fix indentation in numbered list
- improve formatting and consistency
- ensure proper line endings
|
| |
|
|
|
|
|
|
| |
- add order to sidebar configuration
- improve formatting and clarity of instructions
- add relative path support details
- enhance use cases and best practices sections
- fix minor typos and improve consistency
|
| |
|
|
|
|
|
|
|
|
| |
- add security enhancements section for v2.1.9
- update encryption algorithm details from AES-256-ECB to AES-256-GCM
- document new key generation methods and naming convention
- explain new PIN protection mechanism
- add compatibility notice for v2.1.9+ packages
- update transfer instructions to include key file
- improve security best practices section
|
| |
|
|
|
|
|
|
| |
- restructure content with clear sections
- add note about QtAES removal in v2.1.9
- update OpenSSL and mingw-w64 links
- improve formatting and organization
- clarify icon attribution section
|
| |
|
|
|
|
|
|
|
| |
- change section headings from ### to ## for consistency
- remove third-party library assurance section
- simplify binary verification instructions
- consolidate build info and public key sections
- update key fingerprint and public key block
- make language more concise and direct
|
| |
|
|
|
|
|
|
| |
- enhance description with 'portable' keyword
- rewrite hero tagline for better clarity and appeal
- update feature cards with more concise and compelling copy
- emphasize portability and multi-key management
- refine open source messaging
|
| |
|
|
|
|
|
| |
- rewrite introduction with key features list
- restructure mission and origins section
- simplify privacy and contribution statements
- update formatting and organization of content
|
| |
|
|
|
|
|
| |
- add full legal name and preferred name
- include headquarters location
- add note about name usage for verification
- improve formatting of email details
|
| |
|
|
|
|
|
|
| |
Updates the Starlight dependency to version v0.34.2 and theme-nova to v0.6.1.
Applies the starlight-theme-nova plugin for enhanced theming capabilities.
Refactors the main page description and links to improve clarity and provide relevant information.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
