RE: realpath(3) et al

From: Devon H. O'Dell (dodell_at_sitetronics.com)
Date: 08/12/03

  • Next message: Kris Kennaway: "Re: realpath(3) et al" 
    To: "'Kris Kennaway'" <kris@obsecurity.org>, "'Jacques A. Vidrine'" <nectar@FreeBSD.org>, "'Jason Stone'" <freebsd-security@dfmm.org>, <security@freebsd.org>, <kris@FreeBSD.org>
Date: Tue, 12 Aug 2003 22:49:33 +0200

    If you guys are too busy for maintaining this port, shall I take on this
    burden?

    --Devon

    > -----Oorspronkelijk bericht-----
    > Van: Kris Kennaway [mailto:kris@obsecurity.org]
    > Verzonden: Tuesday, August 12, 2003 10:48 PM
    > Aan: Jacques A. Vidrine; Devon H. O'Dell; 'Jason Stone';
    > security@freebsd.org; kris@FreeBSD.org
    > Onderwerp: Re: realpath(3) et al
    >
    > On Tue, Aug 12, 2003 at 02:59:46PM -0500, Jacques A. Vidrine wrote:
    > > On Tue, Aug 12, 2003 at 01:59:51PM +0200, Devon H. O'Dell wrote:
    > > > In any case, IBM has a stack smashing protection patch for GCC 3.3 on
    > > > FreeBSD 4.8 available at
    > > > http://www.trl.ibm.com/projects/security/ssp/buildfreebsd.html (the
    > > > description page is at http://www.trl.ibm.com/projects/security/ssp/).
    > It
    > > > currently works in the latest cvsupped source from 5.1 as well (I've
    > built
    > > > and tested it).
    > >
    > > http://www.research.ibm.com/trl/projects/security/ssp/ has the latest.
    > > Yes, I'd like to see this in the base system as well. Our toolchain
    > > in 5.x is calming down a bit, maybe the timing is getting ripe.
    > >
    > > I thought Kris looked into this before, but I don't recall what might
    > > have ultimately stopped him from making the commits. cc:ing him in
    > > case he has insight to share.
    >
    > The gcc maintainer (David O'Brien at the time) was unwilling to
    > support the burden of an external gcc patch which would need to be
    > re-integrated by him each time a new gcc version was imported.
    >
    > Instead, we agreed that the best solution was to make a port that uses
    > this patch, which can be updated periodically as the SSP authors track
    > new gcc releases. Neither of us followed through on this though.
    >
    > Kris

    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"

  • Next message: Kris Kennaway: "Re: realpath(3) et al"

    Relevant Pages

    • Re: realpath(3) et al
      ... > in 5.x is calming down a bit, maybe the timing is getting ripe. ... > I thought Kris looked into this before, but I don't recall what might ... The gcc maintainer was unwilling to ... support the burden of an external gcc patch which would need to be ...
      (FreeBSD-Security)
    • Re: LPC900/80C51 Compiler Toolchain
      ... The reason for 2.7.2 was originally because it was a late enough revision for the 68k port to be stable and the whole suite was less cluttered by ports to other, ... Also, Tru64 unix wasn't supported as a target and some of the very late gcc and library versions wouldn't build at all, whereas earlier versions built fine. ... What gcc and open source in general have done is to make it possible for small shops. ... over open source developers - it is often easier to get restricted information from the microcontroller manufacturers. ...
      (comp.arch.embedded)
    • Re: New C++ standard
      ... Are anybody going to port new gcc test versions of C++ (with concepts ... The reason was broken DJGPP port of bash-2.05b. ... So I don't know whether these packages really work reasonably well for DJGPP. ...
      (comp.os.msdos.djgpp)
    • Re: port gcc for c51 step by step
      ... Just because a processor is not listed on the GCC website, it does not have to be the case that it is not already ported and actively maintained for GCC. ... E.g. the MIL-STD-1750A used to have a configuration in GCC supported by the Free Software Foundation, but even after it was culled from GNU.org it was still privately maintained in a commercial product. ... the msp430 port is a solid and port with strong development outside the official tree. ...
      (comp.arch.embedded)
    • Re: about the gcc 3.4.x problems
      ... In fact I had to wait two days because the system gcc commits were not ... This puny pentium2 finally finished compiling the lang/gcc34 port last night, ... It also seems like you don't use maillist archives to read-up ...
      (freebsd-current)