[Pidgin] #15290: Compile everything with secure flags

Pidgin trac at pidgin.im
Wed Sep 26 19:04:02 EDT 2012


#15290: Compile everything with secure flags
-------------------------------------+------------------------------
 Reporter:  DrWhax                   |       Owner:  datallah
     Type:  defect                   |      Status:  closed
Milestone:  2.10.7                   |   Component:  winpidgin (gtk)
  Version:  2.10.6                   |  Resolution:  fixed
 Keywords:  security aslr dep build  |
-------------------------------------+------------------------------

Comment (by datallah):

 Replying to [comment:13 noloader]:
 > Replying to [comment:12 datallah]:
 > > These changes make our crash reporting stack traces useless (I assume
 it is the ASLR that is problematic).  I'm not sure if there's going to be
 an easy way to fix that.
 > Hmmm... I've never heard that one (I'm not being a smart ass).
 Optimizations and stripping symbols usually causes this problem. What is
 Pidgin using for crash reporting?

 The only compiler changes are the the additions to `CC_HARDENING_OPTIONS`
 and the linker changes are `LD_HARDENING_OPTIONS` in [d9ebf57cd361].
 The way things are being stripped hasn't changed either.

 We're using a [https://hg.pidgin.im/util/drmingw/ forked version] of the
 drmingw `exchndl.dll` which uses the binutils bfd library to get at the
 debug symbols.

 If there were something better, we'd be happy to use it.

-- 
Ticket URL: <https://developer.pidgin.im/ticket/15290#comment:14>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list