This way the deltas could also be made smaller by splitting the main wallet into several smaller blocks, but that's for another discussion. So I'm not suggesting to create anything *outside* the wallet, but rather expand the concept of the wallet to a file tree instead of only a file. The "wallet" could be a bundle, like a directory composed by many files, entirely managed by the Enpass application. Now, I've never suggested that the separate files reside on arbitrary locations. Hi thing that all kinds of files will be attachable. I don't to say more specific things, because I think it is clear, what I want to say. On developer side it's easier to have all files in the wallet, because you only have to verfiy if the wallet is valid and not the whole attachments files. Some people don't trust the cloud at all and manually copy the wallet to the different clients Copying a single file is easier. Next if the program use absolute paths, then you will get an error after copying it somewhere else.įor syncing: As I have already written it in the post above, it is possible to sync only the difference of the file and not the whole file! I'm not sure if Enpass is using this function, but I think so.Īt the end your suggestion is more work for all, the developer to implement a function, which create encrypted attachments is a external file (I mean with external outside of the wallet) and for us customer, because we must be carefully, when we copy the wallet. First if you copy the wallet to a different location, you must verify that you copied all attachments. That would speed up syncing as the database size grows.Īs you can read above, it already was decided to attach any kind of file and not only images. There are many things that don't fit in regular fields: SSH keys, authentication certs and keys, other secrets.Īnyone from Enpass team care to give their view or an update?Īs a suggestion, attached files (chiefly binary files such as images) could go on a separate file from the main wallet perhaps even one encrypted file for each attachment, or for all attachments of any particular item. These files are used like passwords and for this reason I also want to store it in the same location as all my other passwords. It's fine that you only store passwords in Enpass, but in my case some files(cert.) are used to authenticate me on some services. So if you don't attach documents to Enpass, the DB of Enpass will stay at the same size as it is now. The last point (I don't want to attack you) if this feature is implemented, nobody forces you to use it. Next today we have highspeed Internet and so the sync takes some seconds. I don't know, how the development-team have implemented the sync function, but nowadays it's possible to sync only the changes between two files. As I have written previously, for bigger data we can use encrypted folder, but license-files or key-files have in opinion the same priority as passwords.Īnother point is the sync with the cloud. This files are very small and I don't want to store dem separate in a encrypted folder. But some software are providing a license-file instead of a serial number. When you buy a software, you normally get a serial-number (which you can already save it in Enpass). If we need save image then we can save into cloud or zip with protected password and save that password into Enpass. so I like small size for upload/download from/to cloud. With my opinion then Enpass should not support this feature, they should create new product. So thank you guys for providing this nice manager. ATM I have stored them in Keepass.Įnpass is already a powerful password manager and I like it. I would like to store the private keys of PGP, SSH to give you an example in Enpass. So the DB will not increas significant. If you have to store bigger data or all data you have, then encrypt your hard drive and only store the private key in Enpass. Next I think, that the important documents, which you want to save in Enpass are small (In my case each file is some kilobytes big). Of course it will increase it, but nowadays we cane compress the data before saving it. There was already created a feature request for attachments (see below)Ĭoming back to your sentence of the DB size. Yes it would be helpfull to attach documents or files of any type. I guess this would significantly increase the size of the database file. A good idea I think would be to create a new category File, with sub categories image, document, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |