How should I manage my passwords?
Nikagi (formerly 2Keys) is a client-side password manager which wants to answer to this everyday question.
Its purpose is to allow people to easily use a different password for each service, without having to remember them, store them, or worse: write them.
Nikagi takes some input data:
- the password length
- charsets to use (lowercases, uppercases, digits, symbols)
- a public key
- a private key
Then it uses all these data to generate a password, and here come the two main interest of Nikagi:
- the same input data generates the same password
- everything is generated on the fly, nothing is stored
As long as you understand how Nikagi works, your password management policy is up to you!
The most common way to use it would be to use the service name as the public key, and a unique private key. It's worth mentioning this 1Password-like policy requires your strong private key to never, ever be revealed to anyone.
Whatever the way you're using Nikagi, just remember that your private key must never be guessable from your public key. This would make the whole process of having various passwords useless.
Use git clone, or download and extract this whole repository on your own server.
Access to your brand new password manager, and the installation process will launch itself. It will ask you to create an admin account (used to manage presets), and to define the default values used by Nikagi.
You're now ready to use Nikagi!
Some online services require password with a limited length, or without any symbols. Nikagi allows you to take these limitations in account, without having to remember it, using presets.
To create a new preset, access to your administration page through the bottom left buttons.
Each preset offers you a shortcut. For example, if you've set a preset for the public key github, you'll be able to use the following url: http://host.io/Nikagi/github.
This url will load your settings, leaving you with a single field to fill: your private key.
You've defined the default values at the installation, but you may want to change them at a time.
Simply clear the config/config.ini file and the installation process will be launched again.
The config/ directory does not contain anything critical, but it's still not a good idea to leave it public. You should protect this folder, with an .htaccess containing Deny from all for example if you're using Apache2.
- (~) Remove config folder for better deploys
- (+) Add entry point for mobile users
- (+) Add robots.txt
- (~) Project renamed from 2keys to Nikagi (trademark request)
- (~) Logo changed to fit new name
- (+) Order presets
- (~) Fix issue when Nikagi is not is a subfolder
- (+) An administration interface has been added
- (+) Nikagi has now an installation process
- (-) Htaccess use has been dropped
- (~) A different font is now used to differenciate 1, i, I, l, L, etc.
- (~) Logo has been changed
- (~) Design has been slightly modified
- (+) Initial release
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
- Contact : @zessx