Computing and Software Wiki - User contributions [en]

http://wiki.cas.mcmaster.ca/index.php?feed=atom&target=Frostd&title=Special%3AContributions Computing and Software Wiki - User contributions [en] 2026-04-10T00:20:32Z From Computing and Software Wiki MediaWiki 1.15.1 http://wiki.cas.mcmaster.ca/index.php/User:Skip User:Skip 2009-11-23T20:56:58Z

<p>Frostd: Added link to Group 7s page</p> <hr /> <div>= Human Computer Interaction =<br /> <br /> =='''This is the projects main page for cs4hc3 and se4f03''' -- ''HCI / CHI'' Courses.==<br /> <br /> ===Objectives===<br /> <br /> ===Logistics===<br /> <ul><br /> <li><br /> During the middle of term the class will be divided into about 12 (n) groups, each of whom will negotiate amongst<br /> themselves a topic of concentration from the list below with at least three ranked by selected priority.<br /> At an early designated lecture, each group will be linked to a topic of their choice in a first-come/first-served<br /> basis -- only one group per project.<br /> </li><br /> <li><br /> Group members should all have their associated member email addresses and use these to generate a wiki in one of the<br /> groups member names. Note that ALL changes made to a wiki are logged by IP address of the machine, as well as time<br /> and date. By law Derek Lipiec MUST always be running an audit trail system which essentially operates as a key logger<br /> in that if any vandalism is done electronically, he can determine who is logged on, from where as well as what was typed.<br /> This is a warning that anyone modifying a group's wiki who is NOT a member of that group will be caught and risk a zero<br /> grade for this assignment exists. Therefore "play safe" and do not fool around. (wfsp)<br /> </li><br /> <li><br /> Just after several weeks of class duration, a created wiki from each group will be completed<br /> and marked. As soon as scheduled, these dates will be posted in the ELM calendar for this course.<br /> </li><br /> <li><br /> Part of this mark will be composed of 12 other rankings (by three groups of four members each as listed below)<br /> from <b>each</b> of the other group members, <b>done individually</b>, who will rank and provide one sentence<br /> of what is best and one sentence of what is worst about the subject wiki under consideration. This is done<br /> through sending Dr.Poehlman an email with the three marks and single sentences for like and dislike reasons.<br /> The ranking for each wiki will be compiled by the instructor and posted anonymously for class consideration<br /> and discussion near the end of term.<br /> </li><br /> </ul><br /> <br /> ===Topics:===<br /> Reference -- adapted from ACM (Association for Computing Machinery -- but people can join, too!) http://wiki.acm.org/cs2001/index.php?title=HUMAN-COMPUTER_INTERACTION<br /> <OL><br /> <Li> '''Motivation:''' Why the study of how people interact with technology is vital for the development of most usable and acceptable systems. [[Motivations for the Studying of HCI]] (Taken by Group 10 -- wfsp/15nov09@14:30) </Li><br /> <Li> '''Contexts for HCI:''' mobile devices, consumer devices, business applications, web, business applications, collaboration systems, games, etc. [[Contexts for HCI]] (Taken by Group 8 -- wfsp/05nov09@14:00)</Li><br /> <Li> '''[[Process_for_User-centered_Development]]:''' early focus on users, empirical testing, iterative design. (Specified for Group 11 -- wfsp/15nov09@14:30) </Li><br /> <Li> '''[[Different measures for evaluation]]:''' utility, efficiency, learnability, user satisfaction. (Taken by Group 5 -- wfsp/10nov09@13:00)</Li><br /> <Li> '''Models that inform human-computer interaction (HCI) design:''' attention, perception and recognition, movement, and cognition.</Li><br /> <Li> '''Social issues influencing HCI design and use:''' culture, communication, and organizations. (Taken by Group 3 -- wfsp/13nov09@15:30) </Li><br /> <Li> '''[[HCI - Accommodating human diversity]]:''' including universal design and accessibility and designing for multiple cultural and linguistic contexts. (Taken by Group 9 -- wfsp/12nov09@13:30)</Li><br /> <Li> The most '''[[Common Interface Mistakes]]'''. (Taken by Group 1 -- wfsp/04nov09@17:00)</Li><br /> <Li> '''[[User Interface Standards]]'''. (Taken by Group 6 -- wfsp/05nov09@19:30)</Li><br /> <Li> The '''five interaction styles''' as espoused by [[B.Scheidermann]]. [[Five Interaction Styles]] (Taken by Group 7 -- wfsp/04nov09@17:30)</Li><br /> <Li> The '''Object-Action''' (or visa-versa) '''model''' and its applications. [[The Object-Action (or_visa-versa) model and its applications]](Specified for Group 2 -- wfsp/15nov09@14:30) </Li><br /> <Li> The '''direct manipulation method''' and its importance to CHI. [[Direct Manipulation]] (Taken by Group 4 -- wfsp/06nov09@09:30) </Li><br /> </OL><br /> <h4><br /> Marking Duties for Each Group:<br /> </h4><br /> <table border="1"><br /> <tr><br /> <th><br /> <u>Group Mark1 Mark2 Mark3</u><br /> </th><br /> </tr><br /> <tr><br /> <td><br /> 1 Group 2 Group 3 Group 4<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 2 Group 3 Group 4 Group 5<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 3 Group 4 Group 5 Group 6<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 4 Group 5 Group 6 Group 7<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 5 Group 6 Group 7 Group 8<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 6 Group 7 Group 8 Group 9<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 7 Group 8 Group 9 Group 10<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 8 Group 9 Group 10 Group 11<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 9 Group 10 Group 11 Group 01<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 10 Group 11 Group 01 Group 02<br /> </td><br /> </tr><br /> <tr><br /> <td><br /> 11 Group 01 Group 02 Group 03<br /> </td><br /> </tr><br /> </table><br /> <br /> <br /> ----<br /> <br /> =='''This is the VRML assignment main page for cs4hc3 and se4f03''' <br> -- ''HCI / CHI'' Courses.==<br /> NOTE: This is NOT required for the 2009-2010 version of this course.<br /> ===Some Important References:===<br /> <br /> <UL><br /> <li><br /> The Custom Courseware for this course has an Appendix section for VRML beginners so this is a good place to begin studying if you are not familiar with the Virtual Reality Modelling Language. We will be using this to create 3-D interfaces for 3-D worlds, just to get some practice in thinking in more than two dimensions. Although VRML has been around for more than a decade, it is still found as the 3-D layer in MPEG4, has been updated and in a standard in the W3C world known as X3D, which is just VRML with <elements> instead of reserved keywords. If you know VRML, you know X3D.<br /> </li><br /> <li><br /> To begin our study of the Virtual Reality Modeling Language (VRML), we need to get setup to view the VRML code (which is in pure ASCII, as is Javascript, etc.) To create VRML, use any ASCII editor that you like best. I use Crimson Editor which has a built-in context sensitive markup that understands VRML, so it is easy to distinguish comments from verbs and nouns, etc.<br /> Go to http://sourceforge.net/projects/emeraldeditor/files/ where Emerald Editor (the newest version of the Crimson editor) can be downloaded freely. To interpret VRML code (nested in HTML code) you need a plug-in. The best that I have found is called Cortona from Parallel Graphics at http://www.cortona3d.com/cortona/ . It works best with Apple Safari Browser version 4 from http://www.apple.com/safari/download/ . All of this information is at the end of the course web site section on VRML at http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML headed with the title "Recommended Client Applications". By the way, Parallel Graphics has an editor called VRMLPad that is not free but can be downloaded as a trial version, which may help the beginner as it provides a thumbnail sketch at the margin right when it recognizes any VRML code shape primitives -- interesting thing to see work.<br /> </li><br /> <li><br /> As far as web references go, the best place to start is on the course web site: <br> --<br /> http://www.cas.mcmaster.ca/~se4d03/demo.html#VRML <br /> </li><br /> <ol><br /> <li><br /> Once here you can take the tutorial, done by a senior thesis student Polo Cerone several year's ago.<br /> It can be taken on-line or downloaded and worked through locally -- either is equivalent.<br /> </li><br /> <li><br /> Once the tutorial is taken, there are many example VRML code snippets that can be viewed with whatever browser plug-in that you have installed. Pay particular attention to the graduated examples that show how one specifically goes about creating an interface in VRML that controls objects in the main scene graph. This is located back near the beginning of the VRML section titled "Graduated VRML2 Interface Examples".<br /> </li><br /> </ol><br /> </UL></div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-23T20:43:28Z

<p>Frostd: </p> <hr /> <div>The '''Five Interaction Styles''' originally presented by Ben Shneiderman in 1983 represent the five basic ways that humans interact with a computer interface. Each interaction style effects the overall efficiency and usability of the computer system, but that is not to say there are good or bad interaction styles. The styles all have benefits and trade offs when dealing with certain types of users and it is often in an interface designers best interest to use a combination of styles instead of anyone one style alone.<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> [[Image:DirectManipulation.jpg|thumb|300px|right|Simple example of file/folder metaphor in Windows Vista]]<br /> <br /> Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.<br /> <br /> === + Advantages ===<br /> * Visual presentation of task concepts<br /> * Allows easy learning<br /> * Encourages exploration<br /> * Users can immediately see if their actions are furthering their goals<br /> * Users gain confidence because they feel in control and can predict system responses<br /> <br /> === - Disadvantages ===<br /> * Can be hard to implement<br /> * Requires graphics display/pointing devices<br /> <br /> == Menus ==<br /> [[Image:menus1.gif|thumb|300px|right|Example of a typical menu in Windows XP]]<br /> [[Image:menus2.gif|thumb|300px|right|Microsoft's new "ribbon" menu]]<br /> <br /> Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in Multiple Document Interfaces or in Mac OS X).<br /> <br /> === + Advantages ===<br /> * Accessible to novice and intermittent users <br /> * Allows for a very large pallette of structured commands which can be easily "explored"<br /> * Facilitates Multiple Document Interfaces well<br /> * Does not rely on parsing input<br /> <br /> === - Disadvantages ===<br /> * Can bury useful features under complex hierarchies<br /> * Number of items limited by screen resolution<br /> * Convention restricts how menu items are categorised<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<sup>[1]</sup><br /> <br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognized'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Line ==<br /> [[Image:Commandline.png|thumb|300px|right|Ubuntu command line showing basic commands]]<br /> <br /> Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<sup>[1]</sup><br /> <br /> === + Advantages ===<br /> * quick and powerful for experienced users<br /> * user-controlled interaction<br /> * minimal amount of typing (no mouse use)<br /> * can be used in conjunction with other user interfaces<br /> <br /> === - Disadvantages ===<br /> * little or no prompting<br /> * requires user’s knowledge of system, programs<br /> * relies on recall of commands and syntax<br /> * difficult to learn<br /> * error prone<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> * [[Motivations for the Studies of HCI]]<br /> * [[Contexts for HCI]]<br /> * [[Process for User-centered Development]]<br /> * [[Social issues influencing HCI design and use]]<br /> * [[HCI - Accommodating human diversity]]<br /> * [[User Interface Standards]]<br /> * [[The Object-Action (or visa-versa) model and its applications]]<br /> * [[Direct Manipulation]]<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)<br /> <br /> --[[User:Collim|Collim]] 23:50, 21 November 2009 (EST)<br /> <br /> --[[User:Frostd|Frostd]] 00:58, 22 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-23T20:41:09Z

<p>Frostd: Added Visual representation picture</p> <hr /> <div>The '''Five Interaction Styles''' originally presented by Ben Shneiderman in 1983 represent the five basic ways that humans interact with a computer interface. Each interaction style effects the overall efficiency and usability of the computer system, but that is not to say there are good or bad interaction styles. The styles all have benefits and trade offs when dealing with certain types of users and it is often in an interface designers best interest to use a combination of styles instead of anyone one style alone.<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> [[Image:DirectManipulation.jpg|thumb|300px|right|Simple example of file/folder metaphor in Windows Vista]]<br /> <br /> Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.<br /> <br /> === + Advantages ===<br /> * Visual presentation of task concepts<br /> * Allows easy learning<br /> * Encourages exploration<br /> * Users can immediately see if their actions are furthering their goals<br /> * Users gain confidence because they feel in control and can predict system responses<br /> <br /> === - Disadvantages ===<br /> * Can be hard to implement<br /> * Requires graphics display/pointing devices<br /> <br /> == Menus ==<br /> [[Image:menus1.gif|thumb|300px|right|Example of a typical menu in Windows XP]]<br /> [[Image:menus2.gif|thumb|300px|right|Microsoft's new "ribbon" menu]]<br /> <br /> Menus provide a way to visually organise a very large set of actions. Menus are nearly ubiquitous in modern applications, with the most standard format being the "File/Edit" strip located across the top of windows (such as in Microsoft Windows) or the user's workspace (such as in Multiple Document Interfaces or in Mac OS X).<br /> <br /> === + Advantages ===<br /> * Accessible to novice and intermittent users <br /> * Allows for a very large pallette of structured commands which can be easily "explored"<br /> * Facilitates Multiple Document Interfaces well<br /> * Does not rely on parsing input<br /> <br /> === - Disadvantages ===<br /> * Can bury useful features under complex hierarchies<br /> * Number of items limited by screen resolution<br /> * Convention restricts how menu items are categorised<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<sup>[1]</sup><br /> <br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognized'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Line ==<br /> [[Image:Commandline.png|thumb|300px|right|Ubuntu command line showing basic commands]]<br /> <br /> Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<sup>[1]</sup><br /> <br /> === + Advantages ===<br /> * quick and powerful for experienced users<br /> * user-controlled interaction<br /> * minimal amount of typing (no mouse use)<br /> * can be used in conjunction with other user interfaces<br /> <br /> === - Disadvantages ===<br /> * little or no prompting<br /> * requires user’s knowledge of system, programs<br /> * relies on recall of commands and syntax<br /> * difficult to learn<br /> * error prone<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> * [[Motivations for the Studies of HCI]]<br /> * [[Contexts for HCI]]<br /> * [[Process for User-centered Development]]<br /> * [[Social issues influencing HCI design and use]]<br /> * [[HCI - Accommodating human diversity]]<br /> * [[User Interface Standards]]<br /> * [[The Object-Action (or visa-versa) model and its applications]]<br /> * [[Direct Manipulation]]<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> = External links =<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)<br /> <br /> --[[User:Collim|Collim]] 23:50, 21 November 2009 (EST)<br /> <br /> --[[User:Frostd|Frostd]] 00:58, 22 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/File:DirectManipulation.jpg File:DirectManipulation.jpg 2009-11-23T20:39:01Z

<p>Frostd: Simple example of direct manipulation in windows</p> <hr /> <div>Simple example of direct manipulation in windows</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-23T17:36:26Z

<p>Frostd: </p> <hr /> <div>The '''Five Interaction Styles''' originally presented by Ben Shneiderman in 1983 represent the five basic ways that humans interact with a computer interface. Each interaction style effects the overall efficiency and usability of the computer system, but that is not to say there are good or bad interaction styles. The styles all have benefits and trade offs when dealing with certain types of users and it is often in an interface designers best interest to use a combination of styles instead of anyone one style alone.<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> <br /> Visual representation (also known as [[Direct Manipulation]]) features a natural representation of task [http://www.cas.mcmaster.ca/wiki/index.php/The_Object-Action_%28or_visa-versa%29_model_and_its_applications objects and actions]. This helps present the process as actually performing a task itself directly even though it is being doing through an intermediary like a computer. The visual representation usually takes the form of a metaphor related to the actual task being performed. In this way well designed visual representation systems tend to make the interaction enjoyable for the users, which is excellent for novice users or complex tasks that can lead to anxiety.<br /> <br /> === + Advantages ===<br /> * Visual presentation of task concepts<br /> * Allows easy learning<br /> * Encourages exploration<br /> * Users can immediately see if their actions are furthering their goals<br /> * Users gain confidence because they feel in control and can predict system responses<br /> <br /> === - Disadvantages ===<br /> * Can be hard to implement<br /> * Requires graphics display/pointing devices<br /> <br /> == Menus ==<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<br /> <br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognized'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Line ==<br /> [[Image:Commandline.png|thumb|300px|right|Ubuntu command line showing basic commands]]<br /> <br /> Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<br /> <br /> === + Advantages ===<br /> * quick and powerful for experienced users<br /> * user-controlled interaction<br /> * minimal amount of typing (no mouse use)<br /> * can be used in conjunction with other user interfaces<br /> <br /> === - Disadvantages ===<br /> * little or no prompting<br /> * requires user’s knowledge of system, programs<br /> * relies on recall of commands and syntax<br /> * difficult to learn<br /> * error prone<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> * [[Motivations for the Studies of HCI]]<br /> * [[Contexts for HCI]]<br /> * [[Process for User-centered Development]]<br /> * [[Social issues influencing HCI design and use]]<br /> * [[HCI - Accommodating human diversity]]<br /> * [[User Interface Standards]]<br /> * [[The Object-Action (or visa-versa) model and its applications]]<br /> * [[Direct Manipulation]]<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> = External links =<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)<br /> <br /> --[[User:Collim|Collim]] 23:50, 21 November 2009 (EST)<br /> <br /> --[[User:Frostd|Frostd]] 00:58, 22 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-22T22:25:47Z

<p>Frostd: </p> <hr /> <div>The '''Five Interaction Styles'''<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> <br /> == Menus ==<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<br /> <br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognized'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Line ==<br /> [[Image:Commandline.png|thumb|300px|right|Ubuntu command line showing basic commands]]<br /> <br /> Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<br /> <br /> === + Advantages ===<br /> * quick and powerful for experienced users<br /> * user-controlled interaction<br /> * minimal amount of typing (no mouse use)<br /> * can be used in conjunction with other user interfaces<br /> <br /> === - Disadvantages ===<br /> * little or no prompting<br /> * requires user’s knowledge of system, programs<br /> * relies on recall of commands and syntax<br /> * difficult to learn<br /> * error prone<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> = External links =<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)<br /> <br /> --[[User:Collim|Collim]] 23:50, 21 November 2009 (EST)<br /> <br /> --[[User:Frostd|Frostd]] 00:58, 22 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/File:Commandline.png File:Commandline.png 2009-11-22T22:23:34Z

<p>Frostd: Commandline terminal example</p> <hr /> <div>Commandline terminal example</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-22T05:58:43Z

<p>Frostd: </p> <hr /> <div>The '''Five Interaction Styles'''<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> <br /> == Menus ==<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interaction style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<br /> <br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognized'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Line ==<br /> <br /> Command line is the earliest used interaction style and is still seen predominantly in Unix operating systems though still usable to varying degrees on Windows and OSX. This style is mainly used by expert users by typing into a prompt that allows them to quickly execute commands. Unfortunately command line places a considerable burden on the user to learn and recall commands from memory. It is often the case that commands take parameters as well and most of the added benefits (mainly in the way of efficiency) come from using them. This leads to an unfriendly environment for both novice and intermediate users that may attempt to use this style. The large overhead in learning commands and minimal help for the user leaves this style almost exclusively in the domain of the expert user.<br /> <br /> === + Advantages ===<br /> * quick and powerful for experienced users<br /> * user-controlled interaction<br /> * minimal amount of typing (no mouse use)<br /> * can be used in conjunction with other user interfaces<br /> <br /> === - Disadvantages ===<br /> * little or no prompting<br /> * requires user’s knowledge of system, programs<br /> * relies on recall of commands and syntax<br /> * difficult to learn<br /> * error prone<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> = External links =<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)<br /> <br /> --[[User:Collim|Collim]] 23:50, 21 November 2009 (EST)<br /> <br /> --[[User:Frostd|Frostd]] 00:58, 22 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-22T03:43:09Z

<p>Frostd: Hopefully this well help to make the headings pop a little more</p> <hr /> <div>The '''Five Interaction Styles'''<br /> <br /> = Shneiderman's Five Interaction Styles =<br /> <br /> == Visual representation ==<br /> <br /> == Menus ==<br /> <br /> == Fill-In-The-Blanks ==<br /> [[Image:formfillin1.gif|thumb|300px|right|Classic Fill-In-The-Blanks]]<br /> [[Image:formfillin2.gif|thumb|300px|right|Modern-day Fill-In-The-Blanks]]<br /> The Fill-In-The-Blanks interaction style (also known as "Form Fill-in") is best suited to data input, which was aimed at a different set of users than command language, specially non-experts users. Originally Fill-In-The-Blanks is to arrange one or more fields in the form of a prose sentence or phrase, with the fields as "blanks" to be filled in by the user. The TAB-key was designed and is still being used to switch between the fields and ENTER to submit the form. Therefore a pointing device (such as a mouse) was not really needed at that time. However it's very common to mix forms with other interaction styles in software design, such as drop down menus, check boxes etc. The spreadsheet is a variation on the Form Fill-in interation style. Even today, there are quite a few computers are still purely forms-based in the industry, like cash registers, financial systems, stock control systems, and so on. The main reason is because the Fill-In-The-Blanks interface is especially useful for routine, clerical work or those tasks require a great amount of data entry.<br /> === + Advantages ===<br /> * Simplifies data entry<br /> * Minimal training - Shortens learning in that the fields are predefined and need only be 'recognised'.<br /> * Gives convenient assistance - Guides the user via the predefined rules<br /> * Permits use of form-management tools<br /> <br /> === - Disadvantages ===<br /> * Screen space consuming<br /> * requires more keystrokes<br /> * requires handling typing errors (bad for users with poor typing skills)<br /> <br /> == Command Prompt ==<br /> <br /> == Natural Language ==<br /> Natural Language is an interaction style which allows the user to communicate with their computer through a series of spoken commands, similar to how one may issue spoken commands to another person. However the benefits and applicability of Natural Language systems thus far is very limited, largely due to the imprecise and verbose nature of spoken languages. A major issue with using spoken language is that to communicate with computer systems the vocabulary would need to be limited to a specific subset of a full natural language, in order to both reduce ambiguity and keep processing time within reasonable bounds. One solution to the ambiguity of spoken languages is to utilize gestural language, which is considered at least as natural as verbal language. At the same time, the definition of what makes a natural language is very important. It is not as though humans are born knowing spoken word or gestures; a natural language is simply one which can be grasped fluently by the time one is required to draw upon it. A language could be considered natural, if upon approaching a computer the typical user already possesses language skills adequate for communicating desired concepts in a fluent and articulate manner. So in a sense Natural Language could involve a kind of language humans develop with the sole purpose of communicating with computer systems, thus potentially eliminating the ambiguities of the current natural spoken languages. Thus far however Natural Language has not seen widespread use, and often requires each user to train the computer to recognize their own voice. Natural Language could be very useful for those with minimal keyboard skills, and once it more accurately interprets verbal commands may even see widespread use one day. <sup>[2][3]</sup><br /> <br /> === + Advantages ===<br /> * Allows users to communicate with their system naturally<br /> * Can reduce or eliminate the need for keyboards, great for those with poor keyboard skills<br /> * Once it is more accurate at interpreting speech, commands may be able to be spoken faster than they are typed<br /> <br /> === - Disadvantages ===<br /> * Currently cannot accurately interpret much of verbal language, which is too ambiguous<br /> * Requires a lot of training for each user so it can interpret their verbal commands<br /> <br /> = See also =<br /> <br /> = References =<br /> # Mads Soegaard, "Interaction Styles", interaction-design.org, http://www.interaction-design.org/encyclopedia/interaction_styles.html<br /> # Byron Long, "Natural Language as an Interaction Style", Retrieved on November 21st, 2009 from http://www.dgp.toronto.edu/people/byron/papers/nli.html<br /> # Bill Buxton, "The "Natural" Language of Interaction", Retrieved on November 21st, 2009 from http://www.billbuxton.com/natural.html<br /> <br /> = External links =<br /> <br /> --[[User:Shensw|Shensw]] 22:55, 20 November 2009 (EST)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/The_Five_Interaction_Styles The Five Interaction Styles 2009-11-20T05:56:15Z

<p>Frostd: The Five Interaction Styles moved to Five Interaction Styles: 'The' shouldn't be in wiki titles</p> <hr /> <div>#REDIRECT [[Five Interaction Styles]]</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-20T05:56:15Z

<p>Frostd: The Five Interaction Styles moved to Five Interaction Styles: 'The' shouldn't be in wiki titles</p> <hr /> <div>The '''five interaction styles'''<br /> <br /> == Shneiderman's five interaction styles ==<br /> <br /> === Visual representation ===<br /> <br /> === Menus ===<br /> <br /> ===Fill-In-The-Blanks ===<br /> <br /> === Command Prompt ===<br /> <br /> === Natural Language ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> == External links ==</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Five_Interaction_Styles Five Interaction Styles 2009-11-20T05:42:05Z

<p>Frostd: Added headings for content</p> <hr /> <div>The '''five interaction styles'''<br /> <br /> == Shneiderman's five interaction styles ==<br /> <br /> === Visual representation ===<br /> <br /> === Menus ===<br /> <br /> ===Fill-In-The-Blanks ===<br /> <br /> === Command Prompt ===<br /> <br /> === Natural Language ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> == External links ==</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T22:29:42Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> [[Image:DOS_Model.gif|thumb|right|400px|The three main types of DoS attack]]<br /> <br /> A distributed denial of service attack (DDoS) is a much more powerful form of the traditional DoS attack. In this form of the attack multiple compromised computers (also known as slaves) are used to proform the attacks noted above. Capturing the computers to do such an attack is done through viruses and malware. Both may be designed so that all of the machines are triggered at a specific date and time. Alternatively the master system could have has more specific and varied control over them. There are many DDoS tools that can be used to both run through lists of exploits to aquire new slaves as well as to control the slaves. A collected group of compermised computers are often called [[Bots & Botnets]]. Stacheldraht is a classic example of a control program that may be used to control multiple master systems at once which in turn control all of the slaved machines. <sup>[8]</sup><br /> <br /> The primary difference and advantage of DDoS is that DoS only makes use of one computer while DDoS uses many computer to complete a task. Because so many more computers are involved these attacks can be much harder to stop and also harder to detect because more focus can be put on staying hidden instead of getting the maxium power out of a single machine. They attacks are also much more powerful and often involve hundreds or even thousands of computers.<sup>[7]</sup><br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<sup>[4]</sup><br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> * [[Bots & Botnets]]<br /> <br /> == References ==<br /> # [http://anml.iu.edu/ddos/types.html Types of DDoS Attacks]. Retrieved April 11, 2009<br /> # [http://www.cert.org/tech_tips/denial_of_service.html CERT/CC Denial of Service]. Retrieved April 11, 2009<br /> # Mullen, Ruth. [http://www.irchelp.org/irchelp/mirc/flood.html Flood Protection and Ignoring People]. Retrieved April 11, 2009<br /> # "Simple Nomad", [http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html Strategies for Defeating Distributed Attacks]. Retrieved April 11, 2009<br /> # Parks, J. (2008, August 25). [http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320 DDoS Attack Prevention - The Best Medicine]. Retrieved April 12, 2009<br /> # Plonka, Dave. (August 21, 2003). [http://pages.cs.wisc.edu/~plonka/netgear-sntp/ Flawed Routers Flood University of Wisconsin Internet Time Server]. Retrieved April 12, 2009<br /> # Manzano, Yanet. [http://www.acm.org/crossroads/xrds10-1/tracingDOS.html Tracing the Development of Denial of Service Attacks: A Corporate Analogy]. Retrieved April 12, 2009<br /> # Dittrich, David. [http://staff.washington.edu/dittrich/misc/stacheldraht.analysis The "stacheldraht" distributed denial of service attack tool]. Retrieved April 12, 2009<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:59, 12 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T21:59:49Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> [[Image:DOS_Model.gif|thumb|right|400px|The three main types of DoS attack]]<br /> <br /> A distributed denial of service attack (DDoS) is a much more powerful form of the traditional DoS attack. In this form of the attack multiple compromised computers (also known as slaves) are used to proform the attacks noted above. Capturing the computers to do such an attack is done through viruses and malware. Both may be designed so that all of the machines are triggered at a specific date and time. Alternatively the master system could have has more specific and varied control over them. There are many DDoS tools that can be used to both run through lists of exploits to aquire new slaves as well as to control the slaves. A collected group of compermised computers are often called [[Bots & Botnets]]. Stacheldraht is a classic example of a control program that may be used to control multiple master systems at once which in turn control all of the slaved machines. <sup>[8]</sup><br /> <br /> The primary difference and advantage of DDoS is that DoS only makes use of one computer while DDoS uses many computer to complete a task. Because so many more computers are involved these attacks can be much harder to stop and also harder to detect because more focus can be put on staying hidden instead of getting the maxium power out of a single machine. They attacks are also much more powerful and often involve hundreds or even thousands of computers.<sup>[7]</sup><br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<sup>[4]</sup><br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> * [[Bots & Botnets]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> # Manzano, Yanet. Tracing the Development of Denial of Service Attacks: A Corporate Analogy. Retrieved April 12, 2009, from http://www.acm.org/crossroads/xrds10-1/tracingDOS.html<br /> # Dittrich, David. The "stacheldraht" distributed denial of service attack tool. Retrieved April 12, 2009, from http://staff.washington.edu/dittrich/misc/stacheldraht.analysis<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:59, 12 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T21:59:08Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> [[Image:DOS_Model.gif|thumb|right|400px|The three main types of DoS attack]]<br /> <br /> A distributed denial of service attack (DDoS) is a much more powerful form of the traditional DoS attack. In this form of the attack multiple compromised computers (also known as slaves) are used to proform the attacks noted above. Capturing the computers to do such an attack is done through viruses and malware. Both may be designed so that all of the machines are triggered at a specific date and time. Alternatively the master system could have has more specific and varied control over them. There are many DDoS tools that can be used to both run through lists of exploits to aquire new slaves as well as to control the slaves. A collected group of compermised computers are often called [[Bots & Botnets]]. Stacheldraht is a classic example of a control program that may be used to control multiple master systems at once which in turn control all of the slaved machines. <sup>[8]</sup><br /> <br /> The primary difference and advantage of DDoS is that DoS only makes use of one computer while DDoS uses many computer to complete a task. Because so many more computers are involved these attacks can be much harder to stop and also harder to detect because more focus can be put on staying hidden instead of getting the maxium power out of a single machine. They attacks are also much more powerful and often involve hundreds or even thousands of computers.<sup>[7]</sup><br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<sup>[4]</sup><br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> * [[Bots & Botnets]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> # Manzano, Yanet. Tracing the Development of Denial of Service Attacks: A Corporate Analogy. Retrieved April 12, 2009, from http://www.acm.org/crossroads/xrds10-1/tracingDOS.html<br /> # Dittrich, David. The "stacheldraht" distributed denial of service attack tool. Retrieved April 12, 2009, from http://staff.washington.edu/dittrich/misc/stacheldraht.analysis<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T21:07:30Z

<p>Frostd: /* Firewalls */</p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> [[Image:DOS_Model.gif|thumb|right|400px|The three main types of DoS attack]]<br /> <br /> Distributed DoS attacks etc.<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<sup>[4]</sup><br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> # Manzano, Yanet. Tracing the Development of Denial of Service Attacks: A Corporate Analogy. Retrieved April 12, 2009, from http://www.acm.org/crossroads/xrds10-1/tracingDOS.html<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T20:17:12Z

<p>Frostd: /* Distributed attack */</p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> [[Image:DOS_Model.gif|thumb|right|400px|The three main types of DoS attack]]<br /> <br /> Distributed DoS attacks etc.<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> # Manzano, Yanet. Tracing the Development of Denial of Service Attacks: A Corporate Analogy. Retrieved April 12, 2009, from http://www.acm.org/crossroads/xrds10-1/tracingDOS.html<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/File:DOS_Model.gif File:DOS Model.gif 2009-04-12T20:12:51Z

<p>Frostd: The three main methods of Denial of Service. DoS, DDoS, and DRDoS.</p> <hr /> <div>The three main methods of Denial of Service. DoS, DDoS, and DRDoS.</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T20:10:41Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> Common firewalls are not well suited to handle DoS attacks except by taking extreme measures. It does not take a very sophisticated defense to simply drop certain types of packets that are received. The Linux command iptables can be used to manually set the firewall rules that would partially protect a system from a DoS attack. An issue with extreme measures like blocking ICMP messages so that you are not vulnerable to ICMP flooding is that you losing a lot of functionality that comes with the protocol. This could be taken to an extreme of crippling a system by not allowing TCP or UDP packets to reach it. Even by taking steps to limit traffic other areas may still be left vulnerable most notably routers leading to the system.<br /> <br /> A few modern firewalls such as [http://en.wikipedia.org/wiki/Cisco_PIX Cisco PIX] have taken steps to help differentiate between good TCP traffic and malicious traffic.<br /> <br /> === Switches and Routers ===<br /> <br /> Most switches and routers have some options in limiting the amount of information that is allowed through device and access control list features. For switches this may include automatic traffic limiting, delayed binding when dealing with TCP, deep packet inspection and the ability to identify bogus IP addresses. The obvious disadvantage to having many features like this turned on is that the router or switch takes a large performance hit since each packet has to be closely inspected before it is allowed past.<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> # Manzano, Yanet. Tracing the Development of Denial of Service Attacks: A Corporate Analogy. Retrieved April 12, 2009, from http://www.acm.org/crossroads/xrds10-1/tracingDOS.html<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T18:57:43Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T18:08:13Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that the [[Internet Control Message Protocol]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> * [[Tools for conducting denial-of-service attacks]]<br /> * [[Internet Control Message Protocol]]<br /> * [[ping]]<br /> * [[Smurfing]]<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> <br /> == External links ==<br /> * [http://en.wikipedia.org/wiki/Denial-of-service_attack Denial-of-service Attacks]<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T18:02:33Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> * "flood" a network which will prevent legitimate network traffic<br /> * disrupt connections between two machines, which will prevent access to a service<br /> * disrupt the service given to a particular system or person <sup>[2]</sup><br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that the [[Internet Control Message Protocol]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as [[Smurfing]] or the Smurf Attack which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [http://en.wikipedia.org/wiki/Ping_of_death Ping of Death] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [http://en.wikipedia.org/wiki/Transmission_Control_Protocol Transmission Control Protocol] connection request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike an ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [http://en.wikipedia.org/wiki/IRC IRC] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. As well as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develop in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannot handle all of the extra traffic and end up under a denial of service like effect. [http://www.digg.com Digg], [http://www.slashdot.org Slashdot] and [http://www.fark.com Fark] are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a reputation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [http://en.wikipedia.org/wiki/Network_Time_Protocol Network Time Protocol] servers without the intention of the owner of the router.<sup>[6]</sup><br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T17:49:34Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> Goals of the attacks:<br /> <br /> - "flood" a network which will prevent legitimate network traffic<br /> - disrupt connections between two machines, which will prevent access to a service<br /> - disrupt the service given to a perticular system or person [2]<br /> <br /> === ICMP flood ===<br /> <br /> There are two basic ways that [[ICMP]] is used to deny service. The first is by flooding the target with [[ping]] messages until they are overwhelmed by trying to send responses and are slowed down. This can be done in either a very simple way that's only requirement is that you have more bandwidth than the target you are attacking or in a more complex way such as the [[Smurf Attack]] which exploits poorly configured network devices allow packets to be sent to all other hosts on a network using the broadcast address. The other way is called a often called a nuke and the most popular example is called the [[Ping of Death]] which sends an ICMP ECHO request packet that is much larger than the maximum IP packet size to target. Because of the size of the packet the target cannot reassemble them. This often causes the system to crash as a result. <sup>[1]</sup><br /> <br /> === TCP SYN Flood Attack ===<br /> <br /> [[TCP]] connect request packets can be used to attack a target machine by causing the target to create half-open connections and reserve all of the ports on the machine. This is done by attempting to create a regular connection with the target, but never returning anything back to them after they have sent the SYN-ACK packet. Since the process of opening a TCP connect is a three-way handshake this will stall the process while waiting for confirmation from the attacker. Unlike a ICMP flood this attack does not depend on having more bandwidth than the target because there is a relatively small number of ports that have to be reserved.<sup>[1,2]</sup> <br /> <br /> === Application level floods ===<br /> <br /> DoS attacks are not limited to only a server scale. Individual applications on a users machine are also prone to attack depending on the software. [[IRC]] is a very common example of where the various types of attacks used on servers can be seen on a smaller scale. These can include exploits such as buffer overflow which can cause software to get confused and fill disk space or consume all available memory or CPU time. Aswell as the more common types of attack such as flooding.<sup>[3]</sup><br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> As certain websites on the Internet grew more popular a relatively interesting phenomena started to develope in which websites were unintentionally being attacked by huge spikes in popularity. It is almost always the case that when big and often very popular sites link to small, unknown websites these sites cannnot handle all of the extra traffic and end up under a denial of service like effect. Digg, Slashdot and Fark are prime examples of websites that's only goal is to increase the popularity of other websites and they have gained a repuation for their own related "effects" when any website is posted on them.<br /> <br /> Unintentional attacks are not limited to popularity. Routes such as D-Link and Netgear also have a history of flooding [[Network Time Protocol]] servers without the intention of the owner of the router.[6]<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T17:46:01Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <br /> === Application level floods ===<br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, from http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, from http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, from http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, from http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> # Plonka, Dave. (August 21, 2003). Flawed Routers Flood University of Wisconsin Internet Time Server. Retrieved April 12, 2009, from http://pages.cs.wisc.edu/~plonka/netgear-sntp/<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T16:39:40Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <br /> === Application level floods ===<br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks. Retrieved April 11, 2009, http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service. Retrieved April 11, 2009, http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, Ruth. Flood Protection and Ignoring People. Retrieved April 11, 2009, http://www.irchelp.org/irchelp/mirc/flood.html<br /> # "Simple Nomad", Strategies for Defeating Distributed Attacks. Retrieved April 11, 2009, http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> # Parks, J. (2008, August 25). DDoS Attack Prevention - The Best Medicine. Retrieved April 12, 2009, from http://ezinearticles.com/?DDoS-Attack-Prevention---The-Best-Medicine&id=1439320<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T16:25:25Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <br /> === Application level floods ===<br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks, http://anml.iu.edu/ddos/types.html<br /> # CERT/CC Denial of Service, http://www.cert.org/tech_tips/denial_of_service.html<br /> # Mullen, R, Flood Protection and Ignoring People, http://www.irchelp.org/irchelp/mirc/flood.html<br /> # Strategies for Defeating Distributed Attacks, http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> <br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T16:12:06Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <ref>{{Cite web|url=http://anml.iu.edu/ddos/types.html|title=Types of DDoS Attacks|accessdate=April 11 2009}}</ref><br /> <br /> === Application level floods ===<br /> <ref>{{Cite web|url=http://www.irchelp.org/irchelp/mirc/flood.html|title=Flood Protection and Ignoring People|accessdate=April 11 2009}}</ref><br /> <br /> === Distributed attack ===<br /> <ref>{{Cite web|url=http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html|title=Strategies for Defeating Distributed Attacks|accessdate=April 11 2009}}</ref><br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> # Types of DDoS Attacks, http://anml.iu.edu/ddos/types.html<br /> # Flood Protection and Ignoring People, http://www.irchelp.org/irchelp/mirc/flood.html<br /> # Strategies for Defeating Distributed Attacks, http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html<br /> <br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T01:12:36Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <ref>{{Cite web|url=http://anml.iu.edu/ddos/types.html|title=Types of DDoS Attacks|accessdate=April 11 2009}}</ref><br /> <br /> === Application level floods ===<br /> <ref>{{Cite web|url=http://www.irchelp.org/irchelp/mirc/flood.html|title=Flood Protection and Ignoring People|accessdate=April 11 2009}}</ref><br /> <br /> === Distributed attack ===<br /> <ref>{{Cite web|url=http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html|title=Strategies for Defeating Distributed Attacks|accessdate=April 11 2009}}</ref><br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> {{Reflist}}<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-12T01:08:00Z

<p>Frostd: </p> <hr /> <div>A '''denial of service attack (DoS attack)''' is generally the attempt to degrade the resources of another computer, or crash it, so the that the intended users of that computer can not longer use it. The methods used to do such an attack usually involve an attempt to exploit a weakness in one of the protocols that are used on the internet to cause harm to the target machine or make it lose and use resources at an unusual level. Since denial of service attacks are so common today protection has become a very important concern for machines on the internet.<br /> <br /> == Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <ref>{{Cite web|url=http://anml.iu.edu/ddos/types.html|title=Types of DDoS Attacks|accessdate=April 11 2009}}</ref><br /> <br /> === Application level floods ===<br /> <ref>{{Cite web|url=http://www.irchelp.org/irchelp/mirc/flood.html|title=Flood Protection and Ignoring People|accessdate=April 11 2009}}</ref><br /> <br /> === Distributed attack ===<br /> <ref>http://www.windowsecurity.com/whitepapers/Strategies_for_Defeating_Distributed_Attacks.html</ref><br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> {{Reflist}}<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-05T18:36:59Z

<p>Frostd: /* Application front end hardware */</p> <hr /> <div>== Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <br /> === Application level floods ===<br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application Level ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> {{Reflist}}<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-05T18:35:50Z

<p>Frostd: </p> <hr /> <div>== Attack Methods ==<br /> <br /> === ICMP flood ===<br /> <br /> === Application level floods ===<br /> <br /> === Distributed attack ===<br /> <br /> === Unintentional attack ===<br /> <br /> == Prevention and Protection ==<br /> <br /> === Firewalls ===<br /> <br /> === Switches and Routers ===<br /> <br /> === Application front end hardware ===<br /> <br /> == See also ==<br /> <br /> == References ==<br /> <br /> {{Reflist}}<br /> <br /> == External links ==<br /> <br /> --[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd http://wiki.cas.mcmaster.ca/index.php/Denial_Of_Service_Attacks Denial Of Service Attacks 2009-04-03T21:32:54Z

<p>Frostd: New page: --~~~~</p> <hr /> <div>--[[User:Frostd|Frostd]] 17:32, 3 April 2009 (EDT)</div>

Frostd