Can I use IBANs with LedgerSMB?
Yes. IBANs are very long bank account numbers. LedgerSMB has no problems storing, retrieving and using these without any issue.
- Read more about Can I use IBANs with LedgerSMB?
- Log in or register to post comments
1.4
Is LedgerSMB SEPA proof?
Yes. SEPA (Single Euro Payments Area) requires support for very long bank account numbers (IBANs or International Bank Account Numbers). LedgerSMB can store and use these numbers without problems.
- Read more about Is LedgerSMB SEPA proof?
- Log in or register to post comments
How do I restore my data?
Assuming you have followed the How Do I Backup My Data instructions, you can restore your database as follows...
Note LedgerSMB versions prior to version 1.9.16 did not support PostgreSQL 14 or higher due to a backward incompatible change in PostgreSQL 14.
- Read more about How do I restore my data?
- Log in or register to post comments
How do I backup my data?
Log in to the the 'setup.pl' administrative interface, using your ledgersmb database admin user (usually "lsmb_dbadmin" or "postgres"). The default address for setup.pl is http://localhost/ledgersmb/setup.pl.
There are 2 buttons:
- Backup database (parts, customers, accounting records, etc)
- Backup roles (your login accounts and rights)
One creates a backup of the content of your database. The other creates a backup of the roles.
- Read more about How do I backup my data?
- 1 comment
- Log in or register to post comments
Security advisory for CVE-2021-3731 (Clickjacking)
Insufficient protection against 'clickjacking'
Summary
LedgerSMB does not sufficiently guard against being wrapped by
other sites, making it vulnerable to 'clickjacking. This allows
an attacker to trick a targetted user to execute unintended actions.
Known vulnerable
All of:
Security advisory for CVE-2021-3694 (Cross site scripting)
Reflected cross-site scripting of authenticated users in LedgerSMB
Summary
LedgerSMB does not sufficiently HTML-encode error messages sent to the browser. By sending a specially crafted URL to an authenticated user, this flaw can be abused for remote code execution and information disclosure.
Known vulnerable
All of:
Upgrade to LedgerSMB 1.8
Overview
Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.
- Read more about Upgrade to LedgerSMB 1.8
- Log in or register to post comments
Upgrade to LedgerSMB 1.6 (from 1.5 or 1.4/starman)
Upgrading tarball installations
There are two steps to upgrading a LedgerSMB 1.5.x to 1.6:
- Upgrade the software
- Upgrade the company database
The last step must be executed for each company database that's set up.
These steps also apply when upgrading a 1.4 installation running Starman. To upgrade 1.4 installations not running on Starman, or to upgrade from earlier versions, please see Upgrading to Ledgersmb 1.5. Note that the default configuration for 1.4 runs CGI, not Starman.
- Read more about Upgrade to LedgerSMB 1.6 (from 1.5 or 1.4/starman)
- Log in or register to post comments
1.4.42 Released (end-of-life release)
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. This will
be the last release in the 1.4 series, which has reached End-Of-Life
(EOL) status on September 15, 2017; after three full years of active
maintenance. The fact that the release series has reached EOL status
means that no further community supported releases will be
created - except for translation updates when available. Users are
1.4.41 Released
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. This release
contains the following fixes and improvements:
Changelog for 1.4.41