From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Password protection
Date: Thu, 30 Sep 2010 19:19:07 +0200 [thread overview]
Message-ID: <87iq1nw3n8.fsf@gmx.de> (raw)
In-Reply-To: <8739sr8c9h.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 30 Sep 2010 10:46:50 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> MA> Hmm. Just a rough idea: what a about a new lisp object "password"? It
> MA> can be created only via an (interactive) C-level function, and another
> MA> C-level function returns the carried string. On lisp level, the value
> MA> is available only as hash string of the password itself. By this,
> MA> functions like `eq' or `string-equal' could still be applied.
>
> MA> C-level functions, visible in lisp (like `process-send-string' or
> MA> `dbus-call-method'), could be tought to accept a password *or* a string
> MA> as parameter.
>
> So only a process or C code can see or set the real value of a secret
> token? That seems like a great idea.
Btw: we should not overestimate the kind of protection. Everybody can
install an asynchronous process, send the password object via
process-send-string, and read the plain password in the process
buffer. Everything on Elisp level.
> Ted
Best regards, Michael.
next prev parent reply other threads:[~2010-09-30 17:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:17 Lars Magne Ingebrigtsen
2010-09-28 14:43 ` Richard Riley
2010-09-29 14:01 ` Lars Magne Ingebrigtsen
2010-09-28 14:46 ` Julien Danjou
2010-09-28 14:50 ` Ted Zlatanov
2010-09-29 14:04 ` Lars Magne Ingebrigtsen
2010-09-28 14:47 ` Ted Zlatanov
2010-09-29 14:07 ` Lars Magne Ingebrigtsen
2010-09-29 16:56 ` Charles Philip Chan
2010-09-29 17:15 ` Ted Zlatanov
2010-09-29 19:27 ` Lars Magne Ingebrigtsen
2010-09-29 19:51 ` Ted Zlatanov
2010-09-29 20:35 ` Michael Albinus
2010-09-29 20:58 ` Ted Zlatanov
2010-09-30 3:32 ` Michael Albinus
2010-09-30 15:46 ` Ted Zlatanov
2010-09-30 17:19 ` Michael Albinus [this message]
2010-09-30 16:25 ` Lars Magne Ingebrigtsen
2010-09-30 16:43 ` Ted Zlatanov
2010-09-30 16:47 ` Lars Magne Ingebrigtsen
2010-09-30 17:07 ` Ted Zlatanov
2010-09-30 17:17 ` Lars Magne Ingebrigtsen
2010-09-30 17:45 ` Ted Zlatanov
2010-09-30 17:51 ` Lars Magne Ingebrigtsen
2010-09-30 19:11 ` Michael Albinus
2010-09-30 17:13 ` Michael Albinus
2010-09-30 17:16 ` Michael Albinus
2010-09-29 21:38 ` Lars Magne Ingebrigtsen
2011-02-25 22:18 ` Ted Zlatanov
2011-03-05 11:53 ` Lars Magne Ingebrigtsen
2011-03-07 17:27 ` Ted Zlatanov
2010-09-28 15:02 ` David Engster
2010-09-29 2:28 ` Daniel Pittman
2010-09-29 4:39 ` Richard Riley
2010-09-29 5:58 ` Daniel Pittman
2010-09-29 6:42 ` Richard Riley
2010-09-29 8:54 ` Gijs Hillenius
2010-09-29 9:07 ` Richard Riley
2010-09-29 10:23 ` Gijs Hillenius
2010-09-29 9:51 ` Tassilo Horn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iq1nw3n8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).