Dev June 2012

dev@lists.roundcube.net

13 participants
6 discussions

keep-alive changes
by A.L.E.C 13 Nov '12

13 Nov '12

Digging into session issues I've found this keep-alive thing a little bit overcomplicated and unclear. The keep-alive setting handles two things: session keeping and new-mail checking. Some plugins also bind to keep-alive to do some recurring actions (e.g. to display calendar alarms, etc.). I think we should split these functionalities. So keep-alive action should be used only for session keeping. In such case we need to execute keep-alive action only after some inactivity time (e.g. session_lifetime - 1min [or 5%]). It means timer should be resetted on every reequest. Also it means we don't need a separate config option, because the interval would be calculated from session_lifetime. For session_lifetime=0 there would be no keep-alive requests. Another thing is recurring check for new-mail. This would work as is, but... see below. Last but not least. We should provide some "global" recurring action which would work across all tasks so, plugins could bind to it. One "global" action to minimize session race-conditions when few plugins will create their own recurring requests on the same time. In mail task we could "bind" our check-recent action to this global action. In my opinion this would be a much clearer solution and would give as some additional possibilities: - possibility to disable recurring checks (for new mail etc.) at all, - better overall performance because keep-alive out of mail task will be executed less frequently I think also, we could rename keep_alive option description ("Check for new messages on") into something like "Update system state (check for new mail, etc.) on", and move it to User Interface section, so we could use it as our global action interval. ps. I'm not sure we should change draft auto-save interval in any way to fit into this. For simplicity would be nice to use the same global action and its interval. -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --------------------------------------------------- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl

3 8

OpenPGP in JavaScript in Roundcube in round in round in round...
by Niklas 13 Jul '12

13 Jul '12

Hello :-) I've been working on implementing OpenPGP.js in Roundcube for the past couple of days. It's still an unfinished project in development, but since there's such high demand for the result I ought I'd ask you guys for some early feedback. For those of you who don't know: OpenPGP.js is a fork of the previous GPG4Browsers. The intent is to port all OpenPGP functionality into JavaScript so that third party software isn't required for PGP activity. It uses HTML5 web storage and standard PKI keyrings (private keys excluded). So far the plugin, rc_openpgpjs, has a "temporary"(?) user interface for key management and selection. Its consciously using a pretty rough UI at the moment because the new design for Roundcube is just around the corner, but just not finished enough yet to start working on. Also the Enigma plugin interface looked in trouble in Larry. Speaking of Enigma: I'm sure someone will ask why I extend that instead. With all due respect to its authors and fans, Enigma has been stuck in development for 2 years, and PGP support has been planned for Roundcube for 6 years. I'm not sure whether Enigma is really relevant or not. Also I can not support a plugin that implements encryption as a server side solution. The main goal of encryption is to ensure that the data can not be accessed by unauthorized people. I believe that people hosting other people's mail should be treated as unauthorized, and giving private keys away to somebody else really fights against the entire purpose. And then arises the exact same problem that Hushmail users are experiencing: http://www.wired.com/threatlevel/2007/11/encrypted-e-mai/ Even though most Roundcube users probably host their own email I'm quite sure most people don't have problems with a client sided solution instead. That said, I'm not opposed to the Enigma plugin in any way. I was only too lazy to bother learning its structure and layout, which turned out to not be entirely supported by the Larry design. I wouldn't mind a merge later on. Anyhow! Check it out, and tell me what you think. I strongly welcome UI recommendations, patches or any other tip about how I should progress. It's still in early development, but most of the key management features are implemented and so is the decryption of emails. Nothing about the UI is finished. https://github.com/qnrq/rc_openpgpjs Cheers! /Nik

5 7

Poll: About Larry - the new skin for Roundcube
by Thomas Bruederli 29 Jun '12

29 Jun '12

Dear Roundcube users and lovers Some controverse questions about the new skin are asking for your votes. Please visit our Google+ page and +1 your favorite options in the comments below the post: https://plus.google.com/b/117198963145106512069/117198963145106512069/posts… We believe in democracy. Thanks for your votes! Cheers, Thomas

11 11

session errors
by Cor Bosman 24 Jun '12

24 Jun '12

Hey all, last few weeks im getting flooded with session timeout complaints. The people i checked have so far been logging in with IPv6. Could there be an issue with IPv6 and sessions? Im running 0.7-svn upto the latest checkin. Cor

2 1

Larry - Few Issues
by Rosali 12 Jun '12

12 Jun '12

Hi all, in messagepreview.html the template object "messageFullHeaders" is missing. Is this intended? It works well if I insert right below ... <roundcube:object name="messageHeaders" id="preview-allheaders" class="headers-table" addicon="/images/addcontact.png" exclude="subject,replyto" /> ... <roundcube:object name="messageFullHeaders" id="full-headers" /> I noticed that the support link in headers.html is configurable. But the link still appears when inserting into main.inc.php ... $rcmail_config['support_url'] = false; Regards, R.

1 0

cookie opt-in
by Phil Weir 11 Jun '12

11 Jun '12

Hi, An EU law requiring websites to obtain opt-in consent from website users before any non-essential cookies back be placed on their computer recently came into force in the UK. Roundcube uses cookies for things like remember the position of the splitters on the mail screen. This isn't essential to the operation of the site and so consent must be sort from the user before these cookies can be saved on their computer. I have created a very simple plugin which displays a banner to the user asking them if they wish to use cookies or not and if they choose not then it disables the JavaScript cookie methods. It also adds a new option in the general settings page to allow the user to change their cookie settings any time they want. This plugin blocks cookies created via JavaScript. The only JavaScript cookie not blocked by this plugin is the one created by googiespell since that uses slight different methods of the rest of RC. These are the only cookies in the RC core which appear to be non-essential. There is one session cookie created in the PHP as part of the security that is essential and so exempt from opt-in. This is only a first go at a cookie opt-in system for RC and I'm sure it's not perfect, any feedback welcome. I am wondering it might be better to simply give an "accept and close" option rather than the choice of accepting or blocking. Phil

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev June 2012