Home → VoodooPad →

Encrypt page issue?

• Edit

Darin

01 Sep, 2018 12:20 AM

Encrypt Page… only works with Rich Text Format pages. In other words, I cannot encrypt either plain text or markdown pages—the menu option is greyed out.

Am I the only person seeing this issue?
Has it always been restricted to Rich Text Format pages?
Is there a reason that only RTF pages can be encrypted?

Thanks,
Darin

1. 1 Posted by Sarah on 04 Sep, 2018 01:03 PM

   

   Hi Darin,

   Thanks for posting. This is a known issue that has been around for a while. I apologize for the trouble. We will take look when we get a chance, and I'll post here if I have any updates for you. If you need help with anything else, don't hesitate to ask!

   • Edit

2. 2 Posted by jetsgaudin on 15 Oct, 2018 11:47 AM

   

   I am using VoodooPad 5.2.2 under Mac OS High Sierra version 10.13.6.
   My encrypted data has become less secure under 5.2.2. At first under 5.2.2, the programme asked for access to my keychain instead of asking directly for the keyword. Now it opens the page but returns a message “The page ‘—— vdp' is encrypted”. This can easily be overcome by using the command “Backlinks”. But that means that the data is open to everyone. Any ideas on how to fix this?
   A second problem is that VoodooPad takes ages (3-4 minutes) to load. Is this normal?
   It’s still a wonderful programme and thanks to Primate Labs more open to its users.

   • Edit

3. 3 Posted by Sarah on 16 Oct, 2018 03:40 PM

   

   Hi Stuart,

   Thanks for letting us know about this. I'll try my best to help out. When the page opens and returns the message that says it is encrypted, have you already entered the password? And could you clarify what you do when you use Backlinks, for the purpose of recreating this issue on my end?

   It isn't normal for VoodooPad to take 3-4 minutes to load. Which Mac Model are you currently using?

   • Edit

4. 4 Posted by jetsgaudin on 17 Oct, 2018 10:30 AM

   

   Dear Sarah,

   Thank you for your interest. Yes I have already entered the password. But it is not the password I set for the page. Instead (since 5.2.2) it asks for the password to my keychain (for the page).
   For the Backlinks, once the page opens and returns the message that says it is encrypted, I press the Backlinks button and choose the first page of the encrypted document. However for the purpose of this email, I went through the procedure outlined above and although the password to the keychain was accepted (no “head shake”) the page that says it is encrypted did not appear. So I don’t know what to say!!
   I am using a mac pro mid 2012.
   I would add that I share the comment of one of the users who said that the programme “freezes” frequently. It is getting to the stage where I have to "Force close” and restart VoodooPad whenever I want to use it.

   Hope you can make it stable again.

   Best regards

   Stuart

   • Edit

5. 5 Posted by Sarah on 17 Oct, 2018 03:49 PM

   

   Thanks for clarifying. If it is prompting the password for Keychain, it is a possibility that at some point your password for that particular page was added to the keychain (most likely when it was first encrypted). If you open up Keychain Access, are you able to find an entry for that document? For example, it could show up as "document.vpdoc:pagename".

   I will let the team know about these issues. Is there anything in particular that you are doing when VoodooPad freezes? Or does it happen seemingly out of nowhere?

   • Edit

6. 6 Posted by jetsgaudin on 19 Oct, 2018 07:48 AM

   

   Dear Sarah,

   Thank you for your e-mail. The password for that page was, as you said, added to the keychain. I found it under keychain/session “my VoudouPad document name” vpdoc: motclé VDP.
   No particular sign when VoodooPad freezes. It often happens when I get back to VoodooPad after having used other programmes or having closed and re-opened the computer (without turning off the computer). Ofter I can still write on a page but the programme will not accept to change pages when I click a link.

   Thank you again,

   Stuart

   • Edit