mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Re: A running list of questions from "porting" Slackware to musl
Date: Wed, 1 Oct 2014 09:48:17 +0200	[thread overview]
Message-ID: <20141001074817.GL21835@port70.net> (raw)
In-Reply-To: <542B41C4.1040701@amacapital.net>

* Andy Lutomirski <luto@amacapital.net> [2014-09-30 16:50:28 -0700]:
> On 09/30/2014 08:50 AM, Rich Felker wrote:
> > When gcc generates the canary-check code, on failure it normally
> > calls/jumps to __stack_chk_fail. But for shared libraries, that call
> > would go to a thunk in the library's PLT, which depends on the GOT
> > register being initialized (actually this varies by arch; x86_64
...
> 
> On x86_64, this would be call *whatever@gotoff(%rip) instead of call
> whatever@plt.
> 
> (Even better: the loader could patch the PLT with a direct jump.  Could
...

hm this seems to be a lot of complication just to crash

if gcc had a -fcrash-on-ssp-chk-fail flag that simply generated
a crash instruction that would be simpler/smaller/more secure

(actually i think that should be the default behaviour)


  parent reply	other threads:[~2014-10-01  7:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 12:43 Weldon Goree
2014-09-30 14:59 ` stephen Turner
2014-09-30 16:20   ` Weldon Goree
2014-09-30 15:32 ` Isaac Dunham
2014-09-30 15:50   ` Rich Felker
2014-09-30 23:50     ` Andy Lutomirski
2014-10-01  0:05       ` Rich Felker
2014-10-01  5:49         ` Andy Lutomirski
2014-10-01 13:29           ` Rich Felker
2014-10-01 15:00             ` Andy Lutomirski
2014-10-01  7:48       ` Szabolcs Nagy [this message]
2014-10-01  8:19         ` u-wsnj
2014-10-01 13:30         ` Rich Felker
2014-09-30 15:46 ` Rich Felker
2014-09-30 16:05   ` Weldon Goree
2014-10-01  6:29 ` Timo Teras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141001074817.GL21835@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).