summaryrefslogtreecommitdiff
path: root/doc/release_notes
blob: f1493b33da69c628f5ead787d44f9de40f7dec35 (plain)
  1. RELEASE NOTES
  2. LedgerSMB 1.1.1
  3. 1: Welcome to LedgerSMB
  4. LedgerSMB is an accounting and ERP program initially aimed at small to midsize
  5. businesses. Currently the financials and supply chain management modules are
  6. fairly complete, while other modules such as project management exist in a
  7. rudamentary form. The initial features are identical to SQL-Ledger 2.6.17 from
  8. which it was derived, but the feature set is starting to diverge rapidly.
  9. 1.1 System Requirements:
  10. * Perl 5.8.
  11. * Apache, IIS, or other web server that supports CGI.
  12. * PostgreSQL 8.0 or higher. 7.3 and 7.4 could be supported with some effort but
  13. will not work out of the box.
  14. * Any operating system that supports the above environment.
  15. * The following CPAN modules:
  16. * Data::Dumper
  17. * Locale::Maketext
  18. * Locale::Maketext::Lexicon
  19. * MIME::Base64
  20. * Digest::MD5
  21. * HTML::Entities
  22. * DBI
  23. * DBD::Pg
  24. * Math::BigFloat
  25. * IO::File
  26. * Encode
  27. * Locale::Country
  28. * Locale::Language
  29. * Time::Local
  30. * Cwd
  31. * Config::Std
  32. * MIME::Lite
  33. 2: What's New in 1.2?
  34. 2.1: Database changes:
  35. All core tables now have defined primary keys. This allows Slony-I to be
  36. supported out of the box.
  37. Chris Browne has contributed a setup script for Slony. It is in the
  38. utils/replication directory.
  39. Also all user information has been moved into the database and the password
  40. algorythm has been changed from crypt to md5. This means that users will need
  41. to convert their accounts prior to first login on the new system (if this is an
  42. upgrade).
  43. Also now the defaults table has moved from a one column per value structure to a simple key->value structure.
  44. 2.2: Security
  45. LedgerSMB 1.2 has been through a detailed SQL injection audit of the codebase
  46. inherited from SQL-Ledger. As a result several vulnerabilities which were known
  47. to be exploitable were corrected along with hundreds of places where
  48. vulnerabilities may have been exploitable but we didn't have time to verify the
  49. what was involved in exploiting it. We believe though that many or most of the
  50. issues were exploitable given a little time and effort.
  51. Also, we discovered the template editor's security system was moved from
  52. blacklisting to whitelisting, eliminating a whole class of possible security
  53. issues.
  54. 2.3: New Features
  55. Metatron Technology Consulting's SL-POS codebase was merged with this project,
  56. providing a framework for POS hardware support and more.
  57. Online credit card processing support has been added.
  58. LSMB now supports an arbitrary number of defined currencies for a business and
  59. is no longer limited to 3.
  60. 2.4: Localization Changes
  61. Localization functions now use Gettext .po files on all platforms. This means that standard translation management tools will work with LSMB translations.
  62. 2.5: Other changes
  63. The ledger-smb.conf is now an inifile which will reduce the level of expertise
  64. necessary to configure it for non-Perl users.
  65. 3: Known Issues
  66. Reposting invoices is known to cause inaccuracies cost of goods sold and
  67. inventory accounts. This problem has been confirmed to affect SQL-Ledger 2.6.x
  68. as well and is caused by problems involving the de-allocation and trasaction
  69. reversal routines. It will be corrected (by removing the ability to truly
  70. repost invoices) in an upcoming version as we continue to re-engineer the
  71. application.
  72. 4: Differences between LedgerSMB and SQL-Ledger(TM)
  73. 4.1: Login name restrictions
  74. Logins in SQL-Ledger can contain any printable characters. In LedgerSMB these
  75. are restricted to alphanumeric characters and the symbols ., @, and -.
  76. 4.2: Session handling
  77. SQL-Ledger as of 2.6.17 uses session tokens for authentication. These tokens
  78. are based on the current timestamp and therefore insecure. Furthermore, these
  79. tokens are not tracked on the server, so one can easily forge credentials for
  80. either the main application or the administrative interface.
  81. LedgerSMB stores the sessions in the database. These are generated as md5 sums
  82. of random numbers and are believed to be reasonably secure. The sessions time
  83. out after a period of inactivity. As of the initial release both
  84. SQL-Ledger-style session ID's and the newer version are required to access the
  85. application. In future versions, the SQL-Ledger style session ID's will
  86. probably be removed.
  87. 4.3: Database Changes
  88. Under certain circumstances where the Chart of Accounts is improperly modified,
  89. it is possible to post transactions such that a portion of the transaction is
  90. put into a NULL account. LedgerSMB does not allow NULL values in the chart id
  91. field of the transaction.
  92. Also, the transaction amount has been changed from FLOAT to NUMERIC so that
  93. arbitrary precision mathematics can be used in third party reports. This ought
  94. to also allow SQL-Ledger to properly scale up better as SUM operations on
  95. floating points are unsafe for large numbers of records where accounting data is
  96. involved.
  97. 5: Roadmap
  98. This project has no defined roadmap but rather a set of statements and
  99. objectives contained in the documentation manager and trackers of sourceforge.
  100. In general, our development is focused around the following principles:
  101. * LSMB as infrastructure: LSMB should be accessible from other applications.
  102. * Universal applicability: LSMB should be usable by any any business and should
  103. always do the right thing in the background. Businesses should never find that
  104. they have outgrown the software.
  105. * Focus on Small to Midsize Businesses: LSMB's core market will remain in the
  106. small to midsize market.
  107. 6: Get Involved
  108. Contributors should start by joining the LedgerSMB users and devel lists. Code
  109. contributions at the moment must be committed by either project maintainer and
  110. should be submitted either using the patches interface at Sourceforge or the
  111. devel mailing lists.
  112. Additionally, we can use help in QA, documentation, advocacy, and many other
  113. places.
  114. SQL-Ledger is a registered trademark of DWS systems and is not affiliated with
  115. this project or its members in any way.