Nice picture I've not seen before from the Bell Labs UNIX room
-
@aka_pugs @lauren @SteveBellovin @dougmerritt software security. This was maybe just after Building Secure Software was published...
@aka_pugs @lauren @SteveBellovin @dougmerritt I had the book cover of K&R with a big Do Not symbol superimposed. I can dig the archive if you care enough.
-
@aka_pugs @lauren @SteveBellovin @dougmerritt I had the book cover of K&R with a big Do Not symbol superimposed. I can dig the archive if you care enough.
@noplasticshower
If it's not too much trouble, that would be interesting and amusing. -
@noplasticshower
If it's not too much trouble, that would be interesting and amusing.@aka_pugs @lauren @SteveBellovin @dougmerritt will take a quick look tomorrow. I think it is in the post TAR days anyway.
-
@aka_pugs I used to hang around MH1127 whenever I was in town. I've told the story of sitting there at a terminal connected back to UCLA and I ran into a tough C declaration problem. DMR was sitting right next to me. So I asked his advice. He gave me an elegant solution. The closest I ever got to getting advice from a god.
@lauren @aka_pugs My lab once bought an off-brand machine to run their variant of 4.xBSD. Their compiler and/or hardware set the result to zero on an integer overflow—which is acceptable for int but not for unsigned, and the latter was causing me problems: the C language definition was quite explicit about what the result should be. I filed a bug report; their response was, in essence, WONT FIX. I forwarded the correspondence to Dennis—and a patch came out in a very few days…
-
@lauren @aka_pugs My lab once bought an off-brand machine to run their variant of 4.xBSD. Their compiler and/or hardware set the result to zero on an integer overflow—which is acceptable for int but not for unsigned, and the latter was causing me problems: the C language definition was quite explicit about what the result should be. I filed a bug report; their response was, in essence, WONT FIX. I forwarded the correspondence to Dennis—and a patch came out in a very few days…
@lauren @aka_pugs @SteveBellovin voice of god
-
@aka_pugs @lauren I once got him to nod the go ahead to allow everyone at a Bell Labs talk I gave to chant, "C is bad...C is bad.". He had a wry beautific smile on his face.
@SteveBellovin were you there?
@noplasticshower @aka_pugs @lauren @cigitalgem I don't think so. Amazon says that that book came out in 2001, well after the AT&T/Lucent split, and I was with AT&T (as was Avi). Ches was with Lucent (or Lumeta) until around '99, I think, when he also moved to AT&T.
-
@aka_pugs @lauren I once got him to nod the go ahead to allow everyone at a Bell Labs talk I gave to chant, "C is bad...C is bad.". He had a wry beautific smile on his face.
@SteveBellovin were you there?
@aka_pugs @lauren @SteveBellovin I think I wrote my first C program in 1989. I came up through applesoft basic, 6502 assembly, and turbo pascal. Then I became a serious scheme weenie because of Dan friedman. C followed that.
-
@noplasticshower @aka_pugs @lauren @cigitalgem I don't think so. Amazon says that that book came out in 2001, well after the AT&T/Lucent split, and I was with AT&T (as was Avi). Ches was with Lucent (or Lumeta) until around '99, I think, when he also moved to AT&T.
@aka_pugs @lauren @cigitalgem @SteveBellovin must have pre-dated the book. I will go look.
I know I gave a big talk at Microsoft about swsec before the book was even done. I think @jdp23 had something to do with that. Met the original SWI team run by Jason Garms before the bill memo.
And I know it was before Ches maps
-
Nice picture I've not seen before from the Bell Labs UNIX room.
Joe Condon and Ken Thompson talking about Belle, their chess machine. Dennis Ritchie all the way in the back. Not sure who is in the middle.
Happy Birthday to Ken!@aka_pugs I think the one in the middle is Gerard Holzmann, but it's hard to be certain.
-
@lauren @aka_pugs My lab once bought an off-brand machine to run their variant of 4.xBSD. Their compiler and/or hardware set the result to zero on an integer overflow—which is acceptable for int but not for unsigned, and the latter was causing me problems: the C language definition was quite explicit about what the result should be. I filed a bug report; their response was, in essence, WONT FIX. I forwarded the correspondence to Dennis—and a patch came out in a very few days…
@SteveBellovin @lauren @aka_pugs On the other coast - at UCLA, mid 1970s - I think it was Mark Kampe, Carl Switzky, and I who submitted a bid to port Unix to UCLA's differential analyzer.
Of course it was impossible, but the administration didn't seem to get the joke.
I am quite unclear what signed or unsigned integers would be on that machine, much less how they would overflow.
-
@SteveBellovin @lauren @aka_pugs On the other coast - at UCLA, mid 1970s - I think it was Mark Kampe, Carl Switzky, and I who submitted a bid to port Unix to UCLA's differential analyzer.
Of course it was impossible, but the administration didn't seem to get the joke.
I am quite unclear what signed or unsigned integers would be on that machine, much less how they would overflow.
@karlauerbach @lauren @aka_pugs Administrative types could be remarkably clueless. My boss—a techie—once asked, "Steve, where is the XXX package?" "On disk, of course." "Which disk?" I told him. "What tracks on the disk?" "How would I know, and why does it matter? Do you want me to dump the VTOC [Volume Table of Contents] to find out?" He showed me the metal property sticker he'd been sent by the clueless—it was something we'd purchased, so we had to put a property label on it…
-
Nice picture I've not seen before from the Bell Labs UNIX room.
Joe Condon and Ken Thompson talking about Belle, their chess machine. Dennis Ritchie all the way in the back. Not sure who is in the middle.
Happy Birthday to Ken!@aka_pugs ... and a row of Tektronix graphics terminals?
-
@SteveBellovin @lauren @aka_pugs On the other coast - at UCLA, mid 1970s - I think it was Mark Kampe, Carl Switzky, and I who submitted a bid to port Unix to UCLA's differential analyzer.
Of course it was impossible, but the administration didn't seem to get the joke.
I am quite unclear what signed or unsigned integers would be on that machine, much less how they would overflow.
@karlauerbach @SteveBellovin @aka_pugs I used to walk by that differential analyzer pretty much every day coming onto campus up to the computing center. It was in quite a few films as I recall. I think it's at the Smithsonian now.
-
@aka_pugs @lauren @cigitalgem @SteveBellovin must have pre-dated the book. I will go look.
I know I gave a big talk at Microsoft about swsec before the book was even done. I think @jdp23 had something to do with that. Met the original SWI team run by Jason Garms before the bill memo.
And I know it was before Ches maps
Not sure what book you're talking about (looks like a post was deleted) -- Writing Secure Code? I worked with the SWI Team extensively, we improved our static analysis tools a lot and even more importantly I continually reminded everybody of the limitations of static analysis tools!
@noplasticshower I think that was where we met. @SteveBellovin I distinctly remember meeing you at a workshop sometime around then but have absolutely no memory of what workshop it was!
-
R ActivityRelay shared this topic
