Dear folks, once again

On 04.10.18 00:10, Hernâni Marques (p≡p foundation) wrote:

> * * *
> 
> Additionally, a version 1.0.25 -- specifically for Windows -- is being
> tested to replace the buggy 1.0.23 release.
> 
>     https://software.pep.foundation/enigmail/1.0.0/testing/1.0.25/
> 
> If you want to help testing, just reach out: thanks!

If you interested in some background, just check the blog entry (which
was updated three times now):

https://pep.foundation/blog/enigmailpep-current-release-for-windows-is-faulty-solution-in-progress/index.html

We're still working on a solution for Windows, which can be shipped to
Windows users (especially to the the few existing ones which got
equipped with 1.0.23 and have not yet reacted): the effective number
(MAX) of such users can be provided by Patrick anytime soon.

In any case, I think we need a much more general approach to this, and
thus I opened a bug (#909):

https://sourceforge.net/p/enigmail/bugs/909/

It should not be possible that such things happen, not in Enigmail/p≡p
and in no other mode Enigmail supports. Sending $whatever over SMTP
which doesn't match what was indicated to the user shouldn't be possible.

(If you read the updates on the blog entry: Indeed,
 it could also have been that a temporary occur produced an
 OUT_OF_MEMORY error from libetpan ... like it was now produced
 constantly (?) in p≡p distribution 1.0.23 for Windows as libiconv was
 not linked in.)

-- 
p≡p foundation: https://pep.foundation/

Attachment: 0xCB5738652768F7E9.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to