emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#30246: closed (25.2.50; auth-source does not suppo


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#30246: closed (25.2.50; auth-source does not support creation or deletion with secrets provider)
Date: Thu, 13 Sep 2018 14:11:01 +0000

Your message dated Thu, 13 Sep 2018 16:09:54 +0200
with message-id <address@hidden>
and subject line Re: bug#30246: 25.2.50; auth-source does not support creation 
or deletion with secrets provider
has caused the debbugs.gnu.org bug report #30246,
regarding 25.2.50; auth-source does not support creation or deletion with 
secrets provider
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30246: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30246
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.2.50; auth-source does not support creation or deletion with secrets provider Date: Wed, 24 Jan 2018 16:56:26 -0800
auth-source does not support saving secrets with the Secrets API
backend.  This reduces the usefulness of auth-source significantly
since keychains that provide secure secret storage using the API are
standard on many GNU/Linux distributions (e.g., gnome-keyring on
Ubuntu).

(auth-source-search :type 'secrets :max 1
                    :host "localhost"
                    :user "user"
                    :create '(secret user host))

Debugger entered--Lisp error: (cl-assertion-failed ((not create) "The
Secrets API auth-source backend doesn't support creation yet"))
  cl--assertion-failed((not create) "The Secrets API auth-source
backend doesn't support creation yet" nil nil)
  auth-source-secrets-search(:backend
[eieio-class-tag--auth-source-backend secrets "Login" t t t nil
auth-source-secrets-create auth-source-secrets-search] :type secrets
:max 1 :require nil :create (secret user host) :delete nil :type
secrets :max 1 :host "localhost" :user "user" :create (secret user
host))
  apply(auth-source-secrets-search :backend
[eieio-class-tag--auth-source-backend secrets "Login" t t t nil
auth-source-secrets-create auth-source-secrets-search] :type secrets
:max 1 :require nil :create (secret user host) :delete nil (:type
secrets :max 1 :host "localhost" :user "user" :create (secret user
host)))
  auth-source-search-backends(([eieio-class-tag--auth-source-backend
secrets "Login" t t t nil auth-source-secrets-create
auth-source-secrets-search]) (:type secrets :max 1 :host "localhost"
:user "user" :create (secret user host)) 1 (secret user host) nil nil)
  auth-source-search(:type secrets :max 1 :host "localhost" :user
"user" :create (secret user host))
  eval((auth-source-search :type (quote secrets) :max 1 :host
"localhost" :user "user" :create (quote (secret user host))) nil)
  elisp--eval-last-sexp(nil)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  #<subr call-interactively>(eval-last-sexp nil nil)
  apply(#<subr call-interactively> eval-last-sexp (nil nil))
  address@hidden(#<subr
call-interactively> eval-last-sexp nil nil)
  apply(address@hidden #<subr
call-interactively> (eval-last-sexp nil nil))
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)



--- End Message ---
--- Begin Message --- Subject: Re: bug#30246: 25.2.50; auth-source does not support creation or deletion with secrets provider Date: Thu, 13 Sep 2018 16:09:54 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
Version: 27.1

Michael Albinus <address@hidden> writes:

Hi Allen,

>>> Could you test it by any chance in Emacs 27? If not, I'll close the
>>> bug. You could still report later if it doesn't work as expected.
>>
>> It looks like secret creation works now, however I can't seem to
>> retrieve the secret.  I can file a separate bug for that if you want.
>
> Yes, please do.

There's now bug#32725 for that problem. I'm closing this bug, therefore.

Best regards, Michael.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]