Is it just me, or did someone actually implement set-uid scripts? I've
proposed some silly things over the decades (my favourite is stty()
working on things other than terminals, and guess what, we got ioctl()
etc) but I have a vague recollection of this...
The trouble is, I've worked with dozens of Unix-based vendors over the
years (some good, some not so much) and so I've lost track of all the
stupidity that I've seen.
ObAnecdote: Just about every Unix vendor went belly-up shortly after I
left them (under various circumstances), because the waste-of-space middle
managers simply did not appreciate the importance of having a Unix guru
on board if you're in the game of selling Unix boxen.
I'd happily name them, but I think the principals are still alive :-)
-- Dave
Read and write permission were common ideas--even part of
the Atlas paging hardware that was described before 1960.
The original concept of time-sharing was to give a virtual
computer to each user. When it became clear that sharing
was an equally important aspect, owner/other permissions
arose. I believe that was the case with Multics.
Owner/other permissions were in PDP-11 Unix from the start.
Group permissions arose from the ferment of daily talk in
the Unix lab. How might the usual protections be extended
to collaborative projects? Ken and Dennis deserve credit
for the final implementation. Yet clean as the idea of groups
was, it has been used only sporadically (in my experience).
Execute permission (much overloaded in Unix) also dates
back to the dawn of paging. One Unix innovation, due to
Dennis, was the suid bit--the only patented feature in
the Research system. It was instantly adopted for
maintaining the Moo (a game now sold under the name
"Master Mind") league standings table.
One trouble with full-blown ACLs as required by NSA's
Orange Book, is obscurity. It is hard (possibly NP-
complete) to analyze the actual security of an ACL
configuration.
A common failing of Unix administration was a proliferation
of suid-root programs, e.g. mail(1). I recall one system
that had a hundred such programs. Sudo provided a way
station between suid and ACLs.
Doug
> From: Arthur Krewat
> there's the setuid bit on directories - otherwise known as the sticky
> bit.
Minor nit; in V6 at least (not sure about later), the 'sticky' bit was a
separate bit from SUID and SGID. (When set on a pure/split object file, it
told the OS to retain the text image on the swap device even when no active
process was using it. Hence the name...)
Noel
Hi all, I'm chasing the Youtube video of the PDP-7 at Bell Labs where
people are using it to draw circuit schematics. This seems to show
the Graphics-2 module that, I believe, was built at the Labs. Can
someone e-mail the URL? I've done some grepping but I haven't found it yet.
Thanks, Warren
Hello Unix enthusiasts.
I'd like to know who or the group of people behind implementing this
filesystem permission system.
Since we are using this system for nearly 40 years and it addresses all the
aspects of the permission matter without any hustle.
I'm inspired to know who/how came up with this theory?
Also if it derived from somewhere else or If there's an origin story about
this, it would be worth to share.
Cheers.
Stephan
--
No When
I was talking about DMERT today and Larry McVoy was wondering if it slipped
out in any fashion.
I believe there were official trainers as well as a production emulator
that ran it on Solaris/SPARC. I have never seen them anywhere. Old phone
phreaks I’m acquainted with had illicit access. Does anyone know if source
or the trainer or emulator are tangible?
I enjoyed the BTSJ on DMERT as much as the Unix articles. Highly recommend
reading.
Regards,
Kevin
Does anyone know where the 386 port from PCC came from?
While trying to build a Tahoe userland for the i386, it seems that everything was built with GCC…
Was there a PCC for the i386 around ’88-90? It seems after the rapid demise of the Tahoe/Harris
HCX-9 that the non Vax/HCX-9 platforms had moved to GCC?
Also anyone know any good test software for LIBC? I’ve been tracing through some
strange issues rebuilding LIBC from Tahoe, where I had to include some bits from
Reno to get diropen to actually work. I would imagine there ought to have been some
platform exercise code to make sure things were actually working instead of say
building as much as you can, and playing rogue for a few hours to make sure
its stable enough.
> BSD[Ii] got in trouble with AT&T for their sales number, which was
> 1-800-ITS-UNIX. I don't know if they ever got officially sued or not.
There was a joke that MIT should have sued them too, for violating their
trademark on ITS.
-- Richard
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.