Security

GitNap has been developed with a focus on security, aimed at protecting your data and confidential information. The following measures have been implemented:

• Absence of hardcoding credentials: The source code of GitNap contains no access credentials, such as authentication tokens or passwords. This ensures that sensitive information is not inadvertently exposed in the event of a code leak.
• Utilization of gnome-keyring: Currently, GitNap employs the secret-tool from gnome-keyring to securely store authentication tokens. This tool provides an interface for managing passwords and other confidential information within the operating system, ensuring that credentials are preserved in an encrypted format.
• Plans for integration with other password vaults: We are working on integrations with other popular password management tools, such as pass and keyring, to provide users with enhanced flexibility and compatibility.

Best security practices:

Users are advised to adhere to the following practices to ensure the utmost security when utilizing GitNap:

• Keep your operating system and tools updated: Security updates rectify vulnerabilities that could be exploited by attackers.
• Use strong and unique passwords: Create complex and exclusive passwords for each service, eschewing the reuse of passwords.
• Properly configure your password manager: Ensure that your password manager is set up with a strong master password and that encryption keys are securely stored.
• Limit access permissions: Grant only the minimal necessary permissions for GitNap to perform its functions.