Aa!<rҀ{  @ U`@0  @ `0PHH $ @d HHHH̀̀̀ff@  d Footnote TableFootnote**.\t.\t/ - :;,.!? : aN$  dTOCHeading1Heading2 Cruess Garfinkel NewsgroupOReilly SebastopolSpaffordTuTuThWalcottemailhttp newsgroup   ZEquationVariablesA AR5ASALAMA5A6AUAV  <$lastpagenum><$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear>;<$monthname> <$daynum>, <$year> <$hour>:<$minute00> <$ampm>"<$monthnum>/<$daynum>/<$shortyear><$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear> <$fullfilename> <$filename> <$paratext[Title]> <$paratext[Heading1]> <$curpagenum> <$marker1> <$marker2> (Continued)+ (Sheet <$tblsheetnum> of <$tblsheetcount>)Heading & Page <$paratext> on page<$pagenum>Pagepage<$pagenum>See Heading & Page%See <$paratext> on page<$pagenum>. Table All7Table<$paranumonly>, <$paratext>, on page<$pagenum>Table Number & Page'Table<$paranumonly> on page<$pagenum>AA?A 5y5|5555A)5)5A5)55)55)5 5)55)551.5 3.5 4.5 5.5 6.5)55 5)55)55)55)55)55)555)55 5 5 558`6)6 : 2.,=9=:=;=<===A=B?\?dqdqdq HmRqHmRHRHR2Footnote Hr@qHr@HzHz2 Single LineHqFootnote 5_  HDq HDHH2 Double LineHq Double Line5c 5e Hq  Single Line5h HZq  TableFootnote EGxRqEGxREPwEPw2 TableFootnoted5p HHˆ5xHHˆGe HHˆ5zHHˆl HHˆ5{HHˆWd HHˆ5}HHˆl HUV 5~HUV WlaVersion of   [September 26, 2000 12:03 am ZPage   W# U of   ]2 \ HUV 5HUV l H$ 5H$ Wl3 YGeneral Information XECS 153 Fall 2000 H$ 5H$ l HUV 5HUV Ge HUV 5HUV l H$ 5H$ Ge H$ 5H$ l HHˆ5HHˆŸ6X7;W:# @hGeneral Information  V HHˆ5HHˆ?l}B,f^Q5 B,f^QW ` Instructor }fz5!fz `8Matt Bishop, 3059 Engineering Unit II; phone: 752-8060; Y`Memail: bishop@cs.ucdavis.edu; web page: http://seclab.cs.ucdavis.edu/~bishop CZ`POffice hours : Tu 2:003:00PM, W 11:0012:00PM, by appointment or by chance }B,^Q5 "B,^Q   Teaching P@ Assistant }z5!#z `&Tom Walcott, 3082 Engineering Unit II ^`email: walcott@cs.ucdavis.edu C_`1Office hours : M 7:009:00PM, Th 3:005:00PM }B,^Q5"$B,^QW `Lecture }z5#%zW`)TuTh 12:10PM 1:30PM in 107 Cruess Hall }B,^Q 5$&B,^Q  Discussion P@Section }z 5%'z `"F 11:0011:50AM in 1115 Hart Hall Q[`_We will use these to make up some classes. Material presented here  will be  on exams. }B,^Q 5&(B,^Q  Course P@Outline }z 5')z  VIntroduce principles, mechanisms, and implementations of computer security; learn how P@Vattacks work, how to defend against them, and how to design systems to withstand them }B,^Qc5(*B,^QcW ` Course Goals }zc5)9zcc` Some goals we hope you achieve: `Flearn about security in the UNIX system and programming environments; !, [learn how to attack a system, and to defend it by analyzing the system for vulnerabilities @!and ameliorating those problems; `Punderstand the strengths, and weaknesses of cryptography as a tool of security `Dlearn how access to systems, resources, and data can be controlled; `7learn the basics of writing security-related programs; A`"learn about security in networks; }B,^Q5:,B,^QW `Text }z5+-z eWe shall use parts of the text  Computer Security: Art and Science . Readings from this text @Cwill be distributed in class. A recommended supplementary text is: a  \S. Garfinkel and E. Spafford,  Practical UNIX & Internet Security , Second Edition, @6OReilly and Associates, Inc., Sebastopol, CA. 1996. }B,^Q5,.B,^QW! ` Computers }z5-/z" YAll registered students have been given an account on the computer science instructional ]machines in the basement.  Change your password as soon as you can; if it is not changed bZwithin a week, your account will be disabled and you will have to see a system programmer @to have it reset. }B,^Q5.0B,^Q  # Course P@ Handouts }z5/1z $ eCourse handouts, programs, and samples will be available in the directory  ~cs153  on any of phthe CSIF workstations, and from  myucdavis . To use the latter, go to http://my.ucdavis.edu and @\log in using your campus-wide login and password. Then go to ECS 153 in your schedule.  }B,#^Q502B,#^Q  & Class P@ Newsgroup }#z513#z ' ]Information about this class, homework assignments, and so forth, will be posted to the newsegroup  ucd.class.ecs153 . Read this newsgroup daily!  You are responsible for everything !dposted to this newsgroup.  Well use it to put out important information. Please do not post to b[this newsgroup. If you want to post things about the class, please use the discussion news@^group  ucd.class.ecs153.d . Discussing something in that newsgroup is perfectly fair. }B,c^Q524B,c^Q W) ` Homework }cz535cz * [Homework is due at noon on the date stated on the homework. See the handout  All About R!@$Homework  for more information. }B,^QK546B,^QK W+ ` Extra Credit }zK55zKK , _Extra credit in this course will be tallied separately from regular scores. If you end up on a p_borderline between two grades at the end of the course, extra credit will count in your favor. ZHowever, failure to do extra credit will never be counted against you, because grades are _assigned on the basis of regular scores. You should do extra credit if you find it interesting ^and think that it might teach you something. Remember, though, it is not wise to skimp on the @0regular assignment in order to do extra credit! }B,c^QW5=Y8B,c^QW> W- `Exams }czW5=7;czWW> .`3Midterm   Thursday, November 9, 2000 in class \`4Final examination  Tuesday, December 12, 2000 s0 ZThese are open book/open notes exams. No early or late exam will be given; if you miss an bexam for medical reasons (you  must  document this; no other excuses are acceptable), you \may be allowed or required to take a make-up exam, or the other parts of the course will be acounted proportionally more (the choice is the instructor's). In particular, forgetting the time @?or place of an exam is  not  an excuse for missing it! }B,k^QA*:B,k^QW `Prerequisites }kzA9+kz  \The prerequisite for this course is ECS 150, Operating Systems. Students who have not taken p`this course are at a serious disadvantage in this class. Students who have not taken the prereq@Xuisite will be  dropped  to make room for those who have had the prerequisites. }B,^Q5=8<B,^Q >4  Academic P@ Integrity }z5=;z>5 gPlease see the  Fall 2000 Class Schedule and Room Directory  for a general discussion of this. @ In particular, for this course: 16 VAll work submitted for credit must be your own. You may discuss your assignments with Zclassmates, with instructors, or with teaching assistants or readers in the course to get Xideas or a critique of your ideas, but the ideas and words you submit must be your own. lUnless  explicitly  stated otherwise  in the assignment , collaboration is considered cheat@(ing and will be dealt with accordingly. !7 TFor written homework, you must write up your own solutions and may neither read nor @"copy another students solutions. 8 \For programs, you must create and type in your own code and document it yourself.  Note @Rthat you are free to seek help while debugging a program once it is written . c9 YA good analogy between appropriate discussion and inappropriate collaboration is the folYlowing: you and a fellow student work for competing software companies developing differ\ent products to meet a given specification. You and your competitor might choose to discuss [product specifications and general techniques employed in your products, but you certainly Zwould not discuss or exchange proprietary information revealing details of your products. iAsk the instructor or a teaching assistant for clarification  beforehand  if the above rules are @ not clear. d5?? HHˆ5=HHˆYX>l}B,H^Q6=YB,H^Q>W `Grading }Hz6=X7Hz>`930% Homework 25% Midterm exam Q]`820% Term Project 25% Final exam dLeftdRightd Referencedd=f@E [ Numbered1.\tNumbered. f@ [Body. f@ [Body. f@ [ Footnote. f@ [YBody. f@T [Heading2Body. f@T [ HeadingRunInBody. f@ [ Indented. f@ [ Bulleted\t. f@ [ Numbered.\t. f@ [ TableFootnote. f@T [ TableTitleT:Table : . @@ [Header Double Line. f@T [ TableTitleT:Table : . f@ [ CellFooting. @@ [Footer. @@ [Body. @@ ,    header. f@ [Rule. @@ [ $ H l      D h  ManHeading.  f@ [ CellHeading.  f@P [ Heading InfoBody.  f@P [ Heading InfoBody. f@ [ CellHeading. f@E [ Numbered1.\tNumbered. f@ [ Numbered.\t. f@ [ Bulleted\t. f@ [CellBody. f@ [CellBody.  f@P[TitleBody.  f@P[TitleBody.  @@ [ ManHeading2.  f@T [Heading1Body. @@ [ $ H l      D h  ManBody. @@ [ $ H l      D h  ManBody. [Emphasis[EquationVariables [ [ [ [ [ ,  [ 33[[ [ [ [ [ [[ [ [8[ 2ThinMediumDoubleThick@ Very Thin H&5H&5H&5H&5H&5Format A H&5H&5H&5H&5H&5Format B,^QVQõ^QzB,fQ  B,Q !"B,Q #$B,Q  %&B,Q  '(B,Qc )*B,Q +,B,Q  -.B,Q  / 0 B,#Q  1 2 B,cQ  3 4 B,QK  5 6 B,cQW > 7 8 B,kQ 9:B,Q  >P;<B,HQ  >XYCommentAQAKA4 ATd BlackT!WhiteddARedddGreendd BluedCyandMagentad YellowHeader/Footer $1Header/Footer $1Header/Footer $2Header/Footer $2IndexIndexCommentCommentSubjectSubjectAuthorAuthorGlossaryGlossaryEquationEquation Hypertext Hypertext  Cross-Ref Cross-Ref Conditional TextConditional TextPositionFMPrivatePositionFMPrivateRangeEndFMPrivateRangeEndFMPrivate HTML Macro HTML Macro M.Times.P Times-Roman FrameRoman M.Times.B Times-Bold FrameRoman M.Geneva.PGeneva FrameRoman M.Times.BITimes-BoldItalic FrameRoman M.Times.I Times-Italic FrameRoman M.Helvetica.BHelvetica-Bold FrameRomanl+Geneva1 HelveticaZTimes#Regular$Roman MediumBoldRegularItalic,; OPNNM;7=c?VlD|1<@{.gZETRqrF˃t,