[notpeter]

I'm attempting to use Ensymble to sign the unsigned Python packages with my free DevCert and running into some problems.

Here is the command line I'm using (multi-line here for readability):

~/bin/ensymble.py signsis --cert=outgoing.cer
--privkey=privatekey
--passphrase=mypass PythonScriptShell_1_3_21_3rdEd_unsigned_freedevcert.SIS PythonShell1_3_21_3rd_SignedPete.sis
-v
--execaps=Powermgmt+ProtServ+SwEvent+NetworkServices+LocalServices+ReadUserData+WriteUserData+Location+SurroundingsDD+UserEnvironment

Output:

/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/termios.py:7: DeprecationWarning: the TERMIOS module is deprecated; please use termios
  DeprecationWarning)
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/fcntl.py:7: DeprecationWarning: the FCNTL module is deprecated; please use fcntl
  DeprecationWarning)

Input SIS file    PythonScriptShell_1_3_21_3rdEd_unsigned_freedevcert.SIS
Output SIS file   PythonShell1_3_21_3rd_SignedPete.sis
Certificate       outgoing.cer
Private key       privatekey
EXE capabilities  0xff104 (ALL-TCB-CommDD-MultimediaDD-ReadDeviceData-WriteDeviceData-DRM-TrustedUI-DiskAdmin-NetworkControl-AllFiles)
DLL capabilities  <not set>

ensymble.py: 1 EXE-files will be modified, 0 DLL-files will be modified

But if I list one less capability (here I remove UserEnvironment, but it can be any of the capabilities) like so

~/bin/ensymble.py signsis --cert=outgoing.cer --privkey=privatekey --passphrase=mypass PythonScriptShell_1_3_21_3rdEd_unsigned_freedevcert.SIS PythonShell1_3_21_3rd_SignedPete.sis -v --execaps=Powermgmt+ProtServ+SwEvent+NetworkServices+LocalServices+ReadUserData+WriteUserData+Location+SurroundingsDD

I get proper output (all lines as above except EXE capabilities) which is now correctly:

EXE capabilities  0x7f104 (PowerMgmt+ProtServ+SwEvent+NetworkServices+LocalServices+ReadUserData+WriteUserData+Location+SurroundingsDD)

What is the deal here? execaps can handle nine listed capabilities, but with 10 it decides you instead want 'ALL'? (special 3 [rw device; trustedUI] & the big 7?)

I see the same behavior with --dllcaps, but omitted those lines for conciseness (yep, I could've been more verbose!)

The packages that get created install properly, but won't run (I imagine because of a certificate/rights mismatch or similar).

Anyone got any ideas?


Environment info:
Ensymble 0.22
Python 2.3.5 under OS X with ensymble_python2.3-0.22.py (deprecated stuff outputted due to old version of python)
Python 2.5.1 under WinXP with ensymble_python2.5-0.22.py (no deprecation warnings in output)

[jethro.fn]

Originally Posted by notpeter

EXE capabilities  0xff104 (ALL-TCB-CommDD-MultimediaDD-ReadDeviceData-WriteDeviceData-DRM-TrustedUI-DiskAdmin-NetworkControl-AllFiles)

EXE capabilities  0x7f104 (PowerMgmt+ProtServ+SwEvent+NetworkServices+LocalServices+ReadUserData+WriteUserData+Location+SurroundingsDD)

Ensymble tries to be clerer and shows the names of capabilities in the shortest form possible. ALL-CAP1-CAP2-... is shorter than CAP1+CAP2+... after the list of capabilities grows sufficiently long. Notice the "+" and "-" between capabilities. This is a cosmetic thing only.