⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 auth.c

📁 PostgreSQL 8.1.4的源码 适用于Linux下的开源数据库系统
💻 C
📖 第 1 页 / 共 2 页
字号:
/*------------------------------------------------------------------------- * * auth.c *	  Routines to handle network authentication * * Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group * Portions Copyright (c) 1994, Regents of the University of California * * * IDENTIFICATION *	  $PostgreSQL: pgsql/src/backend/libpq/auth.c,v 1.132.2.1 2005/11/22 18:23:09 momjian Exp $ * *------------------------------------------------------------------------- */#include "postgres.h"#include <sys/param.h>#include <sys/socket.h>#if defined(HAVE_STRUCT_CMSGCRED) || defined(HAVE_STRUCT_FCRED) || defined(HAVE_STRUCT_SOCKCRED)#include <sys/uio.h>#include <sys/ucred.h>#include <errno.h>#endif#include <netinet/in.h>#include <arpa/inet.h>#include "libpq/auth.h"#include "libpq/crypt.h"#include "libpq/hba.h"#include "libpq/libpq.h"#include "libpq/pqcomm.h"#include "libpq/pqformat.h"#include "miscadmin.h"#include "storage/ipc.h"static void sendAuthRequest(Port *port, AuthRequest areq);static void auth_failed(Port *port, int status);static char *recv_password_packet(Port *port);static int	recv_and_check_password_packet(Port *port);char	   *pg_krb_server_keyfile;char	   *pg_krb_srvnam;bool		pg_krb_caseins_users;char	   *pg_krb_server_hostname = NULL;#ifdef USE_PAM#ifdef HAVE_PAM_PAM_APPL_H#include <pam/pam_appl.h>#endif#ifdef HAVE_SECURITY_PAM_APPL_H#include <security/pam_appl.h>#endif#define PGSQL_PAM_SERVICE "postgresql"	/* Service name passed to PAM */static int	CheckPAMAuth(Port *port, char *user, char *password);static int pam_passwd_conv_proc(int num_msg, const struct pam_message ** msg,					 struct pam_response ** resp, void *appdata_ptr);static struct pam_conv pam_passw_conv = {	&pam_passwd_conv_proc,	NULL};static char *pam_passwd = NULL; /* Workaround for Solaris 2.6 brokenness */static Port *pam_port_cludge;	/* Workaround for passing "Port *port" into								 * pam_passwd_conv_proc */#endif   /* USE_PAM */#ifdef KRB5/*---------------------------------------------------------------- * MIT Kerberos authentication system - protocol version 5 *---------------------------------------------------------------- */#include <krb5.h>/* Some old versions of Kerberos do not include <com_err.h> in <krb5.h> */#if !defined(__COM_ERR_H) && !defined(__COM_ERR_H__)#include <com_err.h>#endif/* * pg_an_to_ln -- return the local name corresponding to an authentication *				  name * * XXX Assumes that the first aname component is the user name.  This is NOT *	   necessarily so, since an aname can actually be something out of your *	   worst X.400 nightmare, like *		  ORGANIZATION=U. C. Berkeley/NAME=Paul M. Aoki@CS.BERKELEY.EDU *	   Note that the MIT an_to_ln code does the same thing if you don't *	   provide an aname mapping database...it may be a better idea to use *	   krb5_an_to_ln, except that it punts if multiple components are found, *	   and we can't afford to punt. */static char *pg_an_to_ln(char *aname){	char	   *p;	if ((p = strchr(aname, '/')) || (p = strchr(aname, '@')))		*p = '\0';	return aname;}/* * Various krb5 state which is not connection specfic, and a flag to * indicate whether we have initialised it yet. */static int	pg_krb5_initialised;static krb5_context pg_krb5_context;static krb5_keytab pg_krb5_keytab;static krb5_principal pg_krb5_server;static intpg_krb5_init(void){	krb5_error_code retval;	char	   *khostname;	if (pg_krb5_initialised)		return STATUS_OK;	retval = krb5_init_context(&pg_krb5_context);	if (retval)	{		ereport(LOG,				(errmsg("Kerberos initialization returned error %d",						retval)));		com_err("postgres", retval, "while initializing krb5");		return STATUS_ERROR;	}	retval = krb5_kt_resolve(pg_krb5_context, pg_krb_server_keyfile, &pg_krb5_keytab);	if (retval)	{		ereport(LOG,				(errmsg("Kerberos keytab resolving returned error %d",						retval)));		com_err("postgres", retval, "while resolving keytab file \"%s\"",				pg_krb_server_keyfile);		krb5_free_context(pg_krb5_context);		return STATUS_ERROR;	}	/*	 * If no hostname was specified, pg_krb_server_hostname is already NULL.	 * If it's set to blank, force it to NULL.	 */	khostname = pg_krb_server_hostname;	if (khostname && khostname[0] == '\0')		khostname = NULL;	retval = krb5_sname_to_principal(pg_krb5_context,									 khostname,									 pg_krb_srvnam,									 KRB5_NT_SRV_HST,									 &pg_krb5_server);	if (retval)	{		ereport(LOG,				(errmsg("Kerberos sname_to_principal(\"%s\", \"%s\") returned error %d",		 khostname ? khostname : "server hostname", pg_krb_srvnam, retval)));		com_err("postgres", retval,		"while getting server principal for server \"%s\" for service \"%s\"",				khostname ? khostname : "server hostname", pg_krb_srvnam);		krb5_kt_close(pg_krb5_context, pg_krb5_keytab);		krb5_free_context(pg_krb5_context);		return STATUS_ERROR;	}	pg_krb5_initialised = 1;	return STATUS_OK;}/* * pg_krb5_recvauth -- server routine to receive authentication information *					   from the client * * We still need to compare the username obtained from the client's setup * packet to the authenticated name. * * We have our own keytab file because postgres is unlikely to run as root, * and so cannot read the default keytab. */static intpg_krb5_recvauth(Port *port){	krb5_error_code retval;	int			ret;	krb5_auth_context auth_context = NULL;	krb5_ticket *ticket;	char	   *kusername;	ret = pg_krb5_init();	if (ret != STATUS_OK)		return ret;	retval = krb5_recvauth(pg_krb5_context, &auth_context,						   (krb5_pointer) & port->sock, pg_krb_srvnam,						   pg_krb5_server, 0, pg_krb5_keytab, &ticket);	if (retval)	{		ereport(LOG,				(errmsg("Kerberos recvauth returned error %d",						retval)));		com_err("postgres", retval, "from krb5_recvauth");		return STATUS_ERROR;	}	/*	 * The "client" structure comes out of the ticket and is therefore	 * authenticated.  Use it to check the username obtained from the	 * postmaster startup packet.	 *	 * I have no idea why this is considered necessary.	 */#if defined(HAVE_KRB5_TICKET_ENC_PART2)	retval = krb5_unparse_name(pg_krb5_context,							   ticket->enc_part2->client, &kusername);#elif defined(HAVE_KRB5_TICKET_CLIENT)	retval = krb5_unparse_name(pg_krb5_context,							   ticket->client, &kusername);#else#error "bogus configuration"#endif	if (retval)	{		ereport(LOG,				(errmsg("Kerberos unparse_name returned error %d",						retval)));		com_err("postgres", retval, "while unparsing client name");		krb5_free_ticket(pg_krb5_context, ticket);		krb5_auth_con_free(pg_krb5_context, auth_context);		return STATUS_ERROR;	}	kusername = pg_an_to_ln(kusername);	if (pg_krb_caseins_users)		ret = pg_strncasecmp(port->user_name, kusername, SM_DATABASE_USER);	else		ret = strncmp(port->user_name, kusername, SM_DATABASE_USER);	if (ret)	{		ereport(LOG,				(errmsg("unexpected Kerberos user name received from client (received \"%s\", expected \"%s\")",						port->user_name, kusername)));		ret = STATUS_ERROR;	}	else		ret = STATUS_OK;	krb5_free_ticket(pg_krb5_context, ticket);	krb5_auth_con_free(pg_krb5_context, auth_context);	free(kusername);	return ret;}#elsestatic intpg_krb5_recvauth(Port *port){	ereport(LOG,			(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),			 errmsg("Kerberos 5 not implemented on this server")));	return STATUS_ERROR;}#endif   /* KRB5 *//* * Tell the user the authentication failed, but not (much about) why. * * There is a tradeoff here between security concerns and making life * unnecessarily difficult for legitimate users.  We would not, for example, * want to report the password we were expecting to receive... * But it seems useful to report the username and authorization method * in use, and these are items that must be presumed known to an attacker * anyway. * Note that many sorts of failure report additional information in the * postmaster log, which we hope is only readable by good guys. */static voidauth_failed(Port *port, int status){	const char *errstr;	/*	 * If we failed due to EOF from client, just quit; there's no point in	 * trying to send a message to the client, and not much point in logging	 * the failure in the postmaster log.  (Logging the failure might be	 * desirable, were it not for the fact that libpq closes the connection	 * unceremoniously if challenged for a password when it hasn't got one to	 * send.  We'll get a useless log entry for every psql connection under	 * password auth, even if it's perfectly successful, if we log STATUS_EOF	 * events.)	 */	if (status == STATUS_EOF)		proc_exit(0);	switch (port->auth_method)	{		case uaReject:			errstr = gettext_noop("authentication failed for user \"%s\": host rejected");			break;		case uaKrb5:			errstr = gettext_noop("Kerberos 5 authentication failed for user \"%s\"");			break;		case uaTrust:			errstr = gettext_noop("\"trust\" authentication failed for user \"%s\"");			break;		case uaIdent:			errstr = gettext_noop("Ident authentication failed for user \"%s\"");			break;		case uaMD5:		case uaCrypt:		case uaPassword:			errstr = gettext_noop("password authentication failed for user \"%s\"");			break;#ifdef USE_PAM		case uaPAM:			errstr = gettext_noop("PAM authentication failed for user \"%s\"");			break;#endif   /* USE_PAM */		default:			errstr = gettext_noop("authentication failed for user \"%s\": invalid authentication method");			break;	}	ereport(FATAL,			(errcode(ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION),			 errmsg(errstr, port->user_name)));	/* doesn't return */}/* * Client authentication starts here.  If there is an error, this * function does not return and the backend process is terminated. */voidClientAuthentication(Port *port){	int			status = STATUS_ERROR;	/*	 * Get the authentication method to use for this frontend/database	 * combination.  Note: a failure return indicates a problem with the hba	 * config file, not with the request.  hba.c should have dropped an error	 * message into the postmaster logfile if it failed.	 */	if (hba_getauthmethod(port) != STATUS_OK)		ereport(FATAL,				(errcode(ERRCODE_CONFIG_FILE_ERROR),				 errmsg("missing or erroneous pg_hba.conf file"),				 errhint("See server log for details.")));	switch (port->auth_method)	{		case uaReject:			/*			 * This could have come from an explicit "reject" entry in			 * pg_hba.conf, but more likely it means there was no matching			 * entry.  Take pity on the poor user and issue a helpful error			 * message.  NOTE: this is not a security breach, because all the			 * info reported here is known at the frontend and must be assumed			 * known to bad guys. We're merely helping out the less clueful			 * good guys.			 */			{				char		hostinfo[NI_MAXHOST];				pg_getnameinfo_all(&port->raddr.addr, port->raddr.salen,								   hostinfo, sizeof(hostinfo),								   NULL, 0,								   NI_NUMERICHOST);#ifdef USE_SSL

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -