All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] crypt.3: ATTRIBUTES: Note function that is not thread-safe
Date: Sat, 18 May 2013 20:08:18 +0200	[thread overview]
Message-ID: <5197C392.2040302@gmail.com> (raw)
In-Reply-To: <1367827391-3564-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

On 05/06/13 10:03, Peng Haitao wrote:
> The function crypt() is not thread safe.


Applied to my local branch for this work.

Thank you, Peng.

Cheers,

Michael


> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/crypt.3 | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/man3/crypt.3 b/man3/crypt.3
> index ca52b92..ed02440 100644
> --- a/man3/crypt.3
> +++ b/man3/crypt.3
> @@ -160,6 +160,15 @@ function was not implemented, probably because of U.S.A. export restrictions.
>  .\" .PP
>  .\" Making encrypted data computed using crypt() publicly available has
>  .\" to be considered insecure for the given reasons.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR crypt ()
> +function is not thread-safe.
> +.LP
> +The
> +.BR crypt_r ()
> +function is thread-safe.
>  .SH CONFORMING TO
>  .BR crypt ():
>  SVr4, 4.3BSD, POSIX.1-2001.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-05-18 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  8:03 [PATCH] crypt.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
     [not found] ` <1367827391-3564-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:08   ` Michael Kerrisk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5197C392.2040302@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.