Re: [Enigmail] Best way to move to TB 78

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============2535863800538293001==
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="tU0LbRyhQExRYAG00ifOmwaD86EDWizqh"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tU0LbRyhQExRYAG00ifOmwaD86EDWizqh
Content-Type: multipart/mixed; boundary="DFShtCgEVxEBmmEvCjAHrSP31ocRLVQ8a";
 protected-headers="v1"
From: Patrick Brunschwig <[email protected]>
To: Mark <[email protected]>,
 Enigmail user discussion list <[email protected]>
Message-ID: <[email protected]>
Subject: Re: [Enigmail] Best way to move to TB 78

--DFShtCgEVxEBmmEvCjAHrSP31ocRLVQ8a
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Yes, that's a possible approach. You won't need Enigmail afterwards anymo=
re.

-Patrick

On 25/09/2020 07:44, Mark wrote:
> Thanks.... from my read of it I gather (as I'm starting with a blank
> slate on that other machine) I would need to first install GPG4Win on i=
t
> and then copy my key files to that PC. I would then install TB78 and
> also the "migration edition" of Enigmail to import the keys into TB78's=

> OpenPGP "database"=C2=A0
>=20
> Is that correct?=C2=A0
>=20
> If so, is there a need to leave that version of Enigmail installed afte=
r
> the initial importation of those keys?
>=20
> Thanks Again
>=20
> On 9/24/2020 10:31 PM, Patrick Brunschwig wrote:
>> On 25.09.2020 07:28, Mark wrote:
>>> Forgive me if this is a bit off-topic but I hope someone can give me
>>> some tips.
>>>
>>> Currently I'm using TB 68 with Enigmail and GPG4Win on one system. I
>>> would like to try out TB 78 with it's Open PGP but want to test it on=
 a
>>> separate machine which does not have TB, Enigmail, nor GPG4Win on it =
at
>>> all.
>>>
>>> How would be the best way to accomplish this so that it imports my
>>> private and public keys into it?=C2=A0 The mail itself can be re-down=
loaded
>>> off the servers so not real worried about that. I'm just not sure how=

>>> best to handle the PGP keys.
>> Read the following article:
>> https://sourceforge.net/p/enigmail/forum/announce/thread/7dcd29e5f9/
>>
>> -Patrick
>>
>>



--DFShtCgEVxEBmmEvCjAHrSP31ocRLVQ8a--

--tU0LbRyhQExRYAG00ifOmwaD86EDWizqh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

wsFzBAEBCAAGBQJfbgvQACEJENsRh7ndX2k7FiEET5+J9VBawdGiYGMc2xGH
ud1faTsYHw/+NHpiZOGU2VBzp4m9Da4R0DwkxzTa/0w6Er755fFyMQfvUz3W
zzpkPH4ODMcuvdO9sn4vmmjcSzdKohSOJ7yq0pQkJAr3A8FCoTvP0fNY+4Wv
CoOFF6Fa9MrH+9w0LnR3WoE082uMrzv+/f/cF5u3mOf3/B6W2nO1BphQj/MK
zJn/9v25rspQ2v2bec286PkI/VQnpiNGNNpTvN6F4KuoHuCquI6MmbH6s3i2
GqIEJ50dRtD/4G6pc5MAGfCpsPjSyrum+s8z9FZoBn1+P9oQ1ei//tY/vrgD
YMsTyku371GHqPkxFPvAoW/lde0v0q+vx7tOTTnCUha1D+rqfZ5McfW6fEwl
hsWQ0SWmoaSynMvUubq7oI97Lxn3s2ifGXLGaXaGCfV2lU05h0dKoCOZfjFa
RINFrpR7bN/OcYAOrTW8Xm24VNKk0JjYoSzYeKgPx29IMswjzJczFC8V6FSl
SEZ8n1OhU1xe8g3oI3TVq1HknJVPWueyFsmx4+iB//+HRa7gLVOdfXQc63JF
CNsKqQr97KVaYcLoG/tBjcrREVZ5+8lx6MXjbiVzVcc65J58qcV9mu5PpbJ8
tBS9Q/ZDdHTxiYTOudQmmJNfibtrW6q0NjSJXYWH46BTm2nc605gYkO/pf83
udVcU398ZnDCRax+3ECecJKZ4/RIYq98wQ0=
=ETTd
-----END PGP SIGNATURE-----

--tU0LbRyhQExRYAG00ifOmwaD86EDWizqh--


--===============2535863800538293001==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
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

--===============2535863800538293001==--