osx - Getting a Mac to trust an application (synergy on loginwindow) -


i'm trying synergy load when mac starts can use mouse/keyboard log in. followed these instructions

http://sourceforge.net/p/synergy2/discussion/199580/thread/76cf630a

where synology installed in /applications/synergy.app/

the plist file looks this

<?xml version="1.0" encoding="utf-8"?> <!doctype plist public "-//apple computer//dtd plist 1.0//en" "http://www.apple.com/dtds/propertylist-1.0.dtd"> <plist version="1.0"> <dict>     <key>keepalive</key> <true/>     <key>label</key> <string>net.sourceforge.synergy2.loginwindow</string>     <key>limitloadtosessiontype</key> <string>loginwindow</string>     <key>programarguments</key>     <array>         <string>/applications/synergy.app/contents/macos/synergyc</string>         <string>-f</string>         <string>-1</string>         <string>--name</string>         <string>mini</string>         <string>--debug</string>         <string>warning</string>         <string>192.168.1.200</string>     </array>     <key>runatload</key>     <true/> </dict> </plist> 

but i'm getting these errors in /var/log/system.log

synergyc[220]: 3891612: (connect_and_check) untrusted apps not allowed connect or launch window server before login.

the files owned correctly

-rwxr-xr-x  1 root  wheel   893040 may  2 21:07 synergy -rwxr-xr-x  1 root  wheel  3999988 may  2 21:07 synergyc -rwxr-xr-x  1 root  wheel  4269168 may  2 21:07 synergys 

i've removed quarantine

xattr -d com.apple.quarantine /applications/synergy.app/contents/macos/* 

i don't know else do? why osx being difficult? else can try?

p.s. tried hook method didn't work either. approach looks cleaner.

from apple's developer tech note on daemons , agents:

if, in mac os x 10.5 , later, see message shown in listing 9 might mistakenly think solution system 'trust' application, perhaps via code signing.

listing 9: pre-login trust message

untrusted apps not allowed connect or launch window server before login.

however, isn't case. message telling you're trying connect window server wrong context. see message if try connect global window server service outside of pre-login context before user has logged in; typically means you're trying use window server daemon.

you should not attempt fix convincing window server trust program; doing cause other problems further down road. example, if connect window server daemon, still have deal window server lifecycle issues described previously.

instead, should fix problem changing code run in correct context. if need connect window server in pre-login context, create pre-login launchd agent. example of this, see sample code 'preloginagents'.

it looks me "right" way involve rewriting of synergy (see sample code link above). there's synergy bug report on this, filed 3 years ago no real action... think if want fixed it's it.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -