Re: ports security (was: fetch extension - use local filename from content-disposition header)
- From: Ádám Szilveszter <adamsz@xxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 12:56:48 +0100 (CET)
On Pén, December 30, 2005 11:20 am, Simon L. Nielsen wrote:
> I don't remember seeing it discussed. Fetching as a non-privileged
> user seems like a really good idea to me. Building as non-root would
> be nice, but doesn't really buy you much security wise
I would be interested to hear why you think this. (I am aware of the
problems at install stage)
> (and will
> possibly break at least some programs that makes silly assumptions
> about build as root).
Yes, although we do not know how many programs are affected by this in
reality. Eg Gentoo, AFAIK does not build as root.
> Note that both of these features are somewhat paranoid security
> features, and the risk of getting compromised by either is much
> smaller than getting compromised by some other much more simple
> vulnerability.
I think that running fetch as root is really an unnecessary risk to the
system for the same reason as running a web browser or reading mail as
root is. For some, this risk is bearable. But it is not security best
practice by any stretch.
Regards
Sz.
------------------------------------------------------------------------
Telcsi.hu - A legújabb csengőhangok menő slágerekkel >>>
Polifónikus és normál csengőhangok >>> Animált és normál háttérképek >>>
MP3 effektek >>> http://www.telcsi.hu/index.php?prefix=VM
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- fetch extension - use local filename from content-disposition header
- From: Martin Cracauer
- Re: fetch extension - use local filename from content-disposition header
- From: Barney Wolff
- Re: fetch extension - use local filename from content-disposition header
- From: Sean Bryant
- Re: fetch extension - use local filename from content-disposition header
- From: Pawel Worach
- Re: fetch extension - use local filename from content-disposition header
- From: Martin Cracauer
- Re: fetch extension - use local filename from content-disposition header
- From: Barney Wolff
- Re: fetch extension - use local filename from content-disposition header
- From: Ádám Szilveszter
- Re: fetch extension - use local filename from content-disposition header
- From: Eygene A. Ryabinkin
- Re: ports security (was: fetch extension - use local filename from content-disposition header)
- From: Simon L. Nielsen
- fetch extension - use local filename from content-disposition header
- Prev by Date: Re: fetch extension - use local filename from content-disposition header
- Next by Date: Re: fetch extension - use local filename from content-disposition header
- Previous by thread: Re: ports security (was: fetch extension - use local filename from content-disposition header)
- Next by thread: Re: fetch extension - use local filename from content-disposition header
- Index(es):
Relevant Pages
|
|
