From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: David Brown <dmlb2000@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.14.tar.bz2 permissions
Date: Sun, 27 Nov 2005 01:38:25 +0000 [thread overview]
Message-ID: <200511270138.25769.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <9c21eeae0511261713vacf13f5u5fdf19711635a381@mail.gmail.com>
On Sunday 27 November 2005 01:13, David Brown wrote:
> > David, it'd probably help if you listed all of the affected files, then
> > people can explain themselves and/or correct the permissions.
> >
> > I personally think that your point is valid and security should be
> > considered when packing the kernel sources. It might even be possible for
> > Linus's tarball script to remove global write permissions.
>
> Okay but it's kinda big here's how I did it.
>
> # for file in `find *` ; do if ls -l $file | grep -q '^.....w..w.' ;
> then ls -d $file ; fi ; done | wc -l
> 19552
> # find * | wc -l
> 19552
>
> seems to be all of them :\
>
> I'll attach the file list
Sure enough, I can confirm this.
I don't seem to have to provide --no-same-permissions to tar to get umask to
affect the permissions of extracted files, so my files are fine on-disc.
What disturbs me more is the number of people using insecure umasks before
checking files in! When does a text file really want to be a+w?
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2005-11-27 1:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c21eeae0511261352u33e32343wf50062ba3038ef06@mail.gmail.com>
2005-11-26 21:58 ` David Brown
2005-11-26 22:19 ` Norbert van Nobelen
2005-11-26 22:27 ` David Brown
2005-11-26 22:36 ` Michael Frank
2005-11-26 22:41 ` David Brown
2005-11-26 22:53 ` Michael Frank
2005-11-26 23:11 ` David Brown
2005-11-27 8:23 ` Jan Engelhardt
2005-11-27 5:57 ` Willy Tarreau
2005-11-26 23:12 ` Nish Aravamudan
2005-11-26 23:15 ` David Brown
2005-11-26 23:46 ` Alistair John Strachan
[not found] ` <9c21eeae0511261713vacf13f5u5fdf19711635a381@mail.gmail.com>
2005-11-27 1:38 ` Alistair John Strachan [this message]
2005-11-27 1:46 ` Nish Aravamudan
2005-11-27 1:51 ` Alistair John Strachan
2005-11-27 1:56 ` David Brown
2005-11-27 2:27 ` Nish Aravamudan
2005-11-27 2:38 ` David Brown
2005-11-27 6:09 ` Willy Tarreau
2005-11-27 9:22 ` David Brown
2005-11-27 10:57 ` Willy Tarreau
2005-11-27 14:39 ` Kyle Moffett
2005-11-27 16:30 ` Jesper Juhl
2005-11-27 1:51 ` David Brown
2005-11-27 6:07 ` Willy Tarreau
2005-11-27 1:47 ` David Brown
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=200511270138.25769.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=dmlb2000@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®