Jump to content


Level 1
  • Posts

  • Joined

  • Last visited

About searchwriter

Recent Profile Visitors

16 profile views

searchwriter's Achievements



  1. There is a difference between password protection and password encryption, even though they may sound alike. Password protection is like locking something in a safe-deposit. It means no one can get to the locked content without knowing the right combination. This method is used on separate documents, folders, and other data a computer user may want to protect from other people who might have access to the device. With password encryption, you are creating a password AND encrypting the contents of the file. It is a process during which the content one wishes to keep secret is altered to make it unrecognizable. For example, if it is a text document, letters of each word might be shuffled with additional characters so the words would no longer make any sense. The reverse process is only available if the person who wants to decrypt this data can provide a specific decryption key or a password. In other words, even if the password is removed no one could read the hidden content as it still would need to be decrypted. Of course, it is important to realize you might be unable to retrieve it too if you lose the decryption key, aka, the password.No doubt it is safer to use password encryption since it provides two security layers and password protection has only one. Nevertheless, it usually depends on the data one wishes to protect and the people one wants to keep it away from. For instance, if you want your kids to be unable to open less important documents or other information, you could password protect it with a secure password made up from random characters; something they could never guess. On the other hand, if we are talking about sensitive data the loss of which could do damage to your virtual security, password encryption would be indicated. Since Notebooks are the containers for EN documents and media, one or both methods are necessary at this "container" level. At a minimum, at least one of these methods is necessary at the Notebook level. EN needs to introduce Notebook-level password protection to protect its users data from prying eyes. Its users have demanded it — for years — as a means of safeguarding the documents placed into EN. The use- cases are so abundant that denying this feature is like denying a lock on a door, a file cabinet or s safe. It is a breach of good faith.
  2. > Re: 'm the only person with "general access" to my Evernote account > My sensitive documents are protected using native encryption (pdfs, office documents, ...) In that case, walking away from your workstation while the application is launched would be like leaving the door to a wall safe wide open. Is it difficult or impossible to provide Notebook-level security? I don't get it. Why is this a problem? Please be specific.
  3. re: Wouldn't the creation of password protected notebooks be an admission that the password protection of the overall app is not good enough? Not at all, Mike. We are talking about degrees of granularity. For example, I may want certain financial documents to be kept in a password-secured directory, or Notebook. That does not mean that other notebooks cannot be shared or made public. The inability to password-protect Evernote Notebooks is the most glaring error in the history of Evernote development as a document management, storage, and archival solution.
  4. Hold on a second. The encryption issue seems like a red herring. One can password-protect a directory, a hard drive, or even access to an entire computer via the desktop without encrypting its entire contents. Every time I step away from my office desk for a few minutes, and a screensaver turns on, my computer becomes locked. It is password protected. Its entire contents are not encrypted. I am talking about adding the essential option to add password protection to Evernote Notebooks on demand. I am not requesting the encryption of those notebooks
  5. I find it patently absurd that conversations have gone on in this Forum for years about whether Evernote should add the capability to password-protect the information one chooses to store in it by creating a a password or PIN option. Is Evernote not an archival resource for the collection of all forms of information? The notion that all the data it helps manage should be publicly accessible by anyone who happens to have general access to one's Evernote account, such as an assistant, a spouse, a child or a co-worker, is utterly ridiculous. Legal documents, personal reflections in a diary, medical information (otherwise protected under HIPAA), receipts for purchased items or gifts, confidential business reports or agreements, photos that may be personally or professionally sensitive? Anything one wants to keep away from prying eyes. The list is truly endless. Especially since Evernote acquired Skitch and it is too easy to capture and automatically store a screenshot that could expose all sorts of sensitive data a user may wish to keep private. If Evernote is worried about getting into the password retrieval or reset business, that problem is easily solved. For example, have a password management notebook with a separate login/pw in case you forget the pw for an individual notebook. Since content is synched online, Evernote could also ask for a secondary password to unlock an online password manager. One is not apt to forget 3 or 4 different passwords and there can be other fail-safe retrieval mechanisms or methods. It seems needlessly time-consuming and arcane to encrypt individual notes or sections of a note, and it is unclear whether this even applies to screenshots or other media. So long as Evernote keeps reminding us of the various media formats we can synch with the application (from PDFs to audio and video files, besides text-based information), I find it insulting to be asked to store valuable information in a file cabinet that cannot be locked. It diminishes the value of my digital assets? Can you imagine if file cabinets were sold that way? Please expedite this feature request. It is way too long overdue!
  • Create New...