Thank you for the suggestion.
When I do like make CC=/path/to/fipsld FIPSLD_CC=/point/to/gcc
It gave out
/bin/sh: warning: shell level (1000) too high, resetting to 1
then putty exit.
At 2019-11-27 13:16:51, "Pankaj Sarode" wrote:
Hi,
You will need to pass your native compiler i.e gcc to
Unless buffer is a char* instead of a char[] in which case its completely
wrong. A very common case among buggy C code.
On Wed, Nov 27, 2019 at 7:09 AM Phillip Susi wrote:
>
> Michael Wojcik writes:
>
> > Some C experts have argued that the length-checking versions of the
> library
> From: Phillip Susi
> > Michael Wojcik writes:
> > Some C experts have argued that the length-checking versions of the library
> > functions, either the C90
> > ones such as strncat or the Appendix K ones, are essentially pointless
> > anyway; that the caller needs to
> > handle truncation
On Tue, 2019-11-26 at 23:47 +, Jordan Brown wrote:
> Here's a paper on the subject:
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm
I love the fact that the "correct and safe" example they give in
"Unnecessary Uses" is neither correct nor safe (it has a potential DOS due
to
Michael Wojcik writes:
> Some C experts have argued that the length-checking versions of the library
> functions, either the C90 ones such as strncat or the Appendix K ones, are
> essentially pointless anyway; that the caller needs to handle truncation and
> so ought to know whether
On 27/11/2019 11:07, shiva kumar wrote:
> but still the update is going on in the GitHub repository for 102
> branch, is that mean there will be a release by end of this year?
There are no commits against the 1.0.2 branch that would qualify for a
CVE - they are all relatively minor commits.
but still the update is going on in the GitHub repository for 102 branch,
is that mean there will be a release by end of this year?
On Tue, Nov 26, 2019 at 6:31 PM Matt Caswell wrote:
>
>
> On 26/11/2019 11:38, shiva kumar wrote:
> > Hi,
> > As we know that OpenSSL 1.0.2 support will end in
