On 2023-09-01 16:15, Todd Zullinger wrote:
> Hi,
>
> Jan Eden wrote:
> > my configuration sets a PGP default key:
> >
> > set pgp_default_key = ...
> >
> > and outgoing messages are signed accordingly. But every time I reply
> > to a message sig
Hi,
Jan Eden wrote:
> my configuration sets a PGP default key:
>
> set pgp_default_key = ...
>
> and outgoing messages are signed accordingly. But every time I reply
> to a message signed using S/MIME, mutt tries to add an S/MIME signature,
> too (which fails, as t
Hi,
my configuration sets a PGP default key:
set pgp_default_key = ...
and outgoing messages are signed accordingly. But every time I reply
to a message signed using S/MIME, mutt tries to add an S/MIME signature,
too (which fails, as there is no S/MIME key available via GPGME).
How can I
I asked on gnupg-users. Adding "disable-dirmngr" to gpgsm.conf disbles
the use of the Dirmngr and thus expensive online checks that can take a
long time to timeout. This is a viable workaround.
I still believe it would be great to have an option in Mutt not to use
GPGME for S/M
Done, thanks: https://gitlab.com/muttmua/mutt/-/issues/450
Kevin J. McCarthy:
Yes, please go ahead. I don't have a current timeline for starting
master development again, but when I do, it will be good to have the
request there.
--
ilf
If you upload your address book to "the cloud", I don't
On Mon, Jul 31, 2023 at 08:43:22PM +0200, ilf wrote:
Do you think I should file a feature request for this in the tracker?
Yes, please go ahead. I don't have a current timeline for starting
master development again, but when I do, it will be good to have the
request there.
Thank you.
--
K
Do you think I should file a feature request for this in the tracker?
Kevin J. McCarthy:
There seem to be quite a few users with this issue. Do you think a
boolean option like "crypt_verify_smime" that explicitly works even
with GPGME would be feasible? From a user POV, it sure sounds
logical
ut, and have no
idea how to adjust that. Maybe others who use s/mime with GPGME have
ideas.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
ication needs before timing out? 25 seconds sounds much too long to
me.
Thanks a lot!
Kevin J. McCarthy:
So: How can I disable the S/MIME signature check while still using
GPGME for OpenPGP?
The option $crypt_verify_sig is shared between PGP and S/MIME, so you'll
have to be creative if yo
On Wed, Jul 26, 2023 at 09:37:34AM +0800, Kevin J. McCarthy wrote:
spam content-type:.*pkcs7 smime
Sorry, it's a good idea to root the regexp above:
spam ^content-type:.*pkcs7 smime
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
mmand="" (along with
smime_verify_opaque_command and smime_decrypt_command).
But this does not work. According to muttrc(5) the default value for
these three options is already "", and I am not setting them anywhere.
That option only works when $crypt_use_gpgme is unset.
So
Hi
I would also like to disable the S/MIME signature check. I have no use
for it. And "Invoking S/MIME..." takes 25 seconds before failing with
"S/MIME signature could NOT be verified."
I do use OpenPGP. So disabling "crypt_use_gpgme" is not an opt
IIUC, you would like to see which certificates have been used while
reading the mail. Sometime I also need such extra info, and I was
struggling to get the info. So I dove again a bit into it.
On 13Oct22 08:26+0200, Ralf Hildebrandt via Mutt-users wrote:
> > gpgsm --list-keys ralf.hildebra...@ch
* ckeader via Mutt-users :
> gpgsm --list-keys ralf.hildebra...@charite.de
>
> would give you all information about the key, including ID (which is the
> last part of the fingerprint), serial etc.
Yeah, that's awesome. Exactly what I need!
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung
me cases (please don't ask) my moron users have
> more than one valid certifcate in use and I'd like to know which one
> that is (because they don't know).
I do not seem to have this problem. Maybe using S/MIME support via gpgme
makes this all a bit easier to handle?
gpgsm -
3f1e2c.0: OK
==> checking purpose flags for b43f1e2c.0
S/MIME signing : Yes
S/MIME encryption : Yes
certificate b43f1e2c.0 (foo) for firstname.lastn...@charite.de added.
But what *IS* "b43f1e2c"? Is it a serial number, a part of the fingerprint?
> Also check the config opt
On 12Oct22 16:12+0200, Ralf Hildebrandt via Mutt-users wrote:
> when receiving an S/MIME signed mail, how can I extract information
> about the certificate / public key that was sent along with the
> signature?
Try ^K, which is the default keybind for `extract-keys`.
This command ext
Hi!
when receiving an S/MIME signed mail, how can I extract information
about the certificate / public key that was sent along with the
signature?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30
> >TBH this looks more like a gpg than a mutt problem, and I haven't
> >figured out how to debug this. Same error for encrypting.
>
> Yes, it sounds like something changed with either the GPGME version, or
> perhaps a configuration file. I can't offer much advice except to check
> those thin
On Wed, Apr 07, 2021 at 12:36:53PM +0100, isdtor wrote:
My S/MIME setup has died one from day to the next and I cannot find out why.
Symptom: trying to send e.g. signed email, the result is
error signing data: No CRL known?
This an error coming back from GPGME when trying to perform the sign
All,
My S/MIME setup has died one from day to the next and I cannot find out why.
Symptom: trying to send e.g. signed email, the result is
error signing data: No CRL known?
TBH this looks more like a gpg than a mutt problem, and I haven't figured out
how to debug this. Same erro
On Thu, Mar 25, 2021 at 10:52:46PM +0100, Andy Spiegl wrote:
> No mess at all. :-)
>
> see attached pic
>
> Andy
Cheers Andy!
Pete.
smime.p7s
Description: S/MIME cryptographic signature
No mess at all. :-)
see attached pic
Andy
--
Now I know what a statesman is; he's a dead politician. We need more statesmen.
(Bob Edwards)
Hi all,
I'm wondering how this mail appears to you all. Is it a mess or do you see
the 'signed message' boundaries?
Thanks.
Pete.
smime.p7s
Description: S/MIME cryptographic signature
Hi, my draft emails have a line in the header called Security: S/MIME. I then
can’t send anything because I don’t have a pass phrase.
Can I set Mutt to not use SMIME?
Thank you! Rob
Hi all,
I upgraded my email tool chain recently to the latest versions of
mutt/gpg/gpgme etc. and now S/MIME signing and encrypting no longer works. The
bad part is, going back to the previous executables also no longer works, so
I'm wondering whether gpg has updated some files
On Tue, May 15, 2018 at 03:27:15PM -0400, Todd Zullinger wrote:
> Kevin J. McCarthy wrote:
> > On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
> >> Is there an option in mutt to do this? Hopefully a run time
> >> option, not a compile time option...
> >
> > The compile-time conf
On 2018-05-15 09:06, Kevin J. McCarthy wrote:
> However, you could try set smime_verify_command="" (along with
> smime_verify_opaque_command and smime_decrypt_command).
Thanks, but unfortunately, this did not help. I found that
set crypt_use_gpgme=no
helps however (source: https://bugs.debian.or
Kevin J. McCarthy wrote:
> On Tue, May 15, 2018 at 09:40:38AM +0200, W. Martin Borgert wrote:
>> Is there an option in mutt to do this? Hopefully a run time
>> option, not a compile time option...
>
> The compile-time configuration is the cleanest way to turn it off.
> However, you could try set s
uot; (along with
smime_verify_opaque_command and smime_decrypt_command).
Alternatively, you could set crypt_verify_sig=ask-yes, but that affects
both PGP and S/MIME.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
Hi,
once in a while I get emails with S/MIME signatures. This is on
public mailing lists, where I seldomly care about signatures,
and I open the email only to read one or two lines to be sure I
can actually press 'd' :~)
Mutt says "Invoking S/MIME..." which takes too lon
*sigh* Never mind, something is not communicating well. After
flailing around for a while with gpgsm and associated tools, I found
that the problem is either that an intermediate certificate is
revoked or dirmngr is confused. I temporarily disabled CRL checking
and now mutt is happy to sign
I need to use PGP/MIME and S/MIME with different correspondents and I have
crypt_use_gpgme set. This works fine for PGP/MIME but has broken
S/MIME. I've set local-user in gpgsm but it seems to be ignored in
Mutt: "error signing data: End of file?". If I set
smime_default_key
I found:
http://comments.gmane.org/gmane.mail.mutt.user/40965
And right now I'm trying to send S/MIME signed mails from the command
line.
Invoking mutt interactively using my custom config:
% mutt -F ~/muttrc
works as expected (mail is being signed, sender is set correctly and
so on)
Inv
On 01Jul2015 20:12, Ian Zimmerman wrote:
On 2015-07-02 12:20 +1000, Cameron Simpson wrote:
I keep a little maildb which assigns group names to addresses, and
autogenerate mutt aliases formed like the above from it. Why the
maildb? Because my mail filing also uses these groups in its rules.
E
On 2015-07-02 12:20 +1000, Cameron Simpson wrote:
> I keep a little maildb which assigns group names to addresses, and
> autogenerate mutt aliases formed like the above from it. Why the
> maildb? Because my mail filing also uses these groups in its rules.
Excuse my ignorance, but what is a maild
On 30Jun2015 16:47, Jon LaBadie wrote:
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
> is it possible to use with one account PGP and S/Mime? I found a how-to
> for using S/Mime or using mutt with one account with PGP a
On 30/06 16:47, Jon LaBadie wrote:
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
> Hi,
>
> is it possible to use with one account PGP and S/Mime? I found a how-to
> for using S/Mime or using mutt with one account with
* Jon LaBadie [2015-06-30 16:53]:
> On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
> > On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
> > > Hi,
> > >
> > > is it possible to use with one account PGP and S/Mime? I found a how-to
> >
On Tue, Jun 30, 2015 at 10:11:53PM +0200, jonas hedman wrote:
> On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
> > Hi,
> >
> > is it possible to use with one account PGP and S/Mime? I found a how-to
> > for using S/Mime or using mutt with one account with PGP and on
On 15-06-30 22:00:27, Niels Kobschaetzki wrote:
> Hi,
>
> is it possible to use with one account PGP and S/Mime? I found a how-to
> for using S/Mime or using mutt with one account with PGP and one account
> S/Mime. But I want to use my main account with both and would like to
&g
Hi,
is it possible to use with one account PGP and S/Mime? I found a how-to
for using S/Mime or using mutt with one account with PGP and one account
S/Mime. But I want to use my main account with both and would like to
choose on a per user basis whether I encrypt via PGP or S/Mime. I know
people
Hi all,
My smime certificate recently expired and I've had to renew it. Now I'm
not entirely sure how I should use it. My first attempt was to import it
using smime_keys and then updating my smime_default_key entry:
set smime_default_key = '73bb549d.0'
to
set smime_default_key = '73bb549d.1'
On Wed, Apr 29, 2015 at 07:33:01PM +0200, Thomas Klausner wrote:
> Is there a way to configure mutt in such a way that I can read mails
> encrypted using my old key and ones encrypted using my current key in
> the same session?
Expired x.509 keys are one of the true pains in the ass of email secu
Hi!
I want to use mutt to send S/MIME encrypted/signed mails. I managed to
set up keys for myself and a friend once already, but they expired, so
I replaced my key. (I haven't managed to replace his key yet. I find
handling keys very hard, because there are too many formats and most
guides a
Hi,
I'm using Mutt for some time and It is great!
I have a number of cert/priv.keys already. All are imported into my
store under the label "zito".
All certs are one year validity.
zito@bobek:~/.keystore$ smime_keys list|fgrep zito
243f80ec.0: Issued for: vaclav.ov...@i.cz "zito" (Expired)
Hello-
When I imported my S/MIME certificates using smime_keys, I noticed
that it separated my signing certificate from my encryption
certificate. Is there a way that I can keep them together such that
when I sign an email the recipient can use the certificate attached to
the signed email to send
Hello-
I'm enjoying Mutt as my email client for work, and would really like
to get S/MIME working as well.
I've posted a question at superuser.com that I wanted to repost here
to see if anyone has some ideas. Thanks in advance for the help!
http://superuser.com/questions/766676/is-i
When I try to sign messages using s/mime, I get:
Varning: Temporärt certifikat hittas inte.Error opening signing key file
/home/per/.smime/keys/658483e2.0
3074218136:error:02001002:system
n the
> intermediate cert.
>
> But also extracting certificates from a smime-signed-e-mail (Ctrl-k)
> doesn't work (? as intermediate). I use the S/MIME-configuration from my
> homebrew setup
> (homebrew/Cellar/mutt/1.5.22/share/doc/mutt/samples/smime.rc).
>
> Maybe I
).
Could it be that the intermediate cert was not part of the p12 file bundle?
I just double-checked this: The Firefox-export didn't contain the
intermediate cert.
But also extracting certificates from a smime-signed-e-mail (Ctrl-k)
doesn't work (? as intermediate). I use the S/M
On Sunday 05 Jan 2014 19:10:42 Heiko Heil wrote:
> On Sun, Jan 05, 2014 at 04:25:39PM +0100, Heiko Heil wrote:
> > [...]
> > first.l...@domain.com 1a2b3c4d.0 me ? t
> > ^ email ^ key ^ label
> >
> >...but what about the last 2? I didn't find any information in the
> >manuals.
>
On Sun, Jan 05, 2014 at 04:25:39PM +0100, Heiko Heil wrote:
[...]
first.l...@domain.com 1a2b3c4d.0 me ? t
^ email ^ key ^ label
...but what about the last 2? I didn't find any information in the
manuals.
I found the description of those fields in smime.c:
/* 0=email 1=name
"--passin" option to openssl so that your smime-key can be decrypted
> properly.
I'm only encrypting the message (no signing) so I only use the public
certificate which isn't encrypted, of course.
I checked the .muttdebugX files and there isn't any reference to
S/MIME/encryption in the non-interactive case. It looks like it
doesn't even try to do this.
Thanks, for any advice!
Arpad Kunszt
a special muttrc for the automated sending
than mentions only the really required stuff. You might also want to use
"--passin" option to openssl so that your smime-key can be decrypted
properly.
Regards, Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Hi!
I want to use Mutt to send S/MIME encrypted (no signing is planned at
the moment, so just encrypting) e-mails from command line. The e-mails
consists of a short body and a variable number of attached files. The
content is generated by a cron job.
When I'm using the interactive user-inte
Hi,
I have a S/MIME key I'd like to use to sign some mails with. However, when
I select to sign a mail with my S/MIME key, after entering the passphrase,
mutt gives the following error:
Can't open OpenSSL subprocess!: No such file or directory (errno = 2)
Any idea what piece is m
give much more information in itself. However, I seem
to have found some pointers on their technet website:
http://technet.microsoft.com/en-us/library/aa995740%28EXCHG.65%29.aspx
http://technet.microsoft.com/en-us/library/aa995749%28EXCHG.65%29.aspx
> I believe in this case Outlook uses S/MIME mul
mailclients or e-mailclients on smartphones.
>
> Actually we might not have an idea, what “clear text” mode is…
I believe in this case Outlook uses S/MIME multipart/signed, so the
signature is in a separate body part and clients without S/MIME
support can still read the text/plain part of the mes
Hi,
Stas Verberkt schrieb am 17.11.2011 14:43:46:
> Nevertheless, disabling the "clear text" mode is not really an option,
> as this would render all my e-mails unreadable by those using older
> e-mailclients or e-mailclients on smartphones.
Actually we might not have an idea, what “clear text” m
L.S.,
Besides my installation with Mutt and GPG, I also have an Outlook 2010
installation with S/Mime enabled. This system is set up such that it
signs all my e-mail in the "clear text" mode.
The problem is that this results in Mutt not being able to verify the
signature and men
On Sat, Sep 11, 2010 at 04:01:27PM +0200, Remco Rijnders wrote:
> I'm hoping to use an S/MIME certificate issued by StartSSL to sign and
> encrypt my mail. When trying to add the certificate I get the following
> error:
>
> re...@silvertown:~$ smime_keys add_p12 startssl.cert
Hi all,
I'm hoping to use an S/MIME certificate issued by StartSSL to sign and
encrypt my mail. When trying to add the certificate I get the following
error:
re...@silvertown:~$ smime_keys add_p12 startssl.cert.p12
NOTE: This will ask you for two passphrases:
1. The passphrase you
Greetings,
I do have a valid S/MIME cert, which I am able to use in Thunderbird to sign
an crypt/decrypt.
However in mutt I fail to configure everything properly.
I can sign, crypt and decrypt, but verification fails with this error:
Verification failure
25294:error:21075075:PKCS7
I've been wrestling with this for a while, and I'm finally at the point
where I think I need help.
I've got a working S/MIME setup with mutt, and everything's great except
when it comes to selecting the right key to use when S/MIME kicks in.
For example, I have two keys:
Hi,
* rj wrote:
When I try to "(s)ign" an outgoing message from the S/MIME menu ("S" from
within the Compose Menu), I'm getting this warning: "Can't sign: No key
specified. Use Sign As."
And when I try to "sign (a)s" from the S/MIME m
rj:
> When I try to "(s)ign" an outgoing message from the S/MIME menu ("S" from
> within the Compose Menu), I'm getting this warning: "Can't sign: No key
> specified. Use Sign As."
I'm seing the same behavior here with mutt 1.5.18 on Fr
When I try to "(s)ign" an outgoing message from the S/MIME menu ("S" from
within the Compose Menu), I'm getting this warning: "Can't sign: No key
specified. Use Sign As."
And when I try to "sign (a)s" from the S/MIME menu, I get this warning:
&quo
Hi, I want to send a mail with S/MIME encryption without user activity.
S/Mime config works well in interactive mode, but I can't send an
encrypted mail via command line. The mail was always send in clear text.
Is it possible? Perhaps with macros, builtin commands that specified at
comman
Quoting Omen Wild <[EMAIL PROTECTED]> on Wed, Sep 25 10:37:
>
> I'll look into this. If that's the cause, then the problem is between
> my keyboard and chair, not yours. ;-)
For anyone following this, the problem was indeed on my end. I have an
updated patch, available from
http://descolada.da
Quoting Ren? Clerc <[EMAIL PROTECTED]> on Wed, Sep 25 15:01:
>
> Typically PEBCAK. The segfault was a result of not setting this
> variable. Strange side-effect, of course, but it works now!
I'll look into this. If that's the cause, then the problem is between
my keyboard and chair, not yours.
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:47]:
> * René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:25]:
>
> > * René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
> >
> > > This patch makes mutt segfault right after sending the e-mail. Despite
> > > of this, it works: both recipient and I a
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:25]:
> * René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
>
> > This patch makes mutt segfault right after sending the e-mail. Despite
> > of this, it works: both recipient and I are able to decrypt and read
> > the message.
> >
> > A clue, anyo
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
> This patch makes mutt segfault right after sending the e-mail. Despite
> of this, it works: both recipient and I are able to decrypt and read
> the message.
>
> A clue, anyone?
Let me be more specific: like I've already mailed Omen, I appli
* Omen Wild <[EMAIL PROTECTED]> [24-09-2002 21:24]:
> Quoting Ren? Clerc <[EMAIL PROTECTED]> on Tue, Sep 24 19:08:
> >
> > I'm looking for the S/MIME equivalent of the GnuPG option:
> >
> > encrypt-to
>
> As far as I could tell, it doesn&#
Quoting Ren? Clerc <[EMAIL PROTECTED]> on Tue, Sep 24 19:08:
>
> I'm looking for the S/MIME equivalent of the GnuPG option:
>
> encrypt-to
As far as I could tell, it doesn't exist. This patch add that
functionality. Set $smime_encrypt_self to true and S/MIME encr
Hi all,
I'm looking for the S/MIME equivalent of the GnuPG option:
encrypt-to
Because now I'm unable to read the encrypted e-mails I have sent to
some recipients...
I was not able to find it in TFM...
Thanks,
--
René Clerc - ([EMAIL PROTECTED])
If you
You are right. If you look at smime.c you will see that Mutt desperatly
needs either smime-type or (to satisfy Netscape 4.x mailers) a
Content-Description.
As s/mime is in development, we all have to wait or find some
workarounds for it. See my mail from 18-09-02 for my current solution.
I&#
is: Is the MS MUA not following the S/MIME standard by
> omitting this row or is mutt wrong by not being able to handle it
> without this row?
I'm quoting from RFC2633:
3.2:
...
Because there are several types of application/pkcs7-mime objects, a
sending agent SHOULD do as much as
I am currently using mutt 1.5.1 and the S/MIME functions have proved to
work without problems. But today I received an encrypted and signed
S/MIME message which could not be neither verified nor decrypted by mutt
(openssl). Here are the significant headers from two different mails,
the first mail
I have been looking into the mailing list software sympa and one of its
features is that when you send an S/MIME mail encrypted to the list, it
will re-encrypt for each recipient. The problem is that the mail shows
as being from me and to the list, so S/MIME was unable to find a key to
use to
Hi,
* Mike Schiraldi <[EMAIL PROTECTED]> [02-04-15 15:55]:
>> That doesn't sound as if you were a friend of these. Since I saw a few
>> using S/MIME in this list, what might have been their reason? Is
>> S/MIME better established with non-free software?
>We ha
currently using it to switch to S/MIME.
Another point why PGP and encryption/signing is not very
widely used is that there are lots people using the internet
who are not technically interested in it. If they knew more
details they maybe were interested in PGP or S/MIME. S/MIME
won't become the
> That doesn't sound as if you were a friend of these. Since I saw a few
> using S/MIME in this list, what might have been their reason? Is
> S/MIME better established with non-free software?
We had a discussion in February about this. Check out Jeremy's exc
begin Thorsten Haude quotation:
>
> using S/MIME in this list, what might have been their reason? Is
> S/MIME better established with non-free software?
Exactly.
--
Shawn McMahon| McMahon's Laws of Linux support:
http://www.eiv.com | 1) The
Hi,
* Will Yardley <[EMAIL PROTECTED]> [02-04-14 23:44]:
>s/mime sigs usually include the key itself along with the signature
>(which is why s/mime signed mails are so rediculously large).
That doesn't sound as if you were a friend of these. Since I saw a few
using S/MIME i
If I get a mail signed with PGP/GPG, I know that I need a
> key, where to get that key, how to authenticate the key, etc. Most
> important, I know how to make and distribute my own key.
>
> I don't know these things for S/MIME.
S/MIME doesn't work the same way as PGP. yo
Hi,
* Rocco Rutte <[EMAIL PROTECTED]> [02-04-14 22:56]:
>* Thorsten Haude [04/13/02 10:41:21 CEST] wrote:
>> I want to get a better picture about S/MIME, but can't find an
>> introduction in the net. Could one of you point me to a S/MIME
>> introduction or tutor
Hi,
* Thorsten Haude [04/13/02 10:41:21 CEST] wrote:
> I want to get a better picture about S/MIME, but can't find an
> introduction in the net. Could one of you point me to a S/MIME
> introduction or tutorial that is written for the user?
The "Linux Security HowTo&quo
Hi,
I want to get a better picture about S/MIME, but can't find an
introduction in the net. Could one of you point me to a S/MIME
introduction or tutorial that is written for the user?
Thorsten
--
They that can give up essential liberty to obtain a little
temporary safety deserve ne
On Tue, Feb 26, 2002 at 11:52:49AM +, Luke Ross wrote:
> How about a red line in the status bar? Would be most elegent surely?
that's what mutt_error does.
> I'm still on old S/MIME mutt, and I saw:
[ ... something ... ]
> What was the reason behind changing it? No scr
On Tue, Feb 26, 2002 at 11:24:56AM -0500, David Collantes wrote:
> What about only the sleep? The continue garbles my screen here, for some
> reason. I just patched with your diff, which got some rejection, btw. I
> would make it sleep for, lets say, 3 seconds and then to the mutt_error().
i thin
On Tue, Feb 26, 2002 at 12:20:33PM +0100, Oliver Ehli wrote:
> alternatively, we could just printf() the first (ie _not_ use
> mutt_error), wait for any_key, and then mutt_error() the second/final
> warning.
What about only the sleep? The continue garbles my screen here, for some
reason. I just
On Tue, Feb 26, 2002 at 12:20:33PM +0100, Oliver Ehli wrote:
> > A warning should absolutely be displayed, but should
> > mutt_any_key_to_continue() be called? A previous bugfix in another part of
> > smime.c mentioned that this is bad, and it added a sleep(5) call whose
> > purpose i didn't unde
Hi,
On Mon, Feb 25, 2002 at 02:24:27PM -0500, Mike Schiraldi wrote:
> Looks like we've got a display-corruption bug in current CVS -- when a
> message arrives whose "From" address doesn't match any in the S/MIME cert
> (like this message), the screen gets g
On Mon, Feb 25, 2002 at 02:24:27PM -0500, Mike Schiraldi wrote:
> Looks like we've got a display-corruption bug in current CVS -- when a
> message arrives whose "From" address doesn't match any in the S/MIME cert
> (like this message), the screen gets garbled.
>
Looks like we've got a display-corruption bug in current CVS -- when a
message arrives whose "From" address doesn't match any in the S/MIME cert
(like this message), the screen gets garbled.
A warning should absolutely be displayed, but should
mutt_any_key_to_continue() b
Something else you can try -- rename your ~/.smime and reinitialize it, so
that it is completely empty. Then, send your mutt account a signed message
from your Outlook account. Extract the S/MIME sig from it, and then reply to
it, with encryption turned on. See if Outlook can decrypt -that
Sorry if this seems like a "did you check the power cord" answer, but you
mention that you have two certificates. Are you positive that the one you
are encrypting to is the one which is installed in Outlook?
--
Mike Schiraldi
VeriSign Applied Research
msg24705/pgp0.pgp
Description: PGP s
On Fri, Feb 22, 2002 at 10:45:51AM -0500, Mike Schiraldi wrote:
> > Does anyone knows where could I find a s/mime howto? I just got 1.5.0i and
> > I want to try the s/mime support, but nothing comes with it to set it up.
> > How to create my certificate/key? How can I make it
1 - 100 of 163 matches
Mail list logo
