Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

GETPASS(3)               BSD Library Functions Manual               GETPASS(3)

     getpass -- get a password

     Standard C Library (libc, -lc)

     #include <pwd.h>
     #include <unistd.h>

     char *
     getpass(const char *prompt);

     The getpass() function displays a prompt to, and reads in a password from, /dev/tty.  If this file is
     not accessible, getpass() displays the prompt on the standard error output and reads from the standard

     The password may be up to _PASSWORD_LEN (currently 128) characters in length.  Any additional charac-ters characters
     ters and the terminating newline character are discarded.

     The getpass() function turns off character echoing while reading the password.

     The getpass() function returns a pointer to the null terminated password.


     crypt(3), readpassphrase(3)

     A getpass() function appeared in Version 7 AT&T UNIX.

     The getpass() function leaves its result in an internal static object and returns a pointer to that
     object.  Subsequent calls to getpass() will modify the same object.

     The calling process should zero the password as soon as possible to avoid leaving the cleartext pass-word password
     word visible in the process's address space.

     Upon receipt of a SIGTSTP, the input buffer will be flushed, so any partially typed password must be
     retyped when the process continues.

BSD                              June 4, 1993                              BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.