Any idea?
signature.asc
Description: OpenPGP digital signature
16.06.2013 01:44, Jochen Spieker ?:
> Alex Dubinin:
>> Hello, I'm trying to send email from a bash script with mutt and sign a
>> message of GPG.
> Where does the passphrase for signing crom from? It is usally read from
> stdin (the keyboard in this case).
>
> J.
I think:
# cat .muttrc
---
set
Alex Dubinin:
>
> Hello, I'm trying to send email from a bash script with mutt and sign a
> message of GPG.
Where does the passphrase for signing crom from? It is usally read from
stdin (the keyboard in this case).
J.
--
In public I try to remain calm and to appear perceptive.
[Agree] [Disagre
Hello, I'm trying to send email from a bash script with mutt and sign a
message of GPG.
I send mail as:
echo -e "${MSG}" | mutt -s "${SUB}" "${TO}" -a "attachment.tgz"
where
MSG - message
SUB - subject
TO - recipient
and attach a file.
This mail send fine.
I trying to sign this message so:
# cat
Hello.
Martin Dickopp:
> a standard solution to this problem is to encrypt the message with
> your own key in addition to the recipient's key. GnuPG will do this
> automatically if you put the line
>
> encrypt-to "your-key-id"
>
> in your ~/.gnupg/gpg.conf file.
Thanks, Martin, Johann and
"Shot (Piotr Szotkowski)" <[EMAIL PROTECTED]> writes:
> Recently I started learning how to use GPG for signing and encrypting my
> mail, and today noticed that the outgoing encrypted messages are copied
> into $record folder *after* the encryption; as you can imagine, this
> makes them quite usele
Hello
Shot (Piotr Szotkowski) (<[EMAIL PROTECTED]>) wrote:
> Recently I started learning how to use GPG for signing and encrypting
> my mail, and today noticed that the outgoing encrypted messages are
> copied into $record folder *after* the encryption; as you can imagine,
> this makes them quite
Hello.
Recently I started learning how to use GPG for signing and encrypting my
mail, and today noticed that the outgoing encrypted messages are copied
into $record folder *after* the encryption; as you can imagine, this
makes them quite useless for me, as I don't have the recipient's private
key.
On Thu, Dec 04, 2003 at 11:03:40AM +0100, Florian Ernst wrote:
> Hello Brian!
>
> On Wed, Dec 03, 2003 at 04:45:16PM -0600, Brian McGroarty wrote:
> >Automatic key retrieval is nice, however it also makes for very slow
> >mail reading if it's done inside of mutt.
> >
> >Has anyone set up procmail
On Fri, Dec 05, 2003 at 07:34:54AM +0100, Magnus von Koeller wrote:
Content-Description: signed data
> On Friday 05 December 2003 04:13, David wrote:
> > I have nothing whatsoever mentioning
> > auto-key-retrieve on the stable system. I've diffed the
> > corresponding ~/.muttrc's, /etc/Muttrc's and
On Friday 05 December 2003 04:13, David wrote:
> I have nothing whatsoever mentioning
> auto-key-retrieve on the stable system. I've diffed the
> corresponding ~/.muttrc's, /etc/Muttrc's and ~/.gnupg/options and
> cannot find anything that would account for the different
> behaviors.
Well, I don't
On Sat, Nov 29, 2003 at 08:49:01PM +0100, Florian Ernst wrote:
>
> You can import keys manually just like
> gpg --keyserver pgp.mit.edu --recv-keys 8DE4D38E
> for Karsten's key.
>
> If you want to have it done automatically one way is to enable a
> keyserver in your .gnupg/pgp.conf and enable
> k
Hello Brian!
On Wed, Dec 03, 2003 at 04:45:16PM -0600, Brian McGroarty wrote:
Automatic key retrieval is nice, however it also makes for very slow
mail reading if it's done inside of mutt.
Has anyone set up procmail to prefetch unknown keys automatically? I
thought I remembered some mention of thi
On Sat, Nov 29, 2003 at 08:49:01PM +0100, Florian Ernst wrote:
>
> You can import keys manually just like
> gpg --keyserver pgp.mit.edu --recv-keys 8DE4D38E
> for Karsten's key.
>
> If you want to have it done automatically one way is to enable a
> keyserver in your .gnupg/pgp.conf and enable
> k
On Sun, Mar 30, 2003 at 01:24:34AM -0600, Nathan Poznick wrote:
> What about the defaults in /etc/Muttrc ? Those work fine for me...
Yeah, those worked...sorry for the dumbass question...
--
.''`. Baloo Ursidae <[EMAIL PROTECTED]>
: :' :proud Debian admin and user
`. `'`
`- Debian
On Sat, Mar 29, 2003 at 10:07:14PM -0800, Paul Johnson wrote:
> The example fragments in /usr/share/doc/mutt/gpg.rc for gpg encrypt &
> sign fail horribly in reality with...
>
> Invoking PGP...
> usage: gpg [options] --sign --encrypt [filename]
> Press any key to continue...
>
> Has anybody found
Thus spake Paul Johnson:
> The example fragments in /usr/share/doc/mutt/gpg.rc for gpg encrypt &
> sign fail horribly in reality with...
>
> Invoking PGP...
> usage: gpg [options] --sign --encrypt [filename]
> Press any key to continue...
>
> Has anybody found a fix for this?
What about the defa
On Sat, Mar 29, 2003 at 10:07:14PM -0800, Paul Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The example fragments in /usr/share/doc/mutt/gpg.rc for gpg encrypt &
> sign fail horribly in reality with...
>
> Invoking PGP...
> usage: gpg [options] --sign --encrypt [filename]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The example fragments in /usr/share/doc/mutt/gpg.rc for gpg encrypt &
sign fail horribly in reality with...
Invoking PGP...
usage: gpg [options] --sign --encrypt [filename]
Press any key to continue...
Has anybody found a fix for this?
- --
.''`.
on Sat, Mar 30, 2002, Rohan Deshpande ([EMAIL PROTECTED]) wrote:
> Sorry everyone! Forgot the subject!
>
> --
> Rohan Deshpande
> [EMAIL PROTECTED]
>
> * Rohan Deshpande ([EMAIL PROTECTED]) wrote:
> > Hi there,
> >
> > I was just wondering: when using Mutt and GnuPG, with all the public
> > ke
Sorry everyone! Forgot the subject!
--
Rohan Deshpande
[EMAIL PROTECTED]
* Rohan Deshpande ([EMAIL PROTECTED]) wrote:
> Hi there,
>
> I was just wondering: when using Mutt and GnuPG, with all the public
> keys downloaded, what do you users do to keep the list of keys at a
> reasonable size? O
On Mon, Dec 11, 2000 at 04:25:37PM -0300, Eduardo Gargiulo wrote:
> Hi all.
>
> I'm new using mutt.
> I want to send my messeges clear signed, but I can't.
> I'm using gnupg, and I put in my .muttrc
> set pgp_sign_command="gpg --clearsign"
> but the signature is attached in binary format. How c
Hi all.
I'm new using mutt.
I want to send my messeges clear signed, but I can't.
I'm using gnupg, and I put in my .muttrc
set pgp_sign_command="gpg --clearsign"
but the signature is attached in binary format. How can I sign my messages in
ASCII from mutt?
--
:%s/Micros~1/GNU\/Linux/g^M
:wq!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 14, 2000 at 09:42:25PM -0400, Noah L. Meyerhans wrote:
> I have sort of worked up a workaround for this problem based on a macro
> given in /usr/local/share/doc/mutt/PGP-Notes.txt.gz. Adding this macro:
> macro compose S "Fgpg -s -a --clea
If it's any interest I can't see this email either.
I'm using pronto.
Tal
On Thu, 14 Sep 2000 01:58:04 +0100, Bruce Richardson said:
: No viewable part found.
--
| Tal Danzig | Join #libranet on the |
If it's any interest I can't see this email either.
I'm using pronto.
Tal
On Thu, 14 Sep 2000 01:58:04 +0100, Bruce Richardson said:
: No viewable part found.
--
| Tal Danzig | Join #libranet on the |
-BEGIN PGP SIGNED MESSAGE-
[ set pgp_create_traditional ]
> Does this work? Can Pine users etc see this?
Nope. I was only able to read your mail by saving it to a file...or by
opening it in mutt. 8^( Pine says this when viewing it:
[ Part 1, Application/PGP 1.1KB. ]
[ Not Sh
pgpJvzdNbVxOs.pgp
Description: PGP message
was one of the people having problems with mutt/gpg, and I believe the
recipient of the suggestion to use pgp_create_traditional. There are
major problems with either method, actually, to which I've found no
solutions.
If you use pgp_create_traditional, there is a single pgp signed message
at
I did some experimenting with my .muttrc since a couple of people have reported
they could not read my posts. My work (windows) outlook was the destination
for my emails. When I had set pgp_create_traditional in my .muttrc and signed
a message (no encrypt just sign) it came into the outlook as an
On Fri, Sep 08, 2000 at 10:47:06PM -0500, William Jensen wrote:
> I've been looking into gpg and mutt. I read on the mutt faq to "include"
> gpg.rc "with" my muttrc. Thing is I don't know what they mean "include"?
> Does mutt accept #include like c++?
I think they mean put the source keyword
Greetings,
I've been looking into gpg and mutt. I read on the mutt faq to "include"
gpg.rc "with" my muttrc. Thing is I don't know what they mean "include"?
Does mutt accept #include like c++?
As a previous note listed I added the set pgp_autosign in the .muttrc already.
Bill
pgpqM4SHids1S.
On Thu, Feb 10, 2000 at 09:39:51PM -0500, Jonathan Lupa wrote:
I use www.pgpkeys.net and it seems to work better than
search.keyserver.net from here. No thoughts as to why from me, but
perhaps someone else can enlighten us.
> Since I upgraded mutt from .95 to 1, I get the following error when
>
This must have been covered before, but I couldn't turn anything up on
a quick deja search. Apologies ahead of time for using this guys
fingerprint in vain, but I snagged it from the debian lists, so... :)
Since I upgraded mutt from .95 to 1, I get the following error when
mutt tries to "learn" ke
On Mon, Dec 20, 1999 at 10:50:21PM +, Jonathan McDowell wrote:
>
> On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
>
> > > I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> > > I guess it was a known bug that got fixed.
> > Is the mutt 1.0i availabl
> On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
> 1.0 appears to be in unstable according to a search on
> http://www.debian.org/distrib/packages
>
> > Is it able to handle automatically multipart/splitted messages (eg.
> > generated by mpack)?
Mutt has very sophsticated han
On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
> > I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> > I guess it was a known bug that got fixed.
> Is the mutt 1.0i available somewhere as a debian package?
1.0 appears to be in unstable according to a
On Mon, Dec 20, 1999 at 08:48:36PM +, Jonathan McDowell wrote:
>
> I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> I guess it was a known bug that got fixed.
Is the mutt 1.0i available somewhere as a debian package?
Is it able to handle automatically multipart/splitt
On Mon, Dec 20, 1999 at 06:57:17PM +0100, Wojciech Zabolotny wrote:
> I can't force my mutt/gpg set to work properly. Signing of messages
> works fine (as can be seen from this message :-) ), but I can't
> encrypt a message to be sent to somebody. I have the recipient&#
Hi all,
I can't force my mutt/gpg set to work properly. Signing of messages works fine
(as can be seen from this message :-) ), but I can't encrypt a message to be
sent
to somebody. I have the recipient's public key in my public keyring. I can
encrypt the date with this recipie
40 matches
Mail list logo
