diff options
author | Jeffrey Stedfast <fejj@ximian.com> | 2003-02-15 04:11:53 +0800 |
---|---|---|
committer | Jeffrey Stedfast <fejj@src.gnome.org> | 2003-02-15 04:11:53 +0800 |
commit | 6545e80191916bea8705e0d4feb0e00192b36905 (patch) | |
tree | 51179e91f5a910f964e8db861e626d76e1bb2c5d /camel/camel-session.c | |
parent | 4d98f14113b8cdf72226361d6904a6829a15f0e7 (diff) | |
download | gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar.gz gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar.bz2 gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar.lz gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar.xz gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.tar.zst gsoc2013-evolution-6545e80191916bea8705e0d4feb0e00192b36905.zip |
Same as the gpg and pkcs7 contexts.
2003-02-14 Jeffrey Stedfast <fejj@ximian.com>
* camel-smime-context.c (smime_get_password): Same as the gpg and
pkcs7 contexts.
* camel-sasl-popb4smtp.c (popb4smtp_challenge): Updated for
camel_session_get_password().
* camel-pkcs7-context.c (get_password): Same as the gpg code.
* camel-gpg-context.c (gpg_ctx_parse_status): Updated for
camel_session_get_password().
* providers/smtp/camel-smtp-transport.c (smtp_connect): No need to
set USER_CANCEL exception here as it is done by
camel_session_get_password(). Also updated for the new
get_password() API change.
* providers/imap/camel-imap-store.c (imap_auth_loop): Updated for
camel_session_get_password() changes. We don't need to play the
"bad passwd" game here too, do we? Bah, probably should but I
don't feel like it for now. Maybe when we rewrite the IMAP
provider.
* camel-session.c (camel_session_get_password): Now takes a
'reprompt' argument that will force user-input to be given even if
we have the passwd cached.
* providers/pop3/camel-pop3-store.c (pop3_connect): Instead of
uncaching the passwd after we receive a -ERR from the POP server,
set 'reprompt' to TRUE to force user-input for the next password
prompt (ie, make sure the front-end knows not to just return the
cached value). The front-end can then decide to fill-in the
user-input field with the last passwd that the user supplied.
(pop3_try_authenticate): Now takes a reprompt argument which we
pass into camel_session_get_password().
svn path=/trunk/; revision=19912
Diffstat (limited to 'camel/camel-session.c')
-rw-r--r-- | camel/camel-session.c | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/camel/camel-session.c b/camel/camel-session.c index c4634b45dd..1d45e9661b 100644 --- a/camel/camel-session.c +++ b/camel/camel-session.c @@ -584,6 +584,7 @@ camel_session_get_storage_path (CamelSession *session, CamelService *service, * camel_session_get_password: * @session: session object * @prompt: prompt to provide to user + * @reprompt: TRUE if the prompt should force a reprompt * @secret: whether or not the data is secret (eg, a password, as opposed * to a smartcard response) * @service: the service this query is being made by @@ -607,14 +608,15 @@ camel_session_get_storage_path (CamelSession *session, CamelService *service, **/ char * camel_session_get_password (CamelSession *session, const char *prompt, - gboolean secret, CamelService *service, - const char *item, CamelException *ex) + gboolean reprompt, gboolean secret, + CamelService *service, const char *item, + CamelException *ex) { g_return_val_if_fail (CAMEL_IS_SESSION (session), NULL); g_return_val_if_fail (prompt != NULL, NULL); g_return_val_if_fail (item != NULL, NULL); - - return CS_CLASS (session)->get_password (session, prompt, secret, service, item, ex); + + return CS_CLASS (session)->get_password (session, prompt, reprompt, secret, service, item, ex); } |