Re: incorporating s/mime??
* Christoph Ludwig <cludwig@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> [20031004 14:12]:
wrote:
> On Sat, Oct 04, 2003 at 01:47:32PM +0300, Odhiambo Washington wrote:
> > 155$ smime_keys add_p12 thawte.p12
> >
> [...]
> > Verifying - Enter PEM pass phrase:
> > Use of uninitialized value in string eq at /usr/local/bin/smime_keys line
> > 961.
>
> This warning is harmless but annoying. My posting to mutt-dev on
> June 10, 2003 contains a simple patch to smime_keys.pl that fixes the
> bug, but AFAIK the patch didn't make it into mutt's CVS.
I guess I will look for tha patch and apply it manually ..
> > You may assign a label to this key, so you don't have to remember
> > the key ID. This has to be _one_ word (no whitespaces).
> >
> > Enter label: wathingito
> > Error opening Certificate /2d8356f7.0
> > 92154:error:0200100D:system library:fopen:Permission
> > denied:bss_file.c:259:fopen('/2d8356f7.0','r')
>
> I am not surprised that you can't access the file '/2d8356f7.0'. It
> seems smime_keys was unable to get the directory where you store your
> keys and certificates.
>
> What's the result of, e.g., 'mutt -Q smime_certificates'? If this does
> not point to the correct directory then your smime setup in .muttrc is
> not correct.
I got it! Thanks a lot. I had not created ~/.smime/certificates (the
certificates dir).
Now it works, almost, but I get
Enter label: wash
added certificate: /home/wash/.smime/certificates/2d8356f7.0.
Couldn't open /home/wash/.smime/certificates/.index: No such file or directory
at /usr/local/bin/smime_keys line 418, <STDIN>
line 1.
Wht is a .index rqd?
THANK YOU VERY MUCH.
-Wash
--
Odhiambo Washington <wash@xxxxxxxxxxxx> "The box said 'Requires
Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,'
Tel: +254 2 313985-9 +254 2 313922 so I installed FreeBSD."
GSM: +254 72 743223 +254 733 744121 This sig is McQ! :-)
Bug, n.:
An aspect of a computer program which exists because the
programmer was thinking about Jumbo Jacks or stock options when s/he
wrote the program.
Fortunately, the second-to-last bug has just been fixed.
-- Ray Simard