This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [1.7] rebaseall doesn't solve the problem

On Feb 28 13:47, Charles Wilson wrote:
> Corinna Vinschen wrote:
> > Way cool, Chuck.  Especially the fact that this tool can also mark
> > executables with the TS-aware flag (doesn't make sense for DLLs, afaik).
> > This helps to test if setting this flag in Cygwin binaries will
> > allow Cygwin to run on 2008 with TS without disabling DEP.
> Well, the tool would need a little tweaking I think. Right now it skips
> any image (DLL or exe) that does not contain relocations.

Uh, ok.  In that case, yes, it needs some tweaking.  Actually, maybe
the tool should really be named differently.  Something suggesting
that it in general changes Win32-related PE/COFF header flags.  ASLR
and TS-aware are just some of them, in theory.

> > If so, I'm wondering if setting the TS-aware flag shouldn't become
> > default in GCC.  What do you say, Dave?  Would that be possible?
> I'd probably wait on that for the /next/ release (e.g. after 4.3.2-2),
> so we can get aslr integerated into rebase, and the rebaseall changes
> tested.  

Yes, sure.  I have to test if the TS-aware flag makes any difference on
a 2K8 TS machine anyway.  I think (and hope) that this flag will
persuade tsappcmp.dll into igoring an executable instead of scrambling
its page executable protection flags.  If so, we should really set this
flag in all applications.  Well, not that I gave up the idea that
Microsoft should fix that bug in tsappcmp.dll in the first place...

> Should I also add a switch to rebaseall that means: ONLY alsr,
> NO rebasing.  There's already a flag that allows you to add .exe's to
> the "rebase" list -- but you can't remove dll's and .so's from the list.

Makes sense to me.

> > That would also allow to drop the ugly TS hack I added to Cygwin 1.7.
> > All newly built binaries would have the flag set already, and older
> > binaries could be tweaked with the aslr utility.
> That would be nice.  However, ONLY exe's linked with cygwin1.dll should
> be marked this way, right?  Not cygcheck, strace, and whatever other few
> exes we might find in the cygwin installation lists.

Hmm, I'm not sure about that one.  At least only EXEs should be marked
TS-aware automatically.  The flag has no meaning on DLLs, afaik.
*Iff* the TS-aware flag helps to avoid tsappcmp.dll entirely, it's a big
help in all cases.  Cygwin applications are TS-aware by default anyway.
If somebody actually manages to write a non-TS-aware Cygwin application,
I'd say this guy should reset the TS-aware flag manually.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]