Recherche avancée

Sur d’autres sites (14906)

• How to prevent App sandoxing from blocking a plugin usage after codesigning ?

  27 mai 2020, par Cyhzault

  I'm struggling to codesign my Unity application in order to push it to the Mac App Store. I followed the unity recommended process but some issues appeared after the codesign command. I've been able to fix some of them by adding new keys in my entitlement file but i'm still stuck due to the App Sandboxing mecanism.

  



  In my application I use an external plugin named FFmpeg to manage video encoding. After codesigning with the mandatory app sandboxing entitlement set to true, the plugin stopped working and i have no log explaining why.

  



  I tried multiple solutions detailed in other posts like defining an AppSandbox inheritance or adding more keys to my entiltement file but none of them worked.

  



  I'm new to codesigning and here is my process and entitlements file :

  



  

  1. chmod -R a+xr ./MY_APP.app

  


  2. codesign --force --sign '3rd Party Mac Developer Application: My Company (id)' --entitlements ./FFmpeg.entitlements ./MY_APP.app/Contents/Resources/Data/StreamingAssets/FFmpegOut/macOS/ffmpeg

  


  3. codesign -f --deep -s '3rd Party Mac Developer Application: My Company (id)' --entitlements ./MY_APP.entitlements ./MY_APP.app

  


  4. Verify codesign & Product build - both successful

  


  



  The main entitlement file for the app (MY_APP.entitlements) :

  



  &lt;?xml version="1.0" encoding="UTF-8"?>&#xA;&#xA;<plist version="1.0">&#xA;    <dict>&#xA;            <key>com.apple.security.app-sandbox</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.files.user-selected.read-write</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.network.client</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.files.user-selected.executable</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.cs.allow-unsigned-executable-memory</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.cs.disable-library-validation</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.cs.allow-dyld-environment-variables</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.get-task-allow</key>&#xA;            <true></true>&#xA;    </dict>&#xA;</plist>&#xA;

  



  Here is the second entitlement file (FFmpeg.entiltlement) for the plugin with inheritance :

  



  &lt;?xml version="1.0" encoding="UTF-8"?>&#xA;&#xA;<plist version="1.0">&#xA;    <dict>&#xA;            <key>com.apple.security.app-sandbox</key>&#xA;            <true></true>&#xA;            <key>com.apple.security.inherit</key>&#xA;            <true></true>&#xA;    </dict>&#xA;</plist>&#xA;

  



  The plugin i used can be found on github, i'll cross post my issue there as well.

  



  I will gladfully take any idea or solution, 
Thanks for your help,

  



  Regards,
Alexis

  


• Intermittent segfault with docker no-new-privileges

  19 juin 2019, par whadhack

  Anyone experienced intermittent segfault when —security-op=no-new-privileges has been turned on ? Is there a way to prevent that , short of privileged mode ?

  Docker container with "—security-op=no-new-privileges" has been enabled.

  avcodec_send_packet()

  No segfault as in privileged mode is the expected result.

• armv6 : Accelerate ff_fft_calc for general case (nbits != 4)

  16 juillet 2014, par Ben Avison

  armv6 : Accelerate ff_fft_calc for general case (nbits != 4)
  The previous implementation targeted DTS Coherent Acoustics, which only
  
  requires nbits == 4 (fft16()). This case was (and still is) linked directly
  
  rather than being indirected through ff_fft_calc_vfp(), but now the full
  
  range from radix-4 up to radix-65536 is available. This benefits other codecs
  
  such as AAC and AC3.
  The implementaion is based upon the C version, with each routine larger than
  
  radix-16 calling a hierarchy of smaller FFT functions, then performing a
  
  post-processing pass. This pass benefits a lot from loop unrolling to
  
  counter the long pipelines in the VFP. A relaxed calling standard also
  
  reduces the overhead of the call hierarchy, and avoiding the excessive
  
  inlining performed by GCC probably helps with I-cache utilisation too.
  I benchmarked the result by measuring the number of gperftools samples that
  
  hit anywhere in the AAC decoder (starting from aac_decode_frame()) or
  
  specifically in the FFT routines (fft4() to fft512() and pass()) for the
  
  same sample AAC stream :
                Before          After
  
                Mean   StdDev   Mean   StdDev  Confidence  Change
  
  Audio decode  2245.5 53.1     1599.6 43.8    100.0%      +40.4%
  
  FFT routines  940.6  22.0     348.1  20.8    100.0%      +170.2%
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/arm/fft_init_arm.c
  • [DH] libavcodec/arm/fft_vfp.S