- User Since
- May 25 2015, 9:14 PM (282 w, 2 d)
Jul 4 2020
Dec 26 2019
I'm running Nextcloud 17 and connected Kolab 16 (both on Debian 10) via webdav.
In my Folder tree I have:
Dec 25 2019
Dec 3 2019
I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:
Nov 23 2019
I've seen in OBS that we now build packages for Debian 10.
What's your opinion: Is it probably ready to upgrade my instance?
The only package failing to build is chwala - where I could possiby use the old package...
Oct 8 2019
Oct 2 2019
According to https://obs.kolabsys.com/project/show/Kolab:Winterfell
RHEL_8 and Debian_10.0 have been added to Winterfell.
So my most pressing wishes have been granted :-)
Jun 22 2019
On my system wallace has been updated to 0.8.13-0~kolab2 and restarts seem to work now. I'l have an eye on it. If other people can confirm the fix we can close the ticket.
Jun 2 2019
Jun 1 2019
My python is Python 2.7.13 from the debian packages:
May 30 2019
I've tried reading the wallace source but didn't see an easy fix. For now I use a cron job
with the following script to fix wallace up:
May 19 2019
Nov 17 2017
Sep 18 2017
Current Winterfell seems to have it fixed:
Winterfell seems to use newest boot now:
Jul 19 2017
Mar 19 2017
That's far easier than I thought. We already use save_file_content for special condition.
Let's just do that instead of sending the "Location:"-header too. This patch replaces
to one above. Would that work?
Feb 21 2017
The wiki seem not to be available for me, but the following infos might help with autoconfig:
Yes, that'll load the file into memory - no problem for my users, because our files are small.
Feb 12 2017
Yes, I agree it's not a software bug, but I propose to add some documentation about delegation to
[which is empty right now]. Something like:
Feb 5 2017
My users still like the classic skin, but use only mail.
Anyway, we must not break people's setup, so we either need to modify the user settings
when upgrading or alert the admin and help him fix his system.
So we need to do more than just removing the skin.
Feb 4 2017
Feb 2 2017
Jan 28 2017
Thanks - it works for me.
Jan 24 2017
Jan 21 2017
Nov 19 2016
Nov 7 2016
I started to package endroid-qrcode for Debian and saw that there is a new upstream release 1.6.5 available. The changelog has:
Oct 31 2016
You recommended to remove the $config definition from plugins/kolab_2fa/lib/Kolab2FA/Driver/Yubikey,php, but that hunk is missing,
Otherwise looks good to me.
Oct 30 2016
That looks basically like a subset of privacyidea or lintop (and possibly) others.
Do we really want to travel that path?
A test with TOTP was successful.
Hm, there seems to be some confusion between method (driver to use) and id (yubikey:<hexcode>). the plugin tried to load config['kolab_2fa_yubikey:<hexcode>'] which obvously fails. The following patch (against Winterfell) seems to fix it for me - but I didn't test HOTP or TOTP token. And already added yubikeys had to be removed and readded.
Oct 26 2016
Jun 20 2016
From what I see Debian/testing (stretch) contains a newer phantomjs:
Feb 11 2016
Feb 5 2016
CentOS 7 runs a targeted SE Linux policy, which seems to work with minimal changes.
Please, let's fix what might be missing (until now it was easy...) instead of disabling
Please see one of my mails - I did everything the guides asked for - but still failed.
So my guess is that the guide needs some updates too.
Sep 8 2015
Getting OTP would be wonderful. I do own a Yubikey Edge, which is configured for OATH-HOTP and Challenge-Response HMAC-SHA1 (and U2F). I do use Challenge-Response for offline things like keepass, LUKS or Laptop-Login.