Open GoogleCodeExporter opened 8 years ago
The problem is, XLD is an open source software, and includes some GPLed
components. As long as the sign module is distributed as a part of XLD package,
it should be open source. And even if the module were closed source (by
distributing the module as an additional plugin), the checksum/encryption
algorithm could be easily broken with a reverse-engineerging such as
disassembling. So, in my opinion, a security when implementing the feature
under closed source is almost the same as open source implementation, in terms
of cryptology. The only "secure" solution is to use a client-server
authentication system.
Original comment by tmkkmac
on 18 Aug 2011 at 5:25
Definitely XLD should remain open source; no question about that. I'll look
into the client-server system though. Thanks for the feedback tmkkmac.
Original comment by htorr8...@gmail.com
on 18 Aug 2011 at 5:54
A rip log checksum tool has been released as an external plugin:
http://xld.googlecode.com/files/XLDLogChecker-20121122.zip
It works with version 20121027 and later. When you put the plugin to
~/Library/Application Support/XLD/PlugIns, XLD will automatically generate a
checksum for each rip log file.
Logchecker is available from XLD -> Log Checker.
Original comment by tmkkmac
on 22 Nov 2012 at 10:02
Updated the plugin: including some minor changes.
http://xld.googlecode.com/files/XLDLogChecker-20121222.zip
XLD version 20121222 can check files with CLI.
Original comment by tmkkmac
on 22 Dec 2012 at 3:18
There are a few files in the .zip file... do you but them all in
~/Library/Application Support/XLD/PlugIns?
Original comment by TBatt...@gmail.com
on 11 Oct 2013 at 12:29
A few files?
Only XLDLogChecker.bundle is included in the zip archive.
Original comment by tmkkmac
on 11 Oct 2013 at 1:29
Original issue reported on code.google.com by
htorr8...@gmail.com
on 18 Aug 2011 at 5:14