Activity for Hernani Marques
-
Hernani Marques posted a comment on discussion Enigmail Support
Heyo Bob Is there any reason why you can't update your Windows system to SP level 2? I think, with this SP Convenience Rollup alone, not all dependencies are met. :/ We wrote here, minimum version supported for Win 7 32-bit, is (proper) SP2: https://pep.foundation/blog/enigmailpep-current-update-1024-fixes-bug-under-windows/index.html However, I was not aware such pop-ups would show up. That might be something which happens only with the Convenience Rollup: I will try to reproduce that. In other...
-
Dear Bob: Which Windows version (you say "Windows 87") are you using exactly with which service pack? For Windows 7 32-bit you need at least Service Pack 2 to be installed.
-
Addition: If it lands in nightly now, I will also make sure the testing is done now. -> Blame me. :)
-
IMHO a risk by adding that is virtually non-existent: if it's still possible, I would opt for adding it right ahead. In terms of formats, it only affects pEp<->pEp communications.
-
That's actually correct: if installed through the the add-ons menu of TB it gets active. Please try again with the new 1.0.24 update. => Ticket can be closed.
-
Since yesterday an update 1.0.24 exists for all platforms, including Windows.
-
Hello Thorsten: that's a known issue which was now fixed with version 1.0.24 of pEp. Check if ~./thunderbird/$yourProfile/pepmda/version.json has package_version 1.0.24. If not (lower number), just delete the folder pepmda and start again.
-
Avoid Windows users from using Enigmail/p≡p in version 1.0.23
-
Avoid Windows users from using Enigmail/p≡p in version 1.0.23
-
I also opened bug 909: this should (somehow) be fixed altogether. https://sourceforge.net/p/enigmail/bugs/909/ For the concrete situation on the Enigmail/p≡p mode on Wndows, just check the blog post at pep.foundation: it was updated three times already.
-
Always avoid Enigmail to send out messages it indicates as protected to the user without any protection at all
-
Title was completely bogus before: sorry.
-
Always avoid Enigmail to send out messages it indicates as protected to the user without any protection at all
-
Always avoid Enigmail to send out messages it indicates as protected to the user in the clear text
-
Always avoid Enigmail to send out messages it indicates as protected to the user in the clear text
-
Always avoid Enigmail to send out messages it indicates as encrypted/secure to the user
-
For an udpate on this, please check: https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2018-October/005199.html In short: new users again get version 1.0.8 of the p≡p distribution. Existing ones can downgrade or stick with the classic mode until an update to (most probably) 1.0.25 happens.
-
For an udpate on this, please check this: https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2018-October/005199.html In short: new users again get version 1.0.8 of the p≡p distribution. Existing ones can downgrade or stick with the classic mode until an update to (most probably) 1.0.25 happens.
-
Dear users of Enigmail/p≡p for WIndows We have an issue with our latest update of the p≡p distribution in version 1.0.23, available since September 26. It only affects Windows. Sorry for that. But: we are on it! For more about the concrete symptoms you will observe and a workaround, see here: https://pep.foundation/blog/enigmailpep-current-release-for-windows-is-faulty-solution-in-progress/index.html
-
I corrected that: sorry for having it wrong.
-
Concerning header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tampering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concerning header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tampering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concerning header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tempering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concernig header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tempering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concernig header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tempering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concernig header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tempering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Concernig header protection, the fundamental idea (at least with pEp message format 2, which is used by default) is to enclose the inner message like a forwarded message, which means integrity and confidentiality of the entire message can be ensured. If you include sender and recipient fields, you can also detect differences (e.g., tempering) to the envelope outside -- that's to be seen in context with our trust rating system, which includes states and UI mappings for manipulated messages. By default,...
-
Like with instant messaging (take Signal, Threema, WhatsApp etc.) you cannot expect regular and novice users to even know anything about keys: that's the concept here. Despite that, already existing unexpired keys with sufficient length (>= RSA-2048) which you ultimataley trust yourself are expected to be used by pEp. If that doesn't happen (yet) that's a bug. This default behaviour is also mentioned in the drafts. However, by Patrick's decision already existing Enigmail users don't get pEp activated...
-
If you try to use Enigmail 2.0 with a new profile Enigmail/p≡p gets activiated by default. However, this needs GnuPG 2.0.30 or >= 2.1.17 to function. On macOS and Windows GnuPG gets installed if not already available. On GNU/Linux-based systems we rely on GnuPG shipped by the system, as such distributions are (always) shipped with GnuPG pre-installed. Existing Ubuntu(-based) systems ship with a too old version of GnuPG, such that it doesn't run yet without manual upgrade to a newer version. This...
-
This might be a lang env issue: https://twitter.com/dc7ia/status/978413978161475586
-
The p≡p mode is also not enforced (e.g., even no pepmda/ folder is unpacked) if in the configuration editor the junior mode is manually set to 2. Also a restart doesn't help.
-
Force-enable p≡p mode not (always) possible
-
Force-enable p≡p mode not (always) possible
-
Force p≡p mode not (always) possible
-
In cases with very large attachments it's even necessary to forward the message to actually see the mail's contents and attachment(s). Can this be fixed for all modes of Enigmail?
-
This happens for me in production (classic) mode, outside p≡p mode. Is that intended?
-
Show Privacy Status with "Cannot Decrypt" (gray) if no seckey avail
-
Show Privacy Status with "Cannot Decrypt" (gray) if no seckey avail
-
PGP/MIME messages with (larger) attachments often fail to load by its own
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Home
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
-
Todo List for pEp
1
