On 12/11/2014 23:51, Yannick DEVOS (XV4Y) wrote: > Hi Bill, Hi Yan, > > I am not a specialist about this questions, but this is my comment. > What you could do on OS X is at first run check if the KVASD is present (and > updated) and if not download it and install it (with the EULA dialog, etc). > The ClamXAV antivirus does this for its internal engine which is developed by > a different team than the GUI itself. I did consider such a solution for all platforms although it is probable that the application doesn't have permission to write the KVASD executable to the required location. The main reason that I didn't take this route and instead linked the KVASD install to the WSJT-X installer (more or less directly) is that it isolates the code that requires elevated permissions to the installer context.
In general I think it is a potential major security violation for any application to download executable content from the Internet and such ability should not be granted to a user level application. > > 73, > Yan - XV4Y. > --- > http://www.qscope.org/ 73 Bill G4WJS. > >> Le 13 nov. 2014 à 04:36, Bill Somerville <g4...@classdesign.com> a écrit : >> >> >> On Mac life is a bit more complex as the installer we use has no >> scripting or programmatic content, it simply uses standard OS X >> facilities to present the user with a graphical Drag'N'Drop install step >> to place the fully self contained WSJT-X application bundle into the >> system /Applications folder, or elsewhere. This is a fairly normal and >> very common Mac installation mechanism which is made possible by the >> fully self contained Mac application bundle structure itself. This means >> that on Mac a post installation step becomes necessary to "inject" KVASD >> into the system. The best place by far for this "injection" is into the >> WSJT-X bundle itself, this is because the KVASD application can then, >> with a few adjustment commands on the executable, reference the libgcc >> dylibs that are already bundled with WSJT-X. These references are >> relative paths therefore including the KVASD executable inside the >> WSJT-X application bundle allows the bundle to be moved around or copied >> without issue just like any other application bundle. >> Thoughts, comments and updates from the Linux packagers welcome. >> >> 73 >> Bill >> G4WJS. >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
