Dev April 2016

dev@lists.roundcube.net

5 participants
7 discussions

Enigma S/MIME support
by Kyle Francis 23 Aug '16

23 Aug '16

Alec, Thanks for helping me get up and running with the enigma plugin and for pointing me to the previously existing work on an SMIME plugin. For those of you who don't know and are interested, I'm a Master's Candidate and I'm implementing S/MIME in the enigma plugin for an independent study this semester. So far I have implemented the following features: - Import PKCS#12 certificate store (password protected) - Pub cert, priv key, any additional certs contained in the store treated as CA certs. - create a hashed directory of CA certs - Verify S/MIME signatures (pkcs7-signatures .p7s) - Decrypt S/MIME encrypted emails - Decrypt and verify signed then encrypted emails Features that are not yet complete: - Encrypt only outgoing - Add menu option to Compose Window - Sign only outgoing (clear signing) - Add menu option to Compose window - Encrypt then Sign - Sign then Encrypt - List certs/details from settings view - Verify pkcs7-mime (.p7m) signed emails - Generate CSR - Handle CRL's (.p7c) Modifications are available at github.com/guitarmanusa/roundcubemail in a branch called enigma-smime-dev. -- Kyle Francis M.S.IT Candidate Rensselaer Polytechnic Institute Email - franck6(a)rpi.edu kyle(a)linuxtoolbox.ninja

3 8

rc next: ember broccoli error
by Brendan 01 May '16

01 May '16

has anyone encountered this error before? just trying to get things set up for the first time, everything was installed from scratch and latest versions. brendan@xps:~/rcube/roundcube-shell$ export JMAP_HOST=http://127.0.0.1:8080 && STYLEGUIDE=true && ember server version: 1.13.12 BroccoliMergeTrees: Expected Broccoli node, got undefined for inputNodes[0] TypeError: BroccoliMergeTrees: Expected Broccoli node, got undefined for inputNodes[0] at BroccoliMergeTrees.Plugin (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-plugin/index.js:23:13) at new BroccoliMergeTrees (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-merge-trees/index.js:29:10) at BroccoliMergeTrees (/home/brendan/rcube/roundcube-shell/node_modules/broccoli-merge-trees/index.js:23:53) at Class.module.exports.treeForVendor (/home/brendan/rcube/roundcube-shell/node_modules/roundcube-mail/index.js:28:12) at Class._treeFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/models/addon.js:319:31) at Class.treeFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/models/addon.js:289:19) at /home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:369:20 at Array.map (native) at EmberApp.addonTreesFor (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:367:30) at EmberApp._processedVendorTree (/home/brendan/rcube/roundcube-shell/node_modules/ember-cli/lib/broccoli/ember-app.js:796:29)

2 1

Please restore upgrade tutorial
by Zhang Huangbin 26 Apr '16

26 Apr '16

Dear developers, Could you please help restore the Roundcube upgrade tutorial? Old link is: http://trac.roundcube.net/wiki/Howto_Upgrade But i cannot find it in github repo. It's very important to sysadmins who need to upgrade. Thanks. ---- Zhang Huangbin, founder of iRedMail project: http://www.iredmail.org/ Time zone: GMT+8 (China/Beijing).

1 0

bug: html spellcheck on send
by Brendan 25 Apr '16

25 Apr '16

in roundcube-1.1.4 (and almost certainly other versions), we have noticed the following behavior (using the enchant spell engine): if you have a link (ie, {a href="http://blhblh.com"}Happy{/a} - brackets changed so no one's email client interprets them as a link) in an html email, the behavior of using the spellcheck button is different than when you go to send the email (and are configured to check spelling upon send). with the spellcheck button the client only passes the plain text through to the spellcheck engine, ie: Happy when sending, the client sends the full html and before being passed to the spellcheck engine it gets converted into text email content, ie: Happy [1] Links: ------ [1] http://blhblh.com the enchant spell engine then throws errors on "http" and "blhblh.com", both of which it really ought to be ignoring. i see two different solutions: 1) in program/lib/Roundcube/rcube_spellchecker.php function check(), replace: $this->content = $this->html2text($text); with: $this->content = strip_tags($text); 2) in program/lib/Roundcube/rcube_spellchecker_enchant.php (and rcube_spellchecker_pspell.php, etc) function check(), add in a regex to strip out lines matching /^\[\d+\] http:\/\/.*/ prior to tokenizing the text. #1 seems cleaner, but i'm not sure if there is a reason we need to use html2text there. does anyone from kolab have any input on the preferred way to deal with this?

2 2

Published Updates 1.1.5 and 1.0.9
by Thomas Bruederli 20 Apr '16

20 Apr '16

Dear subscribers We just published updates to both stable versions 1.0 and 1.1 delivering important bug fixes and helps protecting Roundcube against more XSS and CSRF attacks. Version 1.1.5 also has two new plugin hooks integrated and version 1.0.9 comes with cherry-picked fixes from the more recent version to ensure proper long term support. See the full changelog in the wiki [1] and the selection for 1.0.9 on the release page [2]. Both versions are considered stable and we recommend to update all productive installations of Roundcube with either one of these versions. Download them from GitHub via https://roundcube.net/download. As usual, don’t forget to backup your data before updating! Best, Thomas [1] https://github.com/roundcube/roundcubemail/wiki/Changelog#release-115 [2] https://github.com/roundcube/roundcubemail/releases/tag/1.0.9

1 0

Release candidate for 1.2 out now
by Thomas Bruederli 13 Apr '16

13 Apr '16

Hello folks Roundcube 1.2 is pretty much complete and after adding some last-minute improvements we just published a release candidate to give it another round of testing before we slap the 'stable' tag on it. We hereby invite you all to test the release candidate and report remaining bugs to our issue tracker. The most important features we added in 1.2 are: * PHP7 compatibility * PGP encryption in two flavours * Improved security measures to protect from brute-force and CSRF attacks See the full Changelog in our wiki: https://github.com/roundcube/roundcubemail/wiki/Changelog Download the packages or the signed source directly from Github: https://github.com/roundcube/roundcubemail/releases/tag/1.2-rc Please note that we recommend to test it on a separate environment. And don't forget to backup your data before installing it. Another note: with the upcoming stable release of 1.2.0 the old 1.0.x and the 1.1.x series will only receive important security fixes. Updates to these two branches are to be released soon. So stay tuned! Best, Thomas

1 0

Say goodbye to Trac
by Thomas Bruederli 01 Apr '16

01 Apr '16

Hello devs and list lurkers You all might have noticed the hickups we recently had with our Trac platform. Our Trac site was under heavy attack from spammers which put high load on the system and flooded the database with garbage. None of us really is a Trac expert and we failed at bringing the necessary measures in place to fight the spamming an to clean up the mess they caused. Adam, our volunteer admin who donated his private server for hosting the Trac site wants to resign from his duties which is fair and understandable. As a first action we deactivated user registration while we're looking for alternatives. That said, we're now looking at possible replacements for Trac or a successor for Adam who is willing to take the burden of hosting that crap. The most obvious - and already often requested - option is to migrate the tickets and the wiki pages into github. I already tested the import through the github API and that's a feasible option. But of course there are downsides: issue IDs cannot be kept and would be re-assigned. Also one cannot add tickets and comments with a date in the past. >From the 6.5K tickets we have in the database, there are ~ 200 open. I guess migrating these plus the resolved ones back to milestone 1.0.0 into github issues would give us a clean restart without loosing to much valuable data and - most importantly - without having to setup, host and protect our own tracker system. Anyway, please raise your voice with suggestions, concerns or offers if you have experience with such a post-Trac situation. Many thanks, Thomas

10 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev April 2016