[lldb-dev] [Bug 30251] New: ioctl for request TIOCGWINSZ on STDOUT_FILENO not working on OS X

2016-09-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=30251 Bug ID: 30251 Summary: ioctl for request TIOCGWINSZ on STDOUT_FILENO not working on OS X Product: lldb Version: unspecified Hardware: Macintosh OS: MacOS X

Re: [lldb-dev] [cfe-dev] [Release-testers] [3.9 Release] 'final' has been tagged

2016-09-01 Thread Renato Golin via lldb-dev
ARM and AArch64 green, uploaded. Thanks! $ sha1sum clang+llvm-3.9.0-aarch64-linux-gnu.tar.xz e9bfdf32c869e8fb344ef1b386c5d2b44ccac056 $ sha1sum clang+llvm-3.9.0-armv7a-linux-gnueabihf.tar.xz 2ad7a7b226b78d5c13ef06abb96da7a0fb8d535e --renato On 2 September 2016 at 01:38, Ben Pope via cfe-dev wr

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread René J . V . Bertin via lldb-dev
On Thursday September 01 2016 10:55:50 Jim Ingham wrote: >You don't have to reboot after every attempt to sign an executable. You only >have to reboot after making the code signing identity and, doing the little >command line trick to get the system to accept it. That still seems >necessary,

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread Jim Ingham via lldb-dev
> On Sep 1, 2016, at 2:01 AM, René J.V. Bertin via lldb-dev > wrote: > > Hi, > > MacPorts has long had ports for llvm and clang which are very practical. > Ports for lldb have been missing until now, so I've been trying to create one > based on the existing clang port. That wasn't particular

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread René J . V . Bertin via lldb-dev
On Thursday September 01 2016 13:44:36 René J.V. Bertin wrote: Here's a thought for the code-signing.txt document, following suggestions at https://sourceware.org/gdb/wiki/BuildingOnDarwin : Try a `killall -1 taskgated` before attempting a reboot. Wait a bit and then do `ps -axlww | fgrep taskg

Re: [lldb-dev] [Release-testers] [3.9 Release] 'final' has been tagged

2016-09-01 Thread Dimitry Andric via lldb-dev
On 01 Sep 2016, at 01:49, Hans Wennborg via Release-testers wrote: > > The final version of 3.9.0 was just tagged (from the 3.9 branch at > r280312). There were no changes after rc3. This took a little longer > than expected, but on the up side that means it's had more time to be > tested. Buil

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread René J . V . Bertin via lldb-dev
> Don't forget that the debugger can attach to an already running > processes as well. without setuid, it could presumably attach only to > own processes, but if it's running as root... Good catch, you're right (on OS X, haven't tried on Linux yet). R.

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread Pavel Labath via lldb-dev
On 1 September 2016 at 11:37, René J.V. Bertin wrote: > On Thursday September 01 2016 10:14:16 Pavel Labath wrote: > >> security safeguards on osx (there certainly aren't any on linux), but > > There's the codesigning bit. But that's just more a nuisance than a real > protection, from what I can

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread René J . V . Bertin via lldb-dev
On Thursday September 01 2016 10:14:16 Pavel Labath wrote: > security safeguards on osx (there certainly aren't any on linux), but There's the codesigning bit. But that's just more a nuisance than a real protection, from what I can tell, at least against code you build and install yourself. >

Re: [lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread Pavel Labath via lldb-dev
On 1 September 2016 at 10:01, René J.V. Bertin via lldb-dev wrote: > - does the debugserver application do anything which makes it a really bad > idea to make it SETUID root? It listens on a tcp connection, and takes control of random applications. debugserver is the ultimate remote code execut

[lldb-dev] [OS X] debugserver SETUID root?

2016-09-01 Thread René J . V . Bertin via lldb-dev
Hi, MacPorts has long had ports for llvm and clang which are very practical. Ports for lldb have been missing until now, so I've been trying to create one based on the existing clang port. That wasn't particularly difficult, except (who'd guess) for the codesigning bit. Two questions: - to w