mirror of
https://github.com/postgres/postgres.git
synced 2025-11-21 00:42:43 +03:00
Pre-beta mechanical code beautification.
Run pgindent, pgperltidy, and reformat-dat-files. This set of diffs is a bit larger than typical. We've updated to pg_bsd_indent 2.1.2, which properly indents variable declarations that have multi-line initialization expressions (the continuation lines are now indented one tab stop). We've also updated to perltidy version 20230309 and changed some of its settings, which reduces its desire to add whitespace to lines to make assignments etc. line up. Going forward, that should make for fewer random-seeming changes to existing code. Discussion: https://postgr.es/m/20230428092545.qfb3y5wcu4cm75ur@alvherre.pgsql
This commit is contained in:
@@ -1104,8 +1104,8 @@ prepare_cert_name(char *name)
|
||||
if (namelen > MAXLEN)
|
||||
{
|
||||
/*
|
||||
* Keep the end of the name, not the beginning, since the most specific
|
||||
* field is likely to give users the most information.
|
||||
* Keep the end of the name, not the beginning, since the most
|
||||
* specific field is likely to give users the most information.
|
||||
*/
|
||||
truncated = name + namelen - MAXLEN;
|
||||
truncated[0] = truncated[1] = truncated[2] = '.';
|
||||
@@ -1165,8 +1165,8 @@ verify_cb(int ok, X509_STORE_CTX *ctx)
|
||||
|
||||
/*
|
||||
* Get the Subject and Issuer for logging, but don't let maliciously
|
||||
* huge certs flood the logs, and don't reflect non-ASCII bytes into it
|
||||
* either.
|
||||
* huge certs flood the logs, and don't reflect non-ASCII bytes into
|
||||
* it either.
|
||||
*/
|
||||
subject = X509_NAME_to_cstring(X509_get_subject_name(cert));
|
||||
sub_prepared = prepare_cert_name(subject);
|
||||
|
||||
Reference in New Issue
Block a user