\e$B$3$N5!G=$r;H$&$K$O\e(B @uref{http://www.gnu.org/software/libidn/, GNU
Libidn} \e$B$r%$%s%9%H!<%k$7$F$*$/I,MW$,$"$j$^$9!#\e(B
-@c TRANSLATEME
@node Security
-@section Security
+@section \e$B%;%-%e%j%F%#!<\e(B
@cindex Security
@cindex S/MIME
@cindex PGP
@cindex encrypt
@cindex secure
-Using the @acronym{MML} language, Message is able to create digitally
-signed and digitally encrypted messages. Message (or rather
-@acronym{MML}) currently support @acronym{PGP} (RFC 1991),
-@acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}. Instructing
-@acronym{MML} to perform security operations on a @acronym{MIME} part is
-done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c C-m
-c} key map for encryption, as follows.
+@acronym{MML} \e$B$r;H$C$F!"\e(BMessage \e$B$OEE;R=pL>$5$l$?!"$^$?$OEE;R0E9f2=$5$l$?\e(B
+\e$B%a%C%;!<%8$r:n$k$3$H$,$G$-$^$9!#\e(BMessage (\e$B$H8@$&$+\e(B @acronym{MML}) \e$B$O!"8=\e(B
+\e$B:_\e(B @acronym{PGP} (RFC 1991), @acronym{PGP/MIME} (RFC 2015/3156) \e$B$*$h\e(B
+\e$B$S\e(B @acronym{S/MIME} \e$B$r%5%]!<%H$7$^$9!#\e(B@acronym{MIME} \e$B%Q!<%H$KBP$7$F%;%-%e\e(B
+\e$B%j%F%#!<$NA`:n$r9T$J$&$?$a$N\e(B @acronym{MML} \e$B$X$N;X<($O!"0J2<$N$h$&$K!"=p\e(B
+\e$BL>$N>l9g$O\e(B @kbd{C-c C-m s} \e$B%-!<%^%C%W$r;H$C$F!"0E9f2=$N>l9g$O\e(B @kbd{C-c
+C-m c} \e$B%-!<%^%C%W$r;H$C$F9T$J$$$^$9!#\e(B
@table @kbd
-
@item C-c C-m s s
@kindex C-c C-m s s
@findex mml-secure-message-sign-smime
-Digitally sign current message using @acronym{S/MIME}.
+@acronym{S/MIME} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$KEE;R=qL>$7$^$9!#\e(B
@item C-c C-m s o
@kindex C-c C-m s o
@findex mml-secure-message-sign-pgp
-Digitally sign current message using @acronym{PGP}.
+@acronym{PGP} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$KEE;R=qL>$7$^$9!#\e(B
@item C-c C-m s p
@kindex C-c C-m s p
@findex mml-secure-message-sign-pgpmime
-Digitally sign current message using @acronym{PGP/MIME}.
+@acronym{PGP/MIME} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$KEE;R=qL>$7$^$9!#\e(B
@item C-c C-m c s
@kindex C-c C-m c s
@findex mml-secure-message-encrypt-smime
-Digitally encrypt current message using @acronym{S/MIME}.
+@acronym{S/MIME} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$rEE;R0E9f2=$7$^$9!#\e(B
@item C-c C-m c o
@kindex C-c C-m c o
@findex mml-secure-message-encrypt-pgp
-Digitally encrypt current message using @acronym{PGP}.
+@acronym{PGP} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$rEE;R0E9f2=$7$^$9!#\e(B
@item C-c C-m c p
@kindex C-c C-m c p
@findex mml-secure-message-encrypt-pgpmime
-Digitally encrypt current message using @acronym{PGP/MIME}.
+@acronym{PGP/MIME} \e$B$r;H$C$F!"8=:_$N%a%C%;!<%8$rEE;R0E9f2=$7$^$9!#\e(B
@item C-c C-m C-n
@kindex C-c C-m C-n
@findex mml-unsecure-message
-Remove security related @acronym{MML} tags from message.
-
+\e$B%a%C%;!<%8$+$i!"%;%-%e%j%F%#!<4XO"$N\e(B @acronym{MML} \e$B%?%0$r30$7$^$9!#\e(B
@end table
-These commands do not immediately sign or encrypt the message, they
-merely insert the proper @acronym{MML} secure tag to instruct the
-@acronym{MML} engine to perform that operation when the message is
-actually sent. They may perform other operations too, such as locating
-and retrieving a @acronym{S/MIME} certificate of the person you wish to
-send encrypted mail to. When the mml parsing engine converts your
-@acronym{MML} into a properly encoded @acronym{MIME} message, the secure
-tag will be replaced with either a part or a multipart tag. If your
-message contains other mml parts, a multipart tag will be used; if no
-other parts are present in your message a single part tag will be used.
-This way, message mode will do the Right Thing (TM) with
-signed/encrypted multipart messages.
-
-Since signing and especially encryption often is used when sensitive
-information is sent, you may want to have some way to ensure that your
-mail is actually signed or encrypted. After invoking the above
-sign/encrypt commands, it is possible to preview the raw article by
-using @kbd{C-u C-c RET P} (@code{mml-preview}). Then you can
-verify that your long rant about what your ex-significant other or
-whomever actually did with that funny looking person at that strange
-party the other night, actually will be sent encrypted.
-
-@emph{Note!} Neither @acronym{PGP/MIME} nor @acronym{S/MIME} encrypt/signs
-RFC822 headers. They only operate on the @acronym{MIME} object. Keep this
-in mind before sending mail with a sensitive Subject line.
-
-By default, when encrypting a message, Gnus will use the
-``signencrypt'' mode, which means the message is both signed and
-encrypted. If you would like to disable this for a particular
-message, give the @code{mml-secure-message-encrypt-*} command a prefix
-argument, e.g., @kbd{C-u C-c C-m c p}.
-
-Actually using the security commands above is not very difficult. At
-least not compared with making sure all involved programs talk with each
-other properly. Thus, we now describe what external libraries or
-programs are required to make things work, and some small general hints.
-
-@subsection Using S/MIME
-
-@emph{Note!} This section assume you have a basic familiarity with
-modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
-so on.
-
-The @acronym{S/MIME} support in Message (and @acronym{MML}) require
-OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
-operations. OpenSSL can be found at @uref{http://www.openssl.org/}.
-OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail
-addresses from certificates, and it insert a spurious CR character into
-@acronym{MIME} separators so you may wish to avoid it if you would like
-to avoid being regarded as someone who send strange mail. (Although by
-sending @acronym{S/MIME} messages you've probably already lost that
-contest.)
-
-To be able to send encrypted mail, a personal certificate is not
-required. Message (@acronym{MML}) need a certificate for the person to whom you
-wish to communicate with though. You're asked for this when you type
-@kbd{C-c C-m c s}. Currently there are two ways to retrieve this
-certificate, from a local file or from DNS. If you chose a local
-file, it need to contain a X.509 certificate in @acronym{PEM} format.
-If you chose DNS, you're asked for the domain name where the
-certificate is stored, the default is a good guess. To my belief,
-Message (@acronym{MML}) is the first mail agent in the world to support
-retrieving @acronym{S/MIME} certificates from DNS, so you're not
-likely to find very many certificates out there. At least there
-should be one, stored at the domain @code{simon.josefsson.org}. LDAP
-is a more popular method of distributing certificates, support for it
-is planned. (Meanwhile, you can use @code{ldapsearch} from the
-command line to retrieve a certificate into a file and use it.)
-
-As for signing messages, OpenSSL can't perform signing operations
-without some kind of configuration. Especially, you need to tell it
-where your private key and your certificate is stored. @acronym{MML}
-uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
-contain a @code{custom} group used for this configuration. So, try
-@kbd{M-x customize-group RET smime RET} and look around.
-
-Currently there is no support for talking to a CA (or RA) to create
-your own certificate. None is planned either. You need to do this
-manually with OpenSSL or using some other program. I used Netscape
-and got a free @acronym{S/MIME} certificate from one of the big CA's on the
-net. Netscape is able to export your private key and certificate in
-PKCS #12 format. Use OpenSSL to convert this into a plain X.509
-certificate in PEM format as follows.
+\e$B$3$l$i$N%3%^%s%I$O!"$=$N>l$G%a%C%;!<%8$K=pL>$7$?$j0E9f2=$9$k$o$1$G$O$J$/!"\e(B
+\e$B$=$l$i$OC1$K%;%-%e%j%F%#!<$N$?$a$NE,@Z$J\e(B @acronym{MML} \e$B%?%0$rA^F~$7$F!"\e(B
+\e$B%a%C%;!<%8$,<B:]$KAw?.$5$l$k$H$-$K$=$NF0:n$r<B9T$9$k$h$&$K!"\e(B
+@acronym{MML} \e$B%(%s%8%s$K;X<($rM?$($k$@$1$G$9!#$=$l$i$OB>$N;E;v!"Nc$($P0E\e(B
+\e$B9f2=$5$l$?%a!<%k$rAw$j$?$$Aj<j$N?M$N\e(B @acronym{S/MIME} \e$B$N>ZL@=q$rC5$7$F<h\e(B
+\e$B$j4s$;$k$h$&$J$3$H$b9T$J$&$+$b$7$l$^$;$s!#\e(Bmml \e$B2r@O%(%s%8%s\e(B
+\e$B$,\e(B @acronym{MML} \e$B$G=q$+$l$?%a%C%;!<%8$r\e(B @acronym{MIME} \e$B%a%C%;!<%8$KE,@Z\e(B
+\e$B$KJQ49$9$k$H$-!"%;%-%e%j%F%#!<$N$?$a$N%?%0$O!"%Q!<%H$^$?$O%^%k%A%Q!<%H$N\e(B
+\e$B$I$A$i$+0lJ}$N%?%0$GCV$-49$($i$l$^$9!#%a%C%;!<%8$,B>$N\e(B mml \e$B%Q!<%H$b4^$s\e(B
+\e$B$G$$$k>l9g$K$O%^%k%A%Q!<%H$N%?%0$,;H$o$l!"B>$N%Q!<%H$,L5$$>l9g$OC10l$N%Q!<\e(B
+\e$B%H$N%?%0$,;H$o$l$k$G$7$g$&!#$3$N$h$&$K$7$F!"=pL>$5$l$k\e(B/\e$B0E9f2=$5$l$k%^%k\e(B
+\e$B%A%Q!<%H$N%a%C%;!<%8$KBP$7!"%a%C%;!<%8!&%b!<%I$O!V@5$7$$$3$H\e(B (\e$BEPO?>&I8\e(B)\e$B!W\e(B
+(\e$B86J8\e(B: Right Thing (TM)) \e$B$r9T$J$$$^$9!#\e(B
+
+\e$B=pL>$=$7$FFC$K0E9f2=$O!"$7$P$7$P5!L)>pJs$rAw?.$9$k$H$-$K;H$o$l$k$N$G!"%a!<\e(B
+\e$B%k$,K\Ev$K=pL>$^$?$O0E9f2=$5$l$k$3$H$r3N<B$K$9$k$?$a$N!"2?$i$+$N<jCJ$rI,\e(B
+\e$BMW$H$9$k$G$7$g$&!#>e5-$N=pL>\e(B/\e$B0E9f2=%3%^%s%I$r<B9T$7$?8e$G$J$i!"\e(B@kbd{C-u
+C-c RET P} (@code{mml-preview}) \e$B$r;H$&$3$H$K$h$C$F!"@8$N5-;v$r2<8+$9$k$3\e(B
+\e$B$H$,2DG=$G$9!#$=$&$7$F!"$"$J$?$N0JA0$KBg@Z$@$C$??M$K4X$9$k!"$"$k$$$O!"$3\e(B
+\e$B$NA0$NLk$NJQ$J%Q!<%F%#!<$G!"$"$N$*$+$7$J?H$J$j$N?M$,<B:]$K$d$C$?$3$H$K4X\e(B
+\e$B$9$k$"$J$?$ND9$$GME]$,!"K\Ev$K0E9f2=$5$l$FAw?.$5$l$k$G$"$m$&$3$H$r!"3NG'\e(B
+\e$B$9$k$3$H$,$G$-$^$9!#\e(B
+
+@emph{\e$BCm0U\e(B!} @acronym{PGP/MIME} \e$B$H\e(B @acronym{S/MIME} \e$B$N$I$A$i$b!"\e(B
+RFC822 \e$B%X%C%@!<$r=pL>\e(B/\e$B0E9f2=$7$^$;$s!#$=$l$i$O\e(B @acronym{MIME} \e$B%Q!<%H$K$N\e(B
+\e$B$_:nMQ$7$^$9!#5!L)$NBjL>$H$H$b$K%a!<%k$rAw$C$F$7$^$&A0$K!"$3$N$3$H$r4N$K\e(B
+\e$BL?$8$F2<$5$$!#\e(B
+
+\e$B%a%C%;!<%8$r0E9f2=$9$k$H$-!"\e(BGnus \e$B$O%G%#%U%)%k%H$G!V=pL>\e(B+\e$B0E9f2=!W\e(B(\e$B%a%C%;!<\e(B
+\e$B%8$KBP$7$F=pL>$H0E9f2=$NN>J}$,9T$J$o$l$k\e(B) \e$B%b!<%I$r;H$$$^$9!#FCDj$N%a%C%;!<\e(B
+\e$B%8$KBP$7$F$3$l$r9T$J$o$;$?$/$J$$$J$i$P!"\e(B
+@code{mml-secure-message-encrypt-*} \e$B%3%^%s%I$K@\F,0z?t$rM?$($F\e(B (\e$BNc$(\e(B
+\e$B$P\e(B @kbd{C-u C-c C-m c p} \e$B$r;H$C$F\e(B) \e$B2<$5$$!#\e(B
+
+\e$B>e5-$N%;%-%e%j%F%#!<%3%^%s%I$r<B:]$K;H$&$N$O!"$5$[$IFq$7$/$"$j$^$;$s!#>/\e(B
+\e$B$J$/$H$b!"$9$Y$F$N4X78$9$k%W%m%0%i%`$,E,@Z$KDL?.$79g$&$3$H$r3N$+$a$k$3$H\e(B
+\e$B$HHf3S$7$F!#$=$3$G!"30It$N$I$s$J%i%$%V%i%j!<$^$?$O%W%m%0%i%`$,I,MW$+!"$*\e(B
+\e$B$h$S$$$/$D$+$N:3:Y$G0lHLE*$J%R%s%H$K$D$$$F!"=R$Y$k$3$H$K$7$^$9!#\e(B
+
+@subsection S/MIME \e$B$r;H$&\e(B
+
+@emph{\e$BCm0U\e(B!} \e$B$3$N9`$O!"6aBeE*$J0E9fK!!"\e(B@acronym{S/MIME}\e$B!"$5$^$6$^\e(B
+\e$B$J\e(B PKCS \e$B$NI8=`!"\e(BOpenSSL \e$B$J$I$N4pAC$K!"$"$J$?$,@:DL$7$F$$$k$3$H$r2>Dj$7$^\e(B
+\e$B$9!#\e(B
+
+Message (\e$B$=$l$K\e(B @acronym{MML}) \e$B$G\e(B @acronym{S/MIME} \e$B$r%5%]!<%H$9$k$K$O!"\e(B
+OpenSSL \e$B$,I,MW$G$9!#\e(BOpenSSL \e$B$O<B:]$N\e(B @acronym{S/MIME} \e$B$K$h$k=pL>\e(B/\e$B0E9f2=\e(B
+\e$B$N=hM}$r<B9T$7$^$9!#\e(BOpenSSL \e$B$O\e(B @uref{http://www.openssl.org/} \e$B$G8+$D$+$j\e(B
+\e$B$^$9!#\e(BOpenSSL 0.9.6 \e$B0J9_$N$b$N$,F0:n$9$k$O$:$G$9!#%P!<%8%g%s\e(B 0.9.5a \e$B$O>Z\e(B
+\e$BL@=q$+$i%a!<%k%"%I%l%9$rCj=P$9$k$3$H$,$G$-$J$$$7!"\e(B@acronym{MIME} \e$B$N%;%Q\e(B
+\e$B%l!<%?$KM>7W$J\e(B CR \e$BJ8;z$rA^F~$9$k$N$G!"JQ$J%a!<%k$rAw$k?M$@$H;W$o$l$?$/$J\e(B
+\e$B$1$l$P!"$=$l$r;H$&$3$H$rHr$1$?$$$G$7$g$&!#\e(B(\e$B$b$C$H$b!"$"$J$?\e(B
+\e$B$O\e(B @acronym{S/MIME} \e$B$N%a%C%;!<%8$rAw$k$3$H$K$h$C$F!"$=$NJQ?M%3%s%F%9%H$G\e(B
+\e$B$N>!Mx$rF($7$^$7$?$,!#\e(B)
+
+\e$B0E9f2=$5$l$?%a!<%k$rAw$k$?$a$K!"8D?M$N>ZL@=q$OMW$j$^$;$s!#\e(BMessage
+(@acronym{MML}) \e$B$O!"DL?.$7$?$$Aj<j$N?M$N>ZL@=q$rI,MW$H$7$^$9$1$l$I!#\e(B
+\e$B$3$N$3$H$O\e(B @kbd{C-c C-m c s} \e$B$r%?%$%W$7$?$H$-$K?R$M$i$l$^$9!#$3$N>ZL@=q\e(B
+\e$B$r%m!<%+%k%U%!%$%k$+\e(B DNS \e$B$+$i<h$j4s$;$k$?$a$K$O!"8=:_Fs$D$NJ}K!$,$"$j$^\e(B
+\e$B$9!#%m!<%+%k%U%!%$%k$rA*Br$7$?>l9g!"$=$l$O\e(B @acronym{PEM} \e$B7A<0$K$h\e(B
+\e$B$k\e(B X.509 \e$B>ZL@=q$r4^$s$G$$$kI,MW$,$"$j$^$9!#\e(BDNS \e$B$rA*$s$@>l9g$K$O!"$=$N>Z\e(B
+\e$BL@=q$,3JG<$5$l$F$$$k%I%a%$%sL>$r?R$M$i$l$^$9\e(B (\e$B%G%#%U%)%k%H$O>e<j$K?dB,$7\e(B
+\e$B$?$b$N$G$9\e(B)\e$B!#;d$,?.$8$k8B$j!"\e(B
+Message (@acronym{MML}) \e$B$O\e(B @acronym{S/MIME} \e$B$N>ZL@=q$r\e(B DNS \e$B$+$i<h$j4s$;\e(B
+\e$B$k@$3&=i$N%a!<%k!&%(!<%8%'%s%H$J$N$G!"$=$3$GHs>o$KB?$/$N>ZL@=q$r8+$D$1=P\e(B
+\e$B$9$3$H$O$J$$$G$7$g$&!#>/$J$/$H$b0l$D$@$1$O!"\e(B
+@code{simon.josefsson.org} \e$B%I%a%$%s$K3JG<$5$l$?$b$N$,$"$k$O$:$G$9!#\e(B
+LDAP \e$B$O$b$C$HIa5Z$7$F$$$k>ZL@=q$rG[5k$9$k<jK!$G!"$=$l$r%5%]!<%H$9$k$3$H\e(B
+\e$B$,7W2h$5$l$F$$$^$9!#\e(B(\e$BOCJQ$o$C$F!"\e(B@code{ldapsearch} \e$B$r%3%^%s%I%i%$%s$+$i\e(B
+\e$B<B9T$7$F>ZL@=q$r%U%!%$%k$K<h$j9~$s$G!"$=$l$r;H$&$3$H$,$G$-$^$9!#\e(B)
+
+\e$B%a%C%;!<%8$N=pL>$K$D$$$F$O!"$"$k<o$N@_DjL5$7$G$O\e(B OpenSSL \e$B$O=pL>$N=hM}$r\e(B
+\e$B<B9T$9$k$3$H$,$G$-$^$;$s!#$H$j$o$1!"$"$J$?$NHkL)80\e(B (private key) \e$B$H>ZL@\e(B
+\e$B=q$,$I$3$K3JG<$5$l$F$$$k$+$r65$($F$"$2$kI,MW$,$"$j$^$9!#\e(B@acronym{MML} \e$B$O\e(B
+\e$B$=$NL>$K$U$5$o$7$$\e(B @code{smime.el} \e$B$H$$$&\e(B Emacs \e$B%$%s%?!<%U%'!<%9\e(B
+\e$B$r\e(B OpenSSL \e$B$KBP$7$F;H$$!"$=$l$O$3$N@_Dj$K;H$&$?$a$N$?$a\e(B
+\e$B$N\e(B @code{custom} \e$B%0%k!<%W$r4^$s$G$$$^$9!#$G$9$+$i!"\e(B
+@kbd{M-x customize-group RET smime RET} \e$B$r;n$7$F!"D/$a$F$_$F2<$5$$!#\e(B
+
+\e$B8=:_$O!"\e(BCA (\e$B$^$?$O\e(B RA) \e$B$HDL?.$7$F$"$J$?<+?H$N>ZL@=q$r@8@.$9$k$?$a$N%5%]!<\e(B
+\e$B%H$O$"$j$^$;$s!#$=$l$K7W2h$b$"$j$^$;$s!#;d$O\e(B Netscape \e$B$r;H$C$F!"%M%C%H>e\e(B
+\e$B$K$"$kBg$-$J\e(B CA \e$B$N0l$D$+$i!"L5NA$N\e(B @acronym{S/MIME} \e$B$N>ZL@=q$r$b$i$$$^$7\e(B
+\e$B$?!#\e(BNetscape \e$B$OHkL)80$H>ZL@=q$r\e(B PKCS #12 \e$B7A<0$GM"=P\e(B (export) \e$B$9$k$3$H$,\e(B
+\e$B$G$-$^$9!#\e(BOpenSSL \e$B$r;H$C$F!"$3$l$r0J2<$N$h$&$K\e(B PEM \e$B7A<0$K$h$kAG\e(B
+\e$B$N\e(B (plain) X.509 \e$B>ZL@=q$KJQ49$7$F2<$5$$!#\e(B
@example
$ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
@end example
-The @file{key+cert.pem} file should be pointed to from the
-@code{smime-keys} variable. You should now be able to send signed mail.
-
-@emph{Note!} Your private key is now stored unencrypted in the file,
-so take care in handling it. Storing encrypted keys on the disk are
-supported, and Gnus will ask you for a passphrase before invoking
-OpenSSL. Read the OpenSSL documentation for how to achieve this. If
-you use unencrypted keys (e.g., if they are on a secure storage, or if
-you are on a secure single user machine) simply press @code{RET} at
-the passphrase prompt.
-
-@subsection Using PGP/MIME
+@code{smime-keys} \e$BJQ?t$,!"\e(B@file{key+cert.pem} \e$B%U%!%$%k$r;X$7<($9$h$&$K$7\e(B
+\e$B$J$1$l$P$J$j$^$;$s!#:#$d$"$J$?$O!"=pL>$5$l$?%a%C%;!<%8$rAw?.$G$-$k$O$:$G\e(B
+\e$B$9!#\e(B
-@acronym{PGP/MIME} requires an external OpenPGP implementation, such
-as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP
-implementations such as PGP 2.x and PGP 5.x are also supported. One
-Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG,
-pgg-ja, PGG Manual}), is included, but Mailcrypt and Florian Weimer's
-@code{gpg.el} are also supported.
+@emph{\e$BCm0U\e(B!} \e$B$"$J$?$N80$O:#!"0E9f2=$5$l$:$K%U%!%$%k$K3JG<$5$l$?$N$G!"$=\e(B
+\e$B$l$N07$$$K$O5$$rIU$1$F2<$5$$!#0E9f2=$5$l$?80$N%U%!%$%k$X$N3JG<$O%5%]!<%H\e(B
+\e$B$5$l$F$$$F!"$=$N>l9g$O\e(B OpenSSL \e$B$r:nF0$9$kA0$K\e(B Gnus \e$B$,%Q%9%U%l!<%:$r?R$M\e(B
+\e$B$k$G$7$g$&!#$I$&$d$C$F$=$l$r@.$7?k$2$k$+$K$D$$$F$O!"\e(BOpenSSL \e$B$N%I%-%e%a%s\e(B
+\e$B%H$rFI$s$G2<$5$$!#0E9f2=$5$l$F$$$J$$80$r;H$&\e(B (\e$BNc$($P$=$l$i$,0BA4$J%9%H%l!<\e(B
+\e$B%8$K$"$k!"$^$?$O!"$"$J$?$,0BA4$J%7%s%0%k!&%f!<%6$N%^%7%s$K$$$k\e(B) \e$B$N$G$"$l\e(B
+\e$B$P!"%Q%9%U%l!<%:$NF~NO$rMW5a$5$l$?$H$-!"C1$K\e(B @kbd{RET} \e$B$r2!$7$F2<$5$$!#\e(B
+
+@subsection PGP/MIME \e$B$r;H$&\e(B
+
+@acronym{PGP/MIME} \e$B$O\e(B @uref{http://www.gnupg.org/, GNU Privacy Guard} \e$B$N\e(B
+\e$B$h$&$J!"30It$N\e(B OpenPGP \e$B$N<BAu$rI,MW$H$7$^$9!#\e(BOpenPGP \e$B$h$j0JA0$N<BAu$G$"\e(B
+\e$B$k\e(B PGP 2.x \e$B$H\e(B PGP 5.x \e$B$b%5%]!<%H$7$^$9!#\e(BPGP \e$B$N<BAu$X$N0l$D$N\e(B Emacs \e$B%$%s\e(B
+\e$B%?!<%U%'!<%9$G$"$k\e(B (@pxref{Top, ,PGG, pgg-ja, PGG Manual}) \e$B$,4^$^$l$F$$\e(B
+\e$B$^$9$,!"\e(BMailcrypt \e$B$H\e(B Florian Weimer \e$B$5$s$N\e(B @code{gpg.el} \e$B$b%5%]!<%H$7$^\e(B
+\e$B$9!#\e(B
@vindex gpg-temp-directory
-Note, if you are using the @code{gpg.el} you must make sure that the
-directory specified by @code{gpg-temp-directory} have permissions
-0700.
-
-Creating your own key is described in detail in the documentation of
-your PGP implementation, so we refer to it.
-
-If you have imported your old PGP 2.x key into GnuPG, and want to send
-signed and encrypted messages to your fellow PGP 2.x users, you'll
-discover that the receiver cannot understand what you send. One
-solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
-@code{pgg-default-scheme} to @code{pgp}). If you do want to use
-GnuPG, you can use a compatibility script called @code{gpg-2comp}
-available from
-@uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You
-could also convince your fellow PGP 2.x users to convert to GnuPG.
+\e$BCm\e(B: \e$B$b$7\e(B @code{gpg.el} \e$B$r;H$&$N$G$"$l$P!"\e(B@code{gpg-temp-directory} \e$B$G;X\e(B
+\e$BDj$5$l$k%G%#%l%/%H%j$N%Q!<%_%C%7%g%s$,\e(B 0700 \e$B$K$J$C$F$$$k$3$H$r3NG'$7$F2<\e(B
+\e$B$5$$!#\e(B
+
+\e$B$"$J$?$N\e(B PGP \e$B$N<BAu$N%I%-%e%a%s%H$G>\$7$/=R$Y$i$l$F$$$k$N$G!"$"$J$?<+?H\e(B
+\e$B$N$?$a$N80$N@8@.$N$7$+$?$O!"$=$l$K>y$j$^$9!#\e(B
+
+\e$B$b$7$"$J$?$,8E$$\e(B PGP 2.x \e$B$N80$r\e(B GnuPG \e$B$KM"F~$7$F$"$C$F!"\e(BPGP 2.x \e$B$r;H$C$F\e(B
+\e$B$$$kAj<j$K=pL>$5$l$+$D0E9f2=$5$l$?%a%C%;!<%8$rAw$j$?$$$H$9$k$H!"<u?.<T$O\e(B
+\e$B$"$J$?$,Aw?.$7$?$b$N$rM}2r$G$-$J$$$3$H$rH/8+$9$k$3$H$K$J$k$G$7$g$&!#0l$D\e(B
+\e$B$N2r$O!"Be$o$j$K\e(B PGP 2.x \e$B$r;H$&$3$H\e(B (\e$B$9$J$o$A!"$b$7\e(B @code{pgg} \e$B$r;H$C$F\e(B
+\e$B$$$k$N$G$"$l$P!"\e(B@code{pgg-default-scheme} \e$B$r\e(B @code{pgp} \e$B$K@_Dj$9$k$3\e(B
+\e$B$H\e(B) \e$B$G$9!#\e(BGnuPG \e$B$r;H$$$?$/$J$$$N$G$"$l$P!"\e(B@code{gpg-2comp} \e$B$H$$$&8_49@-\e(B
+\e$B$,$"$k%9%/%j%W%H\e(B
+\e$B$r\e(B @uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/} \e$B$rF~<j\e(B
+\e$B$7$F!";H$&$3$H$,$G$-$^$9!#\e(BPGP 2.x \e$B$r;H$C$F$$$kAj<j$N?M$K!"\e(BGnuPG \e$B$K>h$j49\e(B
+\e$B$($k$3$H$rG<F@$5$;$k$3$H$b$G$-$k$G$7$g$&!#\e(B
@vindex mml-signencrypt-style-alist
-As a final workaround, you can make the sign and encryption work in
-two steps; separately sign, then encrypt a message. If you would like
-to change this behavior you can customize the
-@code{mml-signencrypt-style-alist} variable. For example:
+\e$B:G8e$NBeBX<jCJ$H$7$F!"=pL>$H0E9f2=$NF0:n$rFsCJ3,\e(B (\e$BJ,N%=pL>$7$F$+$i%a%C%;!<\e(B
+\e$B%8$r0E9f2=$9$k\e(B) \e$B$K$9$k$3$H$,$G$-$^$9!#$3$N?6$kIq$$$rJQ99$7$?$$$N$G$"$l$P!"\e(B
+@code{mml-signencrypt-style-alist} \e$BJQ?t$r%+%9%?%^%$%:$9$k$3$H$,$G$-$^$9!#\e(B
+\e$BNc$($P\e(B:
@lisp
(setq mml-signencrypt-style-alist '(("smime" separate)
("pgpmime" separate)))
@end lisp
-This causes to sign and encrypt in two passes, thus generating a
-message that can be understood by PGP version 2.
+\e$B$3$l$O=pL>$H0E9f2=$rFs%Q%9$G9T$J$o$;$k$3$H$K$h$C$F!"\e(BPGP version 2 \e$B$,M}2r\e(B
+\e$B$G$-$k%a%C%;!<%8$N@8@.$r$b$?$i$7$^$9!#\e(B
-(Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more
-information about the problem.)
+(\e$B$=$NLdBj$K4X$9$k$5$i$J$k>pJs$K$D$$$F!"\e(B
+@uref{http://www.gnupg.org/gph/en/pgp2x.html} \e$B$r;2>H$7$F2<$5$$!#\e(B)
@node Various Commands
@section \e$B$$$m$$$m$JL?Na\e(B
@section \e$B$$$m$$$m$J%a%C%;!<%8JQ?t\e(B
@table @code
-@c TRANSLATEME
@item message-default-charset
@vindex message-default-charset
@cindex charset
-Symbol naming a @acronym{MIME} charset. Non-@acronym{ASCII}
-characters in messages are assumed to be encoded using this charset.
-The default is @code{nil}, which means ask the user. (This variable
-is used only on non-@sc{mule} Emacsen. @xref{Charset Translation, ,
-Charset Translation, emacs-mime-ja, Emacs MIME Manual}, for details on
-the @sc{mule}-to-@acronym{MIME} translation process.
+@acronym{MIME} \e$BJ8;z%;%C%HL>$N%7%s%\%k!#%a%C%;!<%8Fb$N\e(B
+\e$BHs\e(B-@acronym{ASCII} \e$BJ8;z$O!"$3$NJ8;z%;%C%H$r;H$C$F%(%s%3!<%I$5$l$k$b$N$H\e(B
+\e$B2>Dj$7$^$9!#=i4|CM$O\e(B @code{nil} \e$B$G!"%f!<%6$K?R$M$k$3$H$r0UL#$7$^$9!#\e(B(\e$B$3\e(B
+\e$B$NJQ?t$OHs\e(B-@sc{mule} \e$B$J\e(B Emacs \e$B$G$N$_;H$o$l$^$9!#\e(B@sc{mule} \e$B$+\e(B
+\e$B$i\e(B @acronym{MIME} \e$B$X$NCV$-49$(=hM}$N>\:Y$O\e(B @xref{Charset Translation, ,
+Charset Translation, emacs-mime-ja, Emacs MIME Manual}, \e$B$r;2>H$7$F2<$5\e(B
+\e$B$$!#\e(B)
@item message-signature-separator
@vindex message-signature-separator
projects / elisp / gnus-doc-ja.git / commitdiff