LedgerSMB forked with SQL-Ledger because the SQL-ledger dev SQL-ledger
dev decided to randomly change the licence without gaining the
approval of all the folks that had contributed to the project and also
refused to accept patches which fixed serious security issues, as in
really simple SQL injections and remote file includes.  Having worked
with Chris directly a couple times I can say that he and the rest of
the LedgerSMB crew are much more responsive to bug reports and
security concerns.

further reading:
http://lwn.net/Articles/227151/


Thanks,
Scott

On Fri, Apr 3, 2009 at 12:37 PM, Douglass Clem <[email protected]> wrote:
> LedgerSMB looks quite interesting. I noticed that it is a fork of
> SQL-Ledger, but I don't think I saw anything explaining the differences
> between the two. Also,  I was also unable to find a list of features for
> LedgerSMB. Would you mind pointing me to a link if I've overlooked
> something?
>
> Seeing as the data is in a SQL server, for backups I could do a dump of the
> DB. However, does it have an export feature into a standard format?
>
> --
> Douglass Clem
> Chief Technology Officer,
> Crashsystems LLC (crashsystems.net)
> Public Key: E1F6 ADF3 88B4 E5C4 E3B1
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to