Re: strncpy is not a safe version of strcpy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: strncpy is not a safe version of strcpy
Date
Msg-id 19174.1407939710@sss.pgh.pa.us
Whole thread Raw
In response to Re: strncpy is not a safe version of strcpy  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: strncpy is not a safe version of strcpy
Re: strncpy is not a safe version of strcpy
List pgsql-hackers
Kevin Grittner <kgrittn@ymail.com> writes:
> I am concerned that failure to check for truncation could allow
> deletion of unexpected files or directories.

I believe that we deal with this by the expedient of checking the lengths
of tablespace paths in advance, when the tablespace is created.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal for 9.5: monitoring lock time for slow queries
Next
From: Heikki Linnakangas
Date:
Subject: Re: strncpy is not a safe version of strcpy