3 ms·

Note these are thrown-over-the-wall source dumps, with no valuable VCS history, nothing more recent than at least 2 releases ago, and sending a PR will likely o

Note these are thrown-over-the-wall source dumps, with no valuable VCS history, nothing more recent than at least 2 releases ago, and sending a PR will likely only receive crickets (said as someone who recently found an easily patchable bug in dyld, contemplated the idea of opening a PR and was told by an ex-colleague who now works at Apple that my best shot would be through feedbackassistant.apple.com). BTW, those repos don't take issues.

dapids 5y ago
I just got a security bug fixed last month in dyld in one release cycle. Didn't strike me as difficult. I emailed them, and they fixed it. Not much more to add then that. Have you actually tried? Also dyld isn't just some thrown-over the wall code. It's completely designed and built by Apple and is the cornerstone to making the user-space runtime functional.
- glandium 5y ago
  All the code designed and built by Apple is thrown-over-the-wall. That's old-version-of-source-available, barely open source. I tried emailing ld64's author about a bug in the past without success. I don't remember how I found their name/address back then, but I sure can't find any names or contact information for dyld right now...
  - dapids 5y ago
    What on earth are you talking about? ld64 is a completely different beast than dyld in today's world. Also, I'm not sure looking for individual points of contact in a large org is the best idea. I emailed security@apple.com. Even if it's not a security bug they will help direct you to the right team. Again, have you even tried?
    - glandium 5y ago
      > What on earth are you talking about? I'm talking about trying to contact people at Apple about bugs in their "open source" code. Why would I send an email to security@apple.com for something that is not a security issue? > Again, have you even tried? Yes, I tried for ld64 in the past, and I tried through what I was told had the best chances to work by an Apple employee this time for dyld. I'm not holding my breath, though.

dapids 5y ago

I just got a security bug fixed last month in dyld in one release cycle. Didn't strike me as difficult. I emailed them, and they fixed it. Not much more to add then that. Have you actually tried? Also dyld isn't just some thrown-over the wall code. It's completely designed and built by Apple and is the cornerstone to making the user-space runtime functional.

glandium 5y ago
All the code designed and built by Apple is thrown-over-the-wall. That's old-version-of-source-available, barely open source. I tried emailing ld64's author about a bug in the past without success. I don't remember how I found their name/address back then, but I sure can't find any names or contact information for dyld right now...
- dapids 5y ago
  What on earth are you talking about? ld64 is a completely different beast than dyld in today's world. Also, I'm not sure looking for individual points of contact in a large org is the best idea. I emailed security@apple.com. Even if it's not a security bug they will help direct you to the right team. Again, have you even tried?
  - glandium 5y ago
    > What on earth are you talking about? I'm talking about trying to contact people at Apple about bugs in their "open source" code. Why would I send an email to security@apple.com for something that is not a security issue? > Again, have you even tried? Yes, I tried for ld64 in the past, and I tried through what I was told had the best chances to work by an Apple employee this time for dyld. I'm not holding my breath, though.