Hello Christopher,
Saturday, March 28, 2020, 11:33:06 AM, you wrote:
> I've never used it, nor do I know if The Bat! can use this mode let
> alone it's compatibility with other email clients.
Possible with clients that support easy(ish) passing of key-data
handling to pinentry.
Also, I should
On 2020-03-27 at 5:33 PM, Andrew Savchenko wrote:
> It is *technically* possible to use GPG in symmetric mode for messaging
> purposes.
>
> ```
> $ echo "Hello World" > cleartext
> $ gpg -o encrypted -c cleartext
> ```
>
> ...Then one needs to wrap the routine above into something palatable
Hello Christopher,
Thank you for the well-constructed and informative message, I just
wanted to add one small point to the below:
>> What I would like to be able to do is send password-protected
>> messages that can only be opened by the receiving party who has the
>> password. Is that what this
On 2020-03-23 at 12:55:15 PM, Achdut18 wrote:
Before I go on and answer your more detailed questions, I urge you to
think about the threat model that you and your colleague have.
As with all things in security--whether online or offline--you will
want to figure out which threats you care about
HI,
Last summer I posted a query about how to encrypt messages. The response left
me more confused than when I started, so, I decided to carry on, as usual.
M> On Tuesday 4 June 2019 at 3:08:56 AM, in
M> , Avram Sacks wrote:-
>> If I went to send an encrypted message to a client. What
Hi
On Tuesday 4 June 2019 at 3:08:56 AM, in
, Avram Sacks wrote:-
> What is S/MIME?
> What is OpenPGP?
They are standards for signing and encrypting.
In both cases you generate a key or certificate. Sometimes called a
key pair because it actually consists of a public part you share and a
Please explain how this works.
What is S/MIME?
What is OpenPGP?
Currently the bar reads "S/MIME + OpenPGP (auto)"
What is happening automatically?
There are also a picture of a locak and a green "Sign when complete" button to
the right of the S/MIME + Open PGP (auto) bar. What do those
Hi
On Wednesday 22 May 2019 at 6:59:30 AM, in
, Avram Sacks wrote:-
> For what it is worth, the bar at the bottom of the
> message window,
> on the far right reads "S/MIME + OpenPGP (auto)."
> Does this have
> anything to do with what I want to do?
Yes.
--
Best regards
MFPA
HI, all. It's been a while since I had a question for this forum
I will, occasionally, have a client who is concerned about the security of
messages.Short of sending password-protected pdf files, is there a way to
send an e-mail to someone who does not use The Bat, in such a way, that the
It seems that in order for me to encrypt the messages I send
to someone, with PGP, I need his/her public key, is this true ?
And in order for that someone to read the encrypted message I
sent to him/her, that user must have *my* public key right ?
--
If Bill Gates had a dime for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Silviu
On 12 May 2001 at 09:56:22 +0300 (which was 07:56 where I live) Silviu
Cojocaru rearranged electrons to get
It seems that in order for me to encrypt the messages I send to someone,
with PGP, I need his/her public key, is this true ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Silviu Cojocaru !
On Sat, 12 May 2001 09:56:22 +0300 GMT your local time,
which was 12.05.2001, 08:56 (GMT+0200) where I live, you wrote:
It seems that in order for me to encrypt the messages I send
to someone, with PGP, I need his/her
Hello Gerd,
On Sat, 12 May 2001 09:50:25 +0200 GMT (12/05/2001, 15:50 +0800 GMT),
Gerd Ewald wrote:
And in order for that someone to read the encrypted message I
sent to him/her, that user must have *my* public key right ?
GE No, the recipients needs his/her secret key to decrypt the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Thomas !
On Sat, 12 May 2001 16:38:41 +0800 GMT your local time,
which was 12.05.2001, 10:38 (GMT+0200) where I live, you wrote:
And in order for that someone to read the encrypted message I
sent to him/her, that user must have *my*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello David!
On Saturday, May 12, 2001 at 9:18:02 AM you wrote:
No. You can encrypt the message to as many keys as you like the minimum is
one i.e. the recipient. However this is a bit silly as once encrypted you
Yes
--
__
Archives : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
You are subscribed as : archive@jab.org
Hello Gerd,
On Sat, 12 May 2001 11:03:49 +0200 GMT (12/05/2001, 17:03 +0800 GMT),
Gerd Ewald wrote:
GE Even if B doews not have the senders public key, in our example pKa,
GE she would be able to decrypt the message. She wouldn't be able to
GE verify the signature but she could reveal the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 12 May 2001 18:42:34 +0800, Thomas contributed this to our
collective wisdom:
GE Even if B doews not have the senders public key, in our example pKa,
GE she would be able to decrypt the message. She wouldn't be able to
GE verify the
Hello Allie,
On Sat, 12 May 2001 06:25:31 -0500 GMT (12/05/2001, 19:25 +0800 GMT),
A Curtis Martin wrote:
T Would she? I think you do need the sender's public key to drecypt a
T message. Maybe I'm wrong about this?
ACM AFAIK, you only need the senders public key to verify their signatures.
ACM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 11, 2001, at 11:56:22 PM, Silviu Cojocaru wrote:
It seems that in order for me to encrypt the messages I send to
someone, with PGP, I need his/her public key, is this true ?
Correct. Contained within that Public Key are all the User
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 12, 2001, at 4:25:31 AM, A Curtis Martin wrote:
AFAIK, you only need the senders public key to verify their signatures.
However, to decrypt an encrypted message to you, you only need your
private key to decrypt it. The messages encryption
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On 11 October 2000 at 20:23:26 GMT -0700 (which was 04:23 where I
live) Nick Andriash wrote and made these points on the subject
of "Encrypting Messages with PGP":
IOW's the box seems to pop up only when there is some u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
on Wednesday, October 11, 2000 02:21:04, our bat friend Marck D. Pearlstone typed:
NA Can someone please verify that for me, and if that is the case, I
NA want to put in a feature request to Stef and Max. PGP is designed
NA to give you that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Oct 2000 11:24:48 +0200, Krister Ekstrom wrote:
KE I have similar problems as Nick describes with pgp v6.5.8. I've just
KE switched to the ckt build of pgp 6.5.8 and have yet to post a
KE message which is encrypted to see if i have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 11, 2000 Marck D. Pearlstone Wrote:
That's it - and I always get (and always have got) the key selection
box when encrypting messages. This comes up before the pass-phrase
entry window IIRC.
Well that seems strange, because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Oct 2000 07:04:51 -0700, Nick Andriash wrote:
NA You make a good point there Allie, but what if you have more than
NA one Public Key associated with a given recipient... will TB!/6.5.8
NA produce the dialogue box giving you a choice of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 11, 2000 Marck D. Pearlstone Wrote:
I don't think it's a bug - I think it is how it is supposed to work.
After further reading Marck, I have to agree with you and Allie on this.
Apparently, if you want to force the PGP Recipient
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Oct 2000 15:28:53 +0100, Marck D. Pearlstone wrote:
NA Well that seems strange, because that was not my experience when
NA using TB! and 6.5.8 I can't see anything in your setup that was
NA any different in how I had PGP's options set.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Oct 2000 07:27:45 -0700, Nick Andriash wrote:
NA After further reading Marck, I have to agree with you and Allie on
NA this. Apparently, if you want to force the PGP Recipient Dialogue
NA box to appear, hold down the SHIFT key while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Nick,
On 11 October 2000 at 16:36:54 GMT -0700 (which was 00:36 where I
live) Nick Andriash wrote and made these points on the subject
of "Encrypting Messages with PGP":
NA If I remember correctly when I was using PGP 6.5.8 via TB!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 10, 2000 Marck D. Pearlstone Wrote:
That's not what I see. I get a selection dialog showing the two keys
which TB/PGP is intending to use (the recipient's and my default key)
in a small lower panel and allowing me to select any others
Hi Marck,
On Tuesday, October 10, 2000, 7:21 PM, you wrote in part about
"Encrypting Messages with PGP":
M That's not what I see. I get a selection dialog showing the two keys
M which TB/PGP is intending to use (the recipient's and my default key)
M in a small lower panel and a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Oct 2000 01:21:04 +0100, Marck D. Pearlstone wrote:
NA If I remember correctly when I was using PGP 6.5.8 via TB!'s
NA plug-in, no such dialogue box appeared, and the message was simply
NA encrypted to whomever it was addressed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 10, 2000 A. Curtis Martin Wrote:
IOW's the box seems to pop up only when there is some uncertainty as to
which key to use.
Thanks for the confirmation Allie. The mere fact that the dialogue box
doesn't appear under all conditions, is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 10 Oct 2000 20:23:26 -0700, Nick Andriash wrote:
NA Being able to choose multiple recipients is a feature of PGP's encryption
NA process, so not having that choice when using TB! is a clear indication
NA that the problem rests with the
35 matches
Mail list logo
