On 12.01.2021 at 02:37 Ryan Schmidt wrote:
> The automatic codesigning that the compiler/linker does must be
> sufficient, because we're not doing anything beyond that with the
> binary packages that MacPorts downloads when you install a port.
Ok, that's good to hear. So the only benefit of
On Jan 11, 2021, at 07:27, Andreas Falkenhahn wrote:
> Slightly off-topic, but maybe someone here knows something about this: When
> distributing Apple ARM apps outside the App Store, is it sufficient to sign
> them using ad-hoc or self-signed certificates or is it mandatory now to pay
> the
Slightly off-topic, but maybe someone here knows something about this: When
distributing Apple ARM apps outside the App Store, is it sufficient to sign
them using ad-hoc or self-signed certificates or is it mandatory now to pay the
$99 per year even if the app is going to be distributed outside
> On 2020-09-29, at 15:02, Michael Dickens wrote:
>
> Excellent! Thanks for the heads-up. I've downloaded this file and will get it
> installed and start testing later today. - MLD
>
> On Tue, Sep 29, 2020, at 2:47 PM, Gary Palter wrote:
>> Apple today released Xcode 12.2 beta 2 and the
Excellent! Thanks for the heads-up. I've downloaded this file and will get it
installed and start testing later today. - MLD
On Tue, Sep 29, 2020, at 2:47 PM, Gary Palter wrote:
> Apple today released Xcode 12.2 beta 2 and the Release Notes state
>> Apple Clang Compiler
>> Resolved Issues
>>
Apple today released Xcode 12.2 beta 2 and the Release Notes state
> Apple Clang Compiler
> Resolved Issues
> Fixed an issue that caused strip, install_name_tool and vtool to corrupt the
> ad-hoc code signatures generated by the linker for arm64 Mach-O files.
> (51911417)
- Gary Palter
Let's try this again from my MP email so that it gets to lists ... sorry for
duplicate emails!
I've finally gotten to the point of working out a hack solution.
One can -not- modify '/usr/bin' without a lot of effort. But, one can modify
On Sep 24, 2020, at 08:51, Ruben Di Battista wrote:
> Ok, that's what I didn't know. I thought It was mandatory for Apple Store
> software and not everything...
Yup. As of macOS Big Sur 11 beta 6, released September 3, 2020, codesigning is
mandatory for everything on ARM Macs. How to
Ok, that's what I didn't know. I thought It was mandatory for Apple Store
software and not everything...
On Thu, 24 Sep 2020, 13:35 Ryan Schmidt, wrote:
> On Sep 23, 2020, at 03:37, Ruben Di Battista wrote:
>
> > Can't be an easier choice to push globally a linker switch, if it
> exists, to
On Sep 22, 2020, at 18:05, Richard L. Hamilton wrote:
> How will additional signing requirements impact MacPorts binary distribution
> (which is a huge timesaver for installs and updates, if one doesn't have to
> build most packages oneself)?
As I understand it, it should not affect that at
On Sep 22, 2020, at 17:24, Ken Cunningham wrote:
> On 2020-09-22, at 12:58 PM, Ryan Schmidt wrote:
>>
>> To me it seems unrealistic for Apple to suggest that an infinite number of
>> open source projects, many of whose developers have never seen a Mac, should
>> now add code to their build
On Sep 23, 2020, at 03:37, Ruben Di Battista wrote:
> Can't be an easier choice to push globally a linker switch, if it exists, to
> disable codesigning altogether for MP software?
macOS 11 on ARM now require codesigning. Binaries that are not codesigned
cannot be used at all.
, macports-users@lists.macports.org
Assunto: RE: Apple ARM binary codesign issue
look please!!
phone +552122366155
+552121796156
https://photos.app.goo.gl/eZ1qaq6xiciZLdDq9
https://photos.app.goo.gl/vMh9wRVp9yYV2TJ47
https://photos.app.goo.gl/eq6Jp4E7BBPhtYWw6
https://photos.app.goo.gl/wHHNkfg
, macports-users@lists.macports.org
Assunto: RE: Apple ARM binary codesign issue
look please!!
phone +552122366155
+552121796156
https://photos.app.goo.gl/eZ1qaq6xiciZLdDq9
https://photos.app.goo.gl/vMh9wRVp9yYV2TJ47
https://photos.app.goo.gl/eq6Jp4E7BBPhtYWw6
https://photos.app.goo.gl/wHHNkfg
Re: Apple ARM binary codesign issue
Can't be an easier choice to push globally a linker switch, if it exists, to disable codesigning altogether for MP software?
On Wed, 23 Sep 2020, 03:09 Saagar Jha, <saa...@saagarjha.com> wrote:
As far as I understand, ad-hoc codesigning is not
Apple ARM binary codesign issue
Can't be an easier choice to push globally a linker switch, if it exists, to disable codesigning altogether for MP software?
On Wed, 23 Sep 2020, 03:09 Saagar Jha, <saa...@saagarjha.com> wrote:
As far as I understand, ad-hoc codesigning is not actua
Can't be an easier choice to push globally a linker switch, if it exists,
to disable codesigning altogether for MP software?
On Wed, 23 Sep 2020, 03:09 Saagar Jha, wrote:
> As far as I understand, ad-hoc codesigning is not actually really meant to
> protect a file on disk because you can just
On Tue, Sep 22, 2020 at 6:24 PM Ken Cunningham
wrote:
> ...
> I'm trying to imagine how Jeremy might prevent hackers from surreptitiously
> modifying signed binaries with strip or install_name_tool (which is good)
> while letting people modify signed binaries with strip or install_name_tool
>
On 2020-09-22, at 12:58 PM, Ryan Schmidt wrote:
>
> To me it seems unrealistic for Apple to suggest that an infinite number of
> open source projects, many of whose developers have never seen a Mac, should
> now add code to their build systems to codesign things on macOS. Apple made a
>
On 2020-9-23 05:33 , Ryan Schmidt wrote:
>
> Send feedback through the Feedback Assistant app.
Yes, everyone with any issues with Apple preview software should do this
early and often. I've read that number of duplicates is one of the ways
they determine issue priority internally.
- Josh
On Sep 22, 2020, at 14:52, Ken Cunningham wrote:
> On 2020-09-22, at 11:58 AM, Ryan Schmidt wrote:
>>
>> I hope that Apple fixes their toolchain to work without such intervention.
>
> I believe this may ultimately come under the category of "intended
> behaviour".
To me it seems
On 2020-09-22, at 11:58 AM, Ryan Schmidt wrote:
>
> I hope that Apple fixes their toolchain to work without such intervention.
>
I believe this may ultimately come under the category of "intended behaviour".
I can understand why they would want these changes to invalidate the signature.
I
On Sep 22, 2020, at 14:19, Michael Dickens wrote:
> I have macOS 11.0beta7 installed : check!
>
> Compare / contrast ARM Mac versus MacBook Pro 16 : check!
>
> I have Xcode 12.2 beta installed : check!
>
> I've removed "/Library/Developer/CommandLineTools" : check!
>
> I hope that Apple
On 22/09/2020 15:19, Michael Dickens wrote:
> I have macOS 11.0beta7 installed : check!
>
> Compare / contrast ARM Mac versus MacBook Pro 16 : check!
>
> I have Xcode 12.2 beta installed : check!
>
> I've removed "/Library/Developer/CommandLineTools" : check!
>
> I hope that Apple fixes their
I have macOS 11.0beta7 installed : check!
Compare / contrast ARM Mac versus MacBook Pro 16 : check!
I have Xcode 12.2 beta installed : check!
I've removed "/Library/Developer/CommandLineTools" : check!
I hope that Apple fixes their toolchain to work without such intervention :
check!
Do you
On Sep 22, 2020, at 13:29, Michael Dickens wrote:
> % codesign -v - --ignore-resources
> /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8
> /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8:
> invalid signature (code or signature have been
There has been some discussion about the recent change Apple made for macOS
11.0beta7 for ARM Mac only (-not- Intel Mac at this time); we in MP-land had
some on this PR < https://github.com/macports/macports-ports/pull/8328 >. As
pointed out, a better venue for discussion would be these lists.
27 matches
Mail list logo
