On Wed, 2011-10-19 at 08:24 +0200, Milan Crha wrote:
> Hi,
> I cannot find the thread where this was discussed, I'm sorry, but after
> few days I found why this behaviour is pretty bad and why the
> evolution-alarm-notify didn't ask for passwords. My usecase is pretty
> simple, and I believe
On Wed, 2011-10-19 at 08:24 +0200, Milan Crha wrote:
> I cannot find the thread where this was discussed, I'm sorry, but after
> few days I found why this behaviour is pretty bad and why the
> evolution-alarm-notify didn't ask for passwords. My usecase is pretty
> simple, and I believe there are m
On Wed, 2011-10-19 at 08:36 -0400, Matthew Barnes wrote:
> > My question is whether there can be done any better way of coping with
> > this, because having the password prompts (there are two pilled,
> > actually) after each and every login is just a bad experience, from my
> > point of view.
> (G
On Wed, 2011-10-19 at 08:36 -0400, Matthew Barnes wrote:
> One thing I wanted to add after all this account rewrite stuff is done
> (maybe for 3.6) is support for VPN state. My thought was any place in
> Evolution where you would enter host and port information there would
> also be a check box it
On Wed, 2011-10-19 at 16:57 +0530, Chenthill wrote:
> Would it not be possible to store the password in gnome-keyring and be
> shared. The other providers work this way, alarm-daemon would start
> the authenticated calendars if it finds that the passwords is stored
> gnome-keyring. It would also ch
On Sat, 2011-10-15 at 11:18 -0400, Matthew Barnes wrote:
> Just a heads up that I've changed Camel's authentication API to factor
> out the password loop that each and every provider currently replicates
> for themselves. Turns out they all have the same basic logic flow.
>
> These changes make p
On Thu, 2011-10-20 at 01:14 +0100, David Woodhouse wrote:
> > The "mechanism" argument refers to the user's preferred SASL
> mechanism.
> > This will usually be taken from "url->authmech"
>
> That's fine at the moment, but the fact that we have to explicitly
> choose *one* mechanism in advance oug