Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

Mike Perry: > We want to do this for MacOSX as well. Does anyone happen to know if we can > use otool in some way to remove these LC_CODE_SIGNATURE sections easily, > and get the same exact binary as before signing? I don't know if it helps in the case but problem can also be approached the other

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

teor: > > On 27 Oct 2015, at 05:41, Conrad Kramer wrote: > > >> On Oct 26, 2015, at 11:22 AM, Spencer wrote: > >> > >> Hi, > >> > >>> Conrad Kramer: > >>> All resources in a bundle (e.g. an app or framework) are > >>> signed and the

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

Ian Goldberg: > On Mon, Oct 26, 2015 at 06:06:36AM -0700, Mike Perry wrote: >> Essentially, codesign only touches executable binaries in the .app (see >> that second link for info on how the binary's segments get moved around) >> and also adds an SC_Info directory for codesign/DRM metadata. > >

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On 27 Oct 2015, at 20:27, Nima Fatemi wrote: > > Ian Goldberg: >> On Mon, Oct 26, 2015 at 06:06:36AM -0700, Mike Perry wrote: >>> Essentially, codesign only touches executable binaries in the .app (see >>> that second link for info on how the binary's segments get moved

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On 27 Oct 2015, at 21:13, Lunar wrote: > > Mike Perry: >> We want to do this for MacOSX as well. Does anyone happen to know if we can >> use otool in some way to remove these LC_CODE_SIGNATURE sections easily, >> and get the same exact binary as before signing? > > I

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

Tim Wilson-Brown - teor: > > > On 27 Oct 2015, at 20:06, Mike Perry wrote: > > > > teor: > >> > >> On 27 Oct 2015, at 05:41, Conrad Kramer wrote: > >> > On Oct 26, 2015, at 11:22 AM, Spencer wrote: > >

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On Oct 27, 2015, at 5:32 AM, Mike Perry wrote: > > Tim Wilson-Brown - teor: >> >>> On 27 Oct 2015, at 20:06, Mike Perry wrote: >>> >>> teor: On 27 Oct 2015, at 05:41, Conrad Kramer wrote: >> On

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On Oct 27, 2015, at 3:03 PM, Conrad Kramer wrote: > >> >> On Oct 27, 2015, at 5:32 AM, Mike Perry wrote: >> >> Tim Wilson-Brown - teor: >>> On 27 Oct 2015, at 20:06, Mike Perry wrote: teor: >

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

On 27 Oct 2015, at 05:41, Conrad Kramer wrote: >> On Oct 26, 2015, at 11:22 AM, Spencer wrote: >> >> Hi, >> >>> Conrad Kramer: >>> All resources in a bundle (e.g. an app or framework) are >>> signed and the signatures are stored in a file

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On Oct 26, 2015, at 11:22 AM, Spencer wrote: > > Hi, > >> Conrad Kramer: >> All resources in a bundle (e.g. an app or framework) are >> signed and the signatures are stored in a file named "CodeResources”: > > Then what is in 'CodeSignature', Apple's signing

[tor-dev] [FWD: Re: Apple developer account + codesigning]

Here is some info about OSX codesigning, courtesy of Mike Tigas. It sounds like undoing the codesigning to verify build (and signing machine) integrity will be tricky. If anyone has more info on how to do that, it would be appreciated. - Forwarded message from Mike Tigas -

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

> On Oct 26, 2015, at 10:23 AM, Ian Goldberg wrote: > > On Mon, Oct 26, 2015 at 06:06:36AM -0700, Mike Perry wrote: >> Essentially, codesign only touches executable binaries in the .app (see >> that second link for info on how the binary's segments get moved around) >> and

Re: [tor-dev] [FWD: Re: Apple developer account + codesigning]

On Mon, Oct 26, 2015 at 06:06:36AM -0700, Mike Perry wrote: > Essentially, codesign only touches executable binaries in the .app (see > that second link for info on how the binary's segments get moved around) > and also adds an SC_Info directory for codesign/DRM metadata. Wait; does that mean

[tor-dev] [FWD: Re: Apple developer account + codesigning]

Hi, Conrad Kramer: All resources in a bundle (e.g. an app or framework) are signed and the signatures are stored in a file named "CodeResources”: Then what is in 'CodeSignature', Apple's signing stuff? Wordlife, Spencer ___ tor-dev mailing list