unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Glenn Morris <rgm@gnu.org>
Cc: rms@gnu.org, dkg@fifthhorseman.net, emacs-devel@gnu.org
Subject: Re: [dkg@fifthhorseman.net: security: url-cookies file stored world-readable, allowing session hijacking]
Date: Mon, 10 Dec 2007 01:19:16 -0500	[thread overview]
Message-ID: <87ve776pi3.fsf@squeak.fifthhorseman.net> (raw)
In-Reply-To: <08bq90odfi.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat\, 08 Dec 2007 20\:38\:09 -0500")


[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]

On Sat 2007-12-08 20:38:09 -0500, Glenn Morris wrote:

> dkg wrote:
>
>> I just noticed that ~/.url/cookies was world-readable, and its parent
>> directory was world-readable, exposing the cookies emacs held to the
>> outside world, which allows for a session hijacking attack.
>
> I can fix this. Should ~/.url be private, or just certain files within
> it (cookies, history, what else)?

i would suspect that history should also be private -- URLs visited
often hold information that you might not want others to see.  i'm not
sure what else gets placed in that directory, so i don't know if the
directory itself should be mode 0700 or not.

Thanks for the followup,

       --dkg

[-- Attachment #1.2: Type: application/pgp-signature, Size: 826 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

      reply	other threads:[~2007-12-10  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 18:43 [dkg@fifthhorseman.net: security: url-cookies file stored world-readable, allowing session hijacking] Richard Stallman
2007-12-09  1:38 ` Glenn Morris
2007-12-10  6:19   ` Daniel Kahn Gillmor [this message]

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=87ve776pi3.fsf@squeak.fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    --cc=rms@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. 
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).