This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: inlining failed
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Dominik Táborský" <bremby at seznam dot cz>
- Cc: libc-help at sourceware dot org
- Date: Sat, 29 Nov 2008 17:14:47 -0500
- Subject: Re: inlining failed
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=dt/dHWgU4W64PPloO2EieSRxHBVBrJ68FogQZIM+rlw=; b=f6Vqsd83gGJxo+yupinxRAO8yZk6DejSjb0SMbJqh3XStzk20/Rc8380EC4qbySok3 E4MGOSMlRj74Zg8xjATR3VYaKshMhBNjCZIupLnOxEaPcWIEBYdfCs2uMSK78H/5URYS UiwgY/ecMeBINTcCtNfU13/qA7oXUok0Zjgys=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=J3ftrWFGnLgnBB06woyb+J+ae5oZkacf20GI4Gb9V5g/AfIT6MSJzIl5EPXoBpow/G h6guwAZHF3d2yKavN0vl6vmZVhUs/NcONUEqqZelFPyKZm9T9M27J6dmOijwVoEe1yPQ xmgC7H8yOGkm/RfFOdwo5EMj21g0ZAOGcBkqc=
- References: <1227974019.24048.32.camel@eddy> <119aab440811291319m2c2b3bcfjff877960d7cfe4a1@mail.gmail.com> <1227996558.7592.14.camel@eddy>
On Sat, Nov 29, 2008 at 5:09 PM, Dominik Táborský <bremby@seznam.cz> wrote:
> Now I don't know how to get over this.
> It seems to me Glibc is not very secured when I have to turn off stack
> protector and FORTIFY_SOURCE checks...
Do you have information to back up your claim that it is not secure?
Have you checked to see if the distros have patches against glibc to
make it build with these options?
Cheers,
Carlos.