Unable to encrypt Jrnl

[nilact]

I installed pycrypto package on windows 10 machine after lot of struggle.

While trying to encrypt jrnl, it first asks password which I'm not aware of and then I get an error "Pycrypto is not installed"

.jrnl_config:

{ "journals": { "default": "C:\\Users\\nilact/journal.txt" }, "editor": "", "encrypt": false, "default_hour": 9, "default_minute": 0, "timeformat": "%Y-%m-%d %H:%M", "tagsymbols": "@", "highlight": true, "linewrap": 79 }

Suggestion: If pycrypto is not being maintained and pycryptodom is its replacement, then documentation should indicate how to do it. After lot of struggle installing pycrypto on Win 10 machine, I found closed issue here.

Note: I'm new to python, I installed it and took trouble to install package pycrypto as it was dependency.

[arisAlexis]

have the same problem Windows 10, Installation of PyCrypto worked but gettting the same error.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[wren]

This module has been replaced in v2.0. Is this issue still relevant?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[micahellison]

Confirmed that encryption works fine in jrnl v2.2 on Windows 10 right out of the box.

C:\Users\micah>jrnl
[Compose Entry; on a blank line, press Ctrl+Z and then Enter to finish writing]

Testing
^Z
Enter password for new journal:
Enter password again:
Do you want to store the password in your keychain? [Y/n] n
Encrypted journal 'default' created at C:\Users\micah\.local\share\jrnl\journal.txt
[Entry added to default journal]

C:\Users\micah>jrnl -n 1
Password:
2020-03-07 14:12 Testing

This is working in our automated tests as well.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. You can link back here from your new issue to continue the conversation.