Re: code-signing (log message and potential "fixes")

2016-05-21 Thread Brandon Allbery
On Sat, May 21, 2016 at 8:01 PM, Bradley Giesbrecht wrote: > OpenSSL might be able to accomplish the same task and it is possible with > OpenSSL to write a config file that fills in all the required fields. Port > could write such a config per user. OpenSSL can certainly create the signing cert

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread Bradley Giesbrecht
> On May 21, 2016, at 4:33 PM, Rainer Müller wrote: > > On 05/21/2016 04:33 PM, René J.V. Bertin wrote: >> ..., >> wouldn't it be possible to design an interface that allows users to specify >> an identity in macports.conf, and ports to invoke codesign in the >> post-activate stage? > > Yes, of

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread Rainer Müller
On 05/21/2016 04:33 PM, René J.V. Bertin wrote: > ..., > wouldn't it be possible to design an interface that allows users to specify > an identity in macports.conf, and ports to invoke codesign in the > post-activate stage? Yes, of course. This would be the way to implement code-signing. When prev

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread René J . V . Bertin
On Saturday May 21 2016 12:54:00 Brandon Allbery wrote: > That reference was old enough that it is probably something else now. I can It would seem that /etc/authorization was deprecated in Feb. 2014 on my machine, which IIRC corresponds to the epoch where I upgraded from 10.6 to 10.9 . The use

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread Brandon Allbery
That reference was old enough that it is probably something else now. I can dig deeper, I guess; I don't actually know much about the internals aside from various failure cases I've run across while trying to decipher weirdness on my machines. (and until recently I was on 10.9 so paid less attentio

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread René J . V . Bertin
On Saturday May 21 2016 11:02:58 Brandon Allbery wrote: > invalid. This can be as simple as /private/etc/authorization being corrupt Should I have that file (on 10.9)? I only have 1660406 48 -rw-r--r-- 1 root wheel 47369 Feb 14 2014 /etc/authorization.deprecated 1660407 24 -rw-r--r-- 1 root wh

Re: code-signing (log message and potential "fixes")

2016-05-21 Thread Brandon Allbery
On Sat, May 21, 2016 at 10:33 AM, René J.V. wrote: > May 21 16:20:08 Portia kernel[0]: CODE SIGNING: > cs_invalid_page(0x105ead000): p=98132[kioslave] final status 0x0, allowing > (remove VALID) page So what I'm seeing is that this indicates that something is corrupted and making the kernel thi

code-signing (log message and potential "fixes")

2016-05-21 Thread René J . V . Bertin
Hi, I'm seeing messages like the one below, with a certain regularity: May 21 16:20:08 Portia kernel[0]: CODE SIGNING: cs_invalid_page(0x105ead000): p=98132[kioslave] final status 0x0, allowing (remove VALID) page kioslave is a KDE4 or KF5 application, which can be used for lots of things incl