summaryrefslogtreecommitdiff
path: root/databases/ldb
AgeCommit message (Collapse)AuthorFilesLines
2022-06-30*: Revbump packages that use Python at runtime without a PKGNAME prefixnia1-1/+2
2022-03-13ldb: needs newer teventnia1-1/+2
2022-03-10databases/ldb: remove wip reference from bl3thor1-2/+2
2022-03-07ldb: version 2.4.2 for incoming samba4 updatethor3-9/+9
2021-11-10ldb: updated to 2.2.3adam2-6/+6
2.2.3: Unknown changes
2021-10-26databases: Replace RMD160 checksums with BLAKE2s checksumsnia1-2/+2
All checksums have been double-checked against existing RMD160 and SHA512 hashes The following distfiles could not be fetched (some may be only fetched conditionally): ./databases/cstore/distinfo D6.data.ros.gz ./databases/cstore/distinfo cstore0.2.tar.gz ./databases/cstore/distinfo data4.tar.gz
2021-10-07databases: Remove SHA1 distfile hashesnia1-2/+1
2021-06-22samba4: downgrade to 4.13.9, as discussed on netbsd-users@nia2-9/+8
2021-05-11Re-enable building databases/ldb without ldap support.hauke4-7/+44
2021-04-14ldb: updated to 2.3.0adam2-7/+7
2.3.0: Unknown changes
2021-03-24ldb: updated to 2.2.1; samba: updated to 4.13.7adam2-8/+7
============================== Release Notes for Samba 4.13.7 March 24, 2021 ============================== This is a follow-up release to depend on the correct ldb version. This is only needed when building against a system ldb library. This is a security release in order to address the following defects: o CVE-2020-27840: Heap corruption via crafted DN strings. o CVE-2021-20277: Out of bounds read in AD DC LDAP server. ======= Details ======= o CVE-2020-27840: An anonymous attacker can crash the Samba AD DC LDAP server by sending easily crafted DNs as part of a bind request. More serious heap corruption is likely also possible. o CVE-2021-20277: User-controlled LDAP filter strings against the AD DC LDAP server may crash the LDAP server. For more details, please refer to the security advisories. Changes since 4.13.6 -------------------- o Release with dependency on ldb version 2.2.1.
2020-12-04Revbump packages with a runtime Python dep but no version prefix.nia1-1/+2
For the Python 3.8 default switch.
2020-11-12ldb: updated to 2.2.0adam2-7/+7
2.2.0: Unknown changes
2020-07-06ldb: updated to 2.1.4adam2-7/+7
2.1.4: Unknown changes
2020-05-19net/samba4 databases/ldb: updated to 4.12.3 2.1.3adam2-8/+7
Changes 4.12.3: * BUG 14301: Fix smbd panic on force-close share during async io. * BUG 14343: s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[] array. * BUG 14361: vfs_io_uring: Fix data corruption with Windows clients. * BUG 14372: Fix smbd crashes when MacOS Catalina connects if iconv initialization fails. * BUG 14150: Exporting from macOS Adobe Illustrator creates multiple copies. * BUG 14256: smbd does a chdir() twice per request. * BUG 14320: smbd mistakenly updates a file's write-time on close. * BUG 14350: vfs_shadow_copy2: implement case canonicalisation in shadow_copy2_get_real_filename(). * BUG 14375: Fix Windows 7 clients problem after upgrading samba file server. * BUG 14359: s3: Pass DCE RPC handle type to create_policy_hnd. * BUG 14155: Fix uxsuccess test with new MIT krb5 library 1.18. * BUG 14342: mit-kdc: Explicitly reject S4U requests. * BUG 14352: dbwrap_watch: Set rec->value_valid while returning nested share_mode_do_locked(). * BUG 14345: lib:util: Fix smbclient -l basename dir. * BUG 14336: s3:libads: Fix ads_get_upn(). * BUG 14348: ctdb: Fix a memleak. * BUG 14366: Malicous SMB1 server can crash libsmbclient. * BUG 14330: ldb: Bump version to 2.1.3, LMDB databases can grow without bounds * BUG 14361: vfs_io_uring: Fix data corruption with Windows clients. * BUG 14344: s3/librpc/crypto: Fix double free with unresolved credential cache. * BUG 14358: docs-xml: Fix usernames in pam_winbind manpages.
2020-05-19ldb: pkgsrc toolify previous (preferred sed may not be "sed")gutteridge1-3/+3
2020-05-18Unbreak building without ldap support - the library got built andhauke2-2/+10
installed, anyway, resulting in a PLIST error. ldb's snazzy little build system has no official configuration option for this, so we reach in and flick the switch by hand.
2020-04-29ldb: updated to 2.1.2adam2-7/+7
2.1.2: Unknown changes
2020-04-02ldb: updated to 2.1.1adam2-8/+7
2.1.1: Unknown changes (needed for Samba 4.12.0).
2020-03-18ldb: add ldap PKG_OPTION. Otherwise net/samba4's ldap option can't work.tnn3-4/+19
2020-01-26all: migrate homepages from http to httpsrillig1-2/+2
pkglint -r --network --only "migrate" As a side-effect of migrating the homepages, pkglint also fixed a few indentations in unrelated lines. These and the new homepages have been checked manually.
2020-01-18*: Recursive revision bump for openssl 1.1.1.jperkin1-1/+2
2019-12-30ldb: updated to 2.0.8adam2-8/+7
2.0.8: Unknown changes
2019-11-23Recursive revbump based on devel/cmocka 1.1.3 -> 1.1.5mef1-1/+2
2019-11-10ldb: updated to 2.0.7adam5-16/+16
2.0.7: Unknown changes
2019-08-03ldb: updated to 1.5.5adam3-10/+9
1.5.5: Unknown changes
2019-06-22Fixes a build failure when the letter 'j' appears in MAKEFLAGS.jmcneill2-1/+20
2019-04-25PKGREVISION bump for anything using python without a PYPKGPREFIX.maya1-2/+2
This is a semi-manual PKGREVISION bump.
2019-04-04ldb: add dependency on openldap-client to fix PLIST mismatches.bsiegert1-1/+3
From Michael Moll via Pull Request. Fixes NetBSD/pkgsrc#45.
2019-03-29Fix ldb build as per suggestion from wiz@prlw11-2/+2
2019-03-27ldb: mark as incompatible with Python 2.7, since tdb required Python 3.xadam1-1/+3
2019-03-20ldb: added version 1.5.4adam7-0/+197
ldb is a LDAP-like embedded database. It is not at all LDAP standards compliant, so if you want a standards compliant database then please see the excellent OpenLDAP project. What ldb does is provide a fast database with an LDAP-like API designed to be used within an application. In some ways it can be seen as a intermediate solution between key-value pair databases and a real LDAP database. ldb is the database engine used in Samba4. Features: * The main features that separate ldb from other solutions are: * Safe multi-reader, multi-writer, using byte range locking * LDAP-like API * fast operation * choice of local tdb or remote LDAP backends * integration with talloc * schema-less operation, for trivial setup * modules for extensions (such as schema support) * easy setup of indexes and attribute properties * LDIF for import/export * ldbedit tool for database (via LDIF) editing (reminiscent of 'vipw')