- Migrate DAV folder ACL into Kolab4-style sharees
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Fri, Feb 7
Wed, Feb 5
- Add SendMail command tests
Tue, Feb 4
- Cleanup
Mon, Feb 3
Thu, Jan 30
So the 389-ds packages are a mess in Ubuntu. The tools and scripts needed to update the on disk formats are not built and when I enable them they are broken. I am not sure if the upstream source is broken or it comes from the patches applied by Debian or Ubuntu. The only thing that I found worked was moving the contents of /var/lib/dirsrv and /etc/dirsrv to a backup, then upgrade from 18.04 to 20.04 and return the contents before rebooting. There were several other hiccups in the process as kolab packaging for Ubuntu newer than 18.04 is broken and missing packages, see: https://git.kolab.org/T8416
Wed, Jan 29
Tue, Jan 28
- Support IMAP folder ACL migration
- CS
- DataMigrator: Advertise itself as a Kolab client when talking to Kolab IMAP server
- Speed up Fs\Item::storeProperty()
- CS fixes
Mon, Jan 27
In D5090#64308, @machniak wrote:When $verifyMFA=true you still call hash() and store it in the cache. When using $verifyMFA=false that hash would be used. If you add to this not using $clientIP it looks to me like a potential geo-lock bypass.
Addressed comments
When $verifyMFA=true you still call hash() and store it in the cache. When using $verifyMFA=false that hash would be used. If you add to this not using $clientIP it looks to me like a potential geo-lock bypass.
Thu, Jan 23
On our server ipv6 was disabled in the kernel. Enabling ipv6 did resolve the crash of guam
Wed, Jan 22
I also see crashes of guam on AlmaLinux release 9.5 (Teal Serval)
I tested with I guam-0.9.13-3.61.el9.kolab_16.x86_64
- Fix non-ascii folders migration, migrate folder subscription state
- Use kolab3:// and kolab4:// schemes
Fri, Jan 17
- Small improvements and cleanup
Tue, Jan 14
Lookup by id
- Add tests for ContentId and ContentLocation, add some comments
- more tests
Jan 10 2025
Jan 9 2025
Jan 8 2025
Jan 6 2025
Moved the token validation to findAndAuthenticate, so we can skip mfa when a token has been validated.
After another look I think we might be doing something wrong here. A valid token should disable/skip 2FA use. Current User::findAndAuthenticate() will not skip 2FA if the password is a valid token.
Comment style
Now with an actual test
Addressed comments
Jan 4 2025
Jan 3 2025
- Fix comment
- ID generation for mail without Message-ID
- Incremental migration tests for Takeout
- Fixes in incremental migration across drivers
Jan 2 2025
Placing this in User::validateCredentials() maybe is not a bad idea, but it creates some redundancy. See NGINXController::authorizeRequest() - AuthUtils::tokenValidate() now will be called twice. Also, test this new case in Unit/UserTest::testPasswordValidation().