unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mike Mattie <codermattie@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Does pclcvs support ssh protocol ?
Date: Thu, 21 Feb 2008 23:11:56 -0800	[thread overview]
Message-ID: <20080221231156.6ee15c74@reforged> (raw)
In-Reply-To: <20080222.075409.183050664.devel@pollock-nageoire.net>

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On Fri, 22 Feb 2008 07:54:09 +0100 (CET)
Pierre Lorenzon <devel@pollock-nageoire.net> wrote:

> From: Michael Hoffman <b3i4old02@sneakemail.com>
> Subject: Re: Does pclcvs support ssh protocol ?
> Date: Thu, 21 Feb 2008 20:31:54 +0000
> 
> > Pierre Lorenzon wrote:
> > 
> > >   Notice that I still do not have the answer to my question :
> > >   "yes or not is this password transaction implemented in
> > >   pcl-cvs like in tramp ?"
> > 
> > Now the question has changed.
> 
> 
>   Not really ! 
> 
>   Pierre
> 
> 
> 

The answer is clearly ssh-agent. There are a large number of security issues regarding keys,
memory locking, timed expiration, secure entry, etc. Emacs doesn't need to jump through all these
hoops when ssh-agent,pin-entry,gpg do this sort of thing correctly with a robust code-base.

I can't even imagine why someone would want to constantly re-enter the password anyways.

If you were interested in security you would not want your security critical components exposed
in a monolith like Emacs that cannot enforce memory privileges.

Hammering away at this issue is asinine, since you do not have a point. Thanks to these fancy
link-loader gizmos, and those operating system thingies we can distribute functionality across
process boundaries with IPC. Welcome to the revolution.

Cheers,
Mike Mattie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-22  7:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  5:36 Does pclcvs support ssh protocol ? Pierre Lorenzon
2008-02-21 11:38 ` Michael Hoffman
2008-02-21 16:02   ` Pierre Lorenzon
2008-02-21 16:15     ` Michael Albinus
2008-02-21 16:21     ` Michael Hoffman
2008-02-21 20:15       ` Pierre Lorenzon
2008-02-21 20:31         ` Michael Hoffman
2008-02-22  6:54           ` Pierre Lorenzon
2008-02-22  7:11             ` Mike Mattie [this message]
2008-02-22  8:39               ` Enlarging the question Was: " Pierre Lorenzon
2008-02-22  9:19                 ` Thierry Volpiatto
2008-02-23  2:00                   ` Xavier Maillard
2008-02-23  2:00                   ` Xavier Maillard
     [not found]                   ` <mailman.7811.1203734034.18990.help-gnu-emacs@gnu.org>
2008-02-24  7:42                     ` Tim X
2008-03-19  1:00                       ` Xavier Maillard
     [not found]                 ` <mailman.7780.1203672972.18990.help-gnu-emacs@gnu.org>
2008-02-23  1:29                   ` Tim X
2008-02-23  6:34                   ` Stefan Monnier
     [not found]               ` <mailman.7778.1203669624.18990.help-gnu-emacs@gnu.org>
2008-02-23  1:21                 ` Tim X
     [not found] ` <mailman.7737.1203593911.18990.help-gnu-emacs@gnu.org>
2008-02-22  1:19   ` Tim X
2008-02-22  2:00 ` Xavier Maillard
2008-02-22  7:16   ` Pierre Lorenzon

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080221231156.6ee15c74@reforged \
    --to=codermattie@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).