unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Michal Nazarewicz" <mina86@mina86.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] lisp/server.el: Introduction of server-auth-key variable
Date: Fri, 29 Apr 2011 18:35:23 +0200	[thread overview]
Message-ID: <op.vupkc9wt3l0zgt@mnazarewicz-glaptop> (raw)
In-Reply-To: <jwvmxj9hw53.fsf-monnier+emacs@gnu.org>

On Fri, 29 Apr 2011 18:22:27 +0200, Stefan Monnier  
<monnier@iro.umontreal.ca> wrote:

>> +In some situations however, it can be difficult to share randomly
>> +generated password with remote hosts (eg. no shared directory),
>
> ssh/scp work fine for me.

Yes, but you'd have to send the key every time you connect to the remote
host and every time you restart emacs.  I thought about something like
that but decided that it'd be easier to just use a single shared key.

>> +so you can set the key with this variable and then copy server
>> +file to remote host (with possible changes to IP address and/or
>> +port if that applies).
>
> IIUC this only makes sense if you want to use a shared key that you keep
> for a "long" time (since the intention is to reduce the frequency of
> key-distribution).

Yep, that's my use-case.

> Now the server keys are sent in the clear over the network, so the
> security we provide is rather minimal.

In my case it's not actually an issue since I use OpenVPN to connect
to my remote host, not to say that in general this may decrease
security for some users should they choose to use it.

> OT1H that means your patch should be OK since we don't really have
> security anyway.  OTOH it means that it makes the security threat
> more serious.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michal "mina86" Nazarewicz    (o o)
ooo +-----<email/xmpp: mnazarewicz@google.com>-----ooO--(_)--Ooo--



  reply	other threads:[~2011-04-29 16:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 13:55 [PATCH] lisp/server.el: Introduction of server-auth-key variable Michal Nazarewicz
2011-04-29 11:30 ` Juanma Barranquero
2011-04-29 11:42   ` Michal Nazarewicz
2011-04-29 12:02     ` Juanma Barranquero
2011-04-29 12:43       ` Michal Nazarewicz
2011-04-29 14:34       ` Michal Nazarewicz
2011-04-30  6:39         ` Eli Zaretskii
2011-04-30 21:03           ` Richard Stallman
2011-04-30 22:24           ` Michal Nazarewicz
2011-04-29 16:22 ` Stefan Monnier
2011-04-29 16:35   ` Michal Nazarewicz [this message]
2011-04-29 17:09     ` Stefan Monnier
2011-04-30 14:31   ` Juanma Barranquero
2011-04-30 22:55     ` Michal Nazarewicz
2011-04-30 23:59       ` Juanma Barranquero
2011-05-01  0:44         ` Michal Nazarewicz
2011-05-01  0:58           ` Juanma Barranquero
2011-05-01  1:22             ` Michal Nazarewicz
2011-05-02 15:28 ` [PATCHv2] " Michal Nazarewicz

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=op.vupkc9wt3l0zgt@mnazarewicz-glaptop \
    --to=mina86@mina86.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).