Home

Frequently Asked Questions

Below is each FAQ entry and an excerpt from the answer. Click the Question to view the full answer.
Why is Column DBpasswd in users_conf table is not encrypted?

[originally submitted by fling]

Versions affected: LedgerSMB 1.2.x

The decision was made because there is no way to hide this information from the web server, since it needs to log into the database. It is better not to have a false sense of security. SQL-Ledger obfuscates this information but does not truly encrypt it.

Anyway, this problem is going away because 1.3 changes the way db passwords are handled.
Why is LedgerSMB PostgreSQL-only?

Adding support for other database management systems would require that the database logic be coded to the least common denominator. We have decided that we want to eventually allow add-ons in different languages, and thus the database becomes the only point where we can enforce accounting logic consistantly across all parts of the application. Porting and maintaining such logic across database systems is not feasible for this project.

Additionally PostgreSQL is an outstanding RDBMS and we have no desire to move from it.
« first‹ previous12