DOCSLIB.ORG

Security-Warrior.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Security-Warrior.Pdf Security Warrior Other computer security resources from O’Reilly Related titles 802.11 Security Secure Coding: Principles & Building Internet Firewalls Practices Computer Security Basics Securing Windows NT/2000 Java Cryptography Servers for the Internet Java Security SSH, The Secure Shell: The Definitive Guide Linux Security Cookbook Web Security, Privacy, and Secure Programming Cook- Commerce book for C and C++ Database Nation Network Security with OpenSSL Building Secure Servers with Linux Practical Unix and Internet Security Security Books security.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center security and related technologies, including sample chapters and code examples. oreillynet.com is the essential portal for developers interested in open and emerging technologies, including new platforms, pro- gramming languages, and operating systems. Conferences O’Reilly & Associates brings diverse innovators together to nur- ture the ideas that spark revolutionary industries. We specialize in documenting the latest tools and systems, translating the in- novator’s knowledge into useful skills for those in the trenches. Visit conferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today with a free trial. Security Warrior Cyrus Peikari and Anton Chuvakin Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Security Warrior by Cyrus Peikari and Anton Chuvakin Copyright © 2004 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly Media, Inc. books may be purchased for educational, business, or sales promotional use. On- line editions are also available for most titles (safari.oreilly.com). For more information, contact our cor- porate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Production Editor: Colleen Gorman Cover Designer: Emma Colby Interior Designer: David Futato Printing History: January 2004: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Security Warrior, the image of Sumo wrestlers, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. This book uses RepKover™, a durable and flexible lay-flat binding. ISBN: 0-596-00545-8 [M] [11/04] Dr. Cyrus Peikari is humbled before Bahá’u’lláh, the Glory of God. He also thanks his students, teachers, and fellow seekers of knowledge. Dr. Peikari is also grateful to his family for their support and encouragement. —Dr. Cyrus Peikari The part of the book for which I am responsible is dedicated to Olga, who put up with me during all those evenings I spent working on the book and who actually encouraged me to write when I was getting lazy. —Dr. Anton Chuvakin Table of Contents Preface . xiii Part I. Software Cracking 1. Assembly Language . 3 Registers 4 ASM Opcodes 7 References 8 2. Windows Reverse Engineering . 9 History of RCE 10 Reversing Tools 11 Reverse Engineering Examples 23 References 32 3. Linux Reverse Engineering . 33 Basic Tools and Techniques 34 A Good Disassembly 54 Problem Areas 69 Writing New Tools 74 References 116 4. Windows CE Reverse Engineering . 118 Windows CE Architecture 119 CE Reverse Engineering Fundamentals 123 Practical CE Reverse Engineering 131 vii Reverse Engineering serial.exe 147 References 160 5. Overflow Attacks . 161 Buffer Overflows 161 Understanding Buffers 162 Smashing the Stack 165 Heap Overflows 166 Preventing Buffer Overflows 167 A Live Challenge 168 References 175 Part II. Network Stalking 6. TCP/IP Analysis . 179 A Brief History of TCP/IP 179 Encapsulation 179 TCP 180 IP 182 UDP 184 ICMP 185 ARP 185 RARP 186 BOOTP 186 DHCP 186 TCP/IP Handshaking 186 Covert Channels 188 IPv6 188 Ethereal 190 Packet Analysis 191 Fragmentation 192 References 198 7. Social Engineering . 199 Background 200 Performing the Attacks 202 Advanced Social Engineering 209 References 211 viii | Table of Contents 8. Reconnaissance . 212 Online Reconnaissance 212 Conclusion 224 References 224 9. OS Fingerprinting . 225 Telnet Session Negotiation 225 TCP Stack Fingerprinting 226 Special-Purpose Tools 229 Passive Fingerprinting 229 Fuzzy Operating System Fingerprinting 232 TCP/IP Timeout Detection 234 References 235 10. Hiding the Tracks . 236 From Whom Are You Hiding? 236 Postattack Cleanup 237 Forensic Tracks 243 Maintaining Covert Access 248 References 254 Part III. Platform Attacks 11. Unix Defense . 257 Unix Passwords 257 File Permissions 261 System Logging 264 Network Access in Unix 267 Unix Hardening 270 Unix Network Defense 285 References 298 12. Unix Attacks . 299 Local Attacks 299 Remote Attacks 307 Unix Denial-of-Service Attacks 321 References 328 Table of Contents | ix 13. Windows Client Attacks . 329 Denial-of-Service Attacks 329 Remote Attacks 339 Remote Desktop/Remote Assistance 343 References 349 14. Windows Server Attacks . 350 Release History 350 Kerberos Authentication Attacks 351 Kerberos Authentication Review 351 Defeating Buffer Overflow Prevention 356 Active Directory Weaknesses 357 Hacking PKI 359 Smart Card Hacking 360 Encrypting File System Changes 363 Third-Party Encryption 365 References 367 15. SOAP XML Web Services Security . 369 XML Encryption 369 XML Signatures 372 Reference 373 16. SQL Injection . 374 Introduction to SQL 374 SQL Injection Attacks 377 SQL Injection Defenses 383 PHP-Nuke Examples 387 References 390 17. Wireless Security . 391 Reducing Signal Drift 391 Problems with WEP 393 Cracking WEP 393 Practical WEP Cracking 399 VPNs 399 TKIP 400 SSL 401 x | Table of Contents Airborne Viruses 401 References 406 Part IV. Advanced Defense 18. Audit Trail Analysis . 409 Log Analysis Basics 409 Log Examples 410 Logging States 418 When to Look at the Logs 419 Log Overflow and Aggregation 420 Challenge of Log Analysis 421 Security Information Management 421 Global Log Aggregation 422 References 423 19. Intrusion Detection Systems . 424 IDS Examples 425 Bayesian Analysis 430 Hacking Through IDSs 435 The Future of IDSs 437 Snort IDS Case Study 439 IDS Deployment Issues 443 References 445 20. Honeypots . 446 Motivation 447 Building the Infrastructure 448 Capturing Attacks 457 References 458 21. Incident Response . 459 Case Study: Worm Mayhem 459 Definitions 460 Incident Response Framework 462 Small Networks 466 Medium-Sized Networks 471 Large Networks 473 References 477 Table of Contents | xi 22. Forensics and Antiforensics . 478 Hardware Review 478 Information Detritus 480 Forensics Tools 481 Bootable Forensics CD-ROMs 486 Evidence Eliminator 490 Forensics Case Study: FTP Attack 497 References 506 Part V. Appendix Appendix: Useful SoftICE Commands and Breakpoints . 509 Index . 517 xii | Table of Contents Preface ...All samurai ought certainly apply themselves to the study of military science. But a bad use can be made of this study to puff oneself up and disparage one’s colleagues by a lot of high-flown but incorrect arguments that only mislead the young and spoil their spirit. For this kind gives forth a wordy discourse that may appear to be correct and proper enough, but actually he is striving for effect and thinking only of his own advantage, so the result is the deterioration of his character and the loss of the real samurai spirit. This is a fault arising from a superficial study of the subject, so those who begin it should never be satisfied to go only halfway but persevere until they understand all the secrets and only then return to their former simplicity and live a quiet life.... —Daidoji Yuzan The Code of the Samurai * This book offers unique methods for honing your information security (infosec) technique. The typical reader is an intermediate- to advanced-level practitioner. But who among us is typical? Each of us approaches infosec with distinctive training and skill. Still, before you spend your hard-earned money on this book, we will try to describe the target reader. As an example, you might enjoy this book if you already have experience with net- working and are able to program in one or more languages. Although your interest in infosec might be new, you have already read at least a few technical books on the sub- ject, such as Practical UNIX & Internet Security from O’Reilly. You found those books to be informative, and you would like to read more of the same, but hopefully cover- ing newer topics and at a more advanced level. Rather than an introductory survey of security from the defensive side, you would like to see through an attacker’s eyes. You are already familiar with basic network attacks such as sniffing, spoofing, and denial-of-service. You read security articles and vulnerability mailing lists online, and * Samurai quote courtesy of http://www.samurai-archives.com. xiii This is the Title of the Book, eMatter Edition Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved. you know this is the best way to broaden your education. However, you now want a single volume that can quickly ratchet your knowledge level upward by a few notches. Instead of reading a simple catalog of software tools, you would like to delve deeper into underlying concepts such as packet fragmentation, overflow attacks, and operat- ing system fingerprinting.
Load more

Recommended publications
  • Tadiran-Coral-Voicemail-User-Guide-Steadfasttelecom.Com .Pdf
    Coral Message Center (CMC) User Guide Version 2.1 for Windows The flexible way to communicate . © 2002-2003 Active Voice LLC To access your mailbox from inside your organization All rights reserved. First edition 2003. 1. Call the voice messaging system. 1 for Yes, 2 for No, PhoneBASIC, Repartee, TeLANophy, 2. When the system greets you, enter: ViewCall, and ViewMail are trademarks of Active Voice, LLC. Personal ID ______________________________________________________ All other brands and product names used in this docu- ment are trademarks of their respective owners. Security code (if required) ___________________________________________ Licensed under one or more of the following patents: U.S. Nos. 4,994,926; 5,291,302; 5,459,584; 4,696,028; To access your mailbox by computer 4,809,321; 4,850,012; 4,922,526; 4,935,958; 4,955,047; 1. Launch Mailbox Manager. 4,972,469; 4,975,941; 5,020,095; 5,027,384; 5,029,196; 5,099,509; 5,109,405; 5,148,478; 5,166,974; 5,168,519; 2. When the system greets you, enter: 5,249,219; 5,303,298; 5,309,504; 5,347,574; 5,666,401; 5,181,243; 5,724,408; and Canadian No. 1329852. Host name_______________________________________________________ Extension _______________________________________________________ Security Code _____________________________________________________ For assistance, call: Name___________________________________________________________ Extension _______________________________________________________ Contents Introduction ii Changing your mailbox setup 21 Using quick message actions and shortcuts 47 Setting up your mailbox .......................................iv Working with the Mailbox Manager ....................22 Changing your security code..............................24 Quick message actions ...................................... 48 Checking and leaving messages 1 Changing your recorded and spelled names......25 Shortcuts...........................................................
    [Show full text]
  • Resolving Issues with Forms
    C1261587x.fm Page 265 Thursday, November 15, 2001 3:51 PM Resolving Issues with Forms In 1988, Alan Cooper demonstrated a prototype called Ruby to Bill Gates. Ruby provided a form designer that allowed you to drag and drop controls, then known as gizmos, to quickly and easily create composite forms—such as dialog boxes, entry forms, and report forms. Microsoft took Cooper’s Ruby product and combined it with Basic to create Microsoft Visual Basic 1. Microsoft has since shipped a version of Ruby with every version of Visual Basic, versions 1 through 6. With every version, that is, until Visual Basic .NET. Visual Basic .NET provides a new forms package called Windows Forms. Although the Windows Forms package was designed using the same basic prin- ciple as Ruby—it is a form designer that allows you to drag and drop controls and set properties—it was never meant to be an extension of, nor to be com- patible with, Ruby. Therefore, there are fundamental differences between the two forms packages that affect the way you create Visual Basic applications. This chapter focuses on some of the fundamental differences between the Ruby and Windows Forms packages. Specifically, it discusses issues that the Upgrade Wizard does not handle for you. Before we get into the differences, however, let’s look at what Windows Forms and Ruby have in common. Similarities in Form Structure When you create a new project in Visual Basic .NET, you will find yourself at home in the environment. The way you create and design forms is the same in Visual Basic .NET as it is in Visual Basic 6.
    [Show full text]
  • Lecture 1: Introduction to Reverse Engineering
    Boston, 2001 Table of Contents Table of Contents Table of Contents............................................................................................. 2 1. Introduction................................................................................................. 5 1.1 About the Course and Notes ............................................................................ 5 1.2 Definitions...................................................................................................... 5 1.3 Typical Examples ............................................................................................ 6 1.3.1 Hacking ................................................................................................... 7 1.3.2 Hiding Information from Public .................................................................. 7 1.3.3 Cell Phones ............................................................................................ 10 1.3.4 Computer Applications ............................................................................ 10 1.4 Requirements............................................................................................... 12 1.5 Scope .......................................................................................................... 13 1.6 Ethics .......................................................................................................... 13 1.7 Miscellaneous Information ............................................................................. 14 2. Programming Processors
    [Show full text]
  • VI. Lotus Domino
    Le groupware - 1 / 60 - Sommaire I. Introduction ................................................................................................ 2 A. Histoire (Source : Michel Alberganti) ................................................................................ 2 B. Définition................................................................................................................... 2 C. L'offre....................................................................................................................... 2 1. Intranet / Internet................................................................................................. 2 2. Messagerie........................................................................................................... 3 II. Les clients de messagerie ............................................................................... 3 A. Windows Messaging : Msmail........................................................................................... 4 1. Installer et administrer un bureau de poste .................................................................. 4 2. Propriétés du client MAPI......................................................................................... 7 B. Utiliser Outlook ......................................................................................................... 15 1. Les options .........................................................................................................15 2. Envoi de messages ................................................................................................20
    [Show full text]
  • OEM Windows Co-Brand Guide
    OEM Windows Co-Brand Guide March, 2016 Microsoft Confidential Welcome to the OEM Windows Co-Brand Guide! This guide contains important Windows 10 and Office brand elements and guidelines to help tell our brand story together. Our logo is a window—and an iconic symbol known the world over. This symbol has an active feeling to it, representing a person’s unique perspective on their world. When communicating general Windows brand information, use the Windows logo with no The Windows logo includes the Windows symbol and logotype, which version attached. must be used together in a horizontal lockup. The symbol must not be used by itself, and OEMs must not put a box, circle, or other confining When the conversation is shape around the Windows logo. specific to Windows 10 or Trademark symbols highlighting Windows 10 specific features, always use the Logos provided without trademark symbols (TM and ®) should Windows 10 logo lockup. be used in marketing materials only. Trademark symbols are still required in certain places in and on product, and on Minimum size product packaging. More trademark information http://www.microsoft.com/en- us/legal/intellectualproperty/Trademarks/EN-US.aspx Clear space Clear space We respect the logo by giving it some space. The preferred clear space is equivalent to the height of the symbol. Minimum size In print, the logo should never appear smaller than 1” (25 mm). On-screen, it must appear at least 70 pixels wide. Download the Windows logo here: https://omap.microsoft.com/ The Logo Artwork Is Available in Three sizes Windows Logo Color Select the appropriate asset by determining the height Contrast is important — use a white logo on color backgrounds and required for your layout.
    [Show full text]
  • BCM 4.0 Unified Messaging Configuration Guide
    BCM 4.0 Unified Messaging Configuration Guide Business Communications Manager BCM 4.0 Document Status:Beta Document Version: 1.0 Part Code: N0060611 Date: January 2006 Copyright © Nortel Networks Limited 2006 All rights reserved. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Trademarks *Nortel, Nortel (Logo), the Globemark, and This is the way, This is Nortel (Design mark) are trademarks of Nortel Networks. *Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Citrix is a registered trademark of Citrix Systems, Inc. All other trademarks and registered trademarks are the property of their respective owners. Revision history 3 Revision history July 2005 Draft document submitted for external technical review. Review comments received and incorporated. January 2006 Beta document submitted. BCM 4.0 Unified Messaging Configuration Guide 4 Revision history N0060611 5 Task List Getting started . 9 Configuring your system for Unified Messaging . 15 To check that Business Communications Manager is not configured to use DNS........17 To check that a Host Name is entered on the Business Communications Manager.....17 To configure access
    [Show full text]
  • Managed Services Guide for Unity
    Cisco Unified Communications MIBs, Syslogs, and Alerts/Alarms for Managed Service Providers For Cisco Unity Release 7.0(2) Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-19789-01 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • The Expert's Guide for Exchange 2003 Preparing For, Moving To, and Supporting Exchange Server 2003
    The Expert's Guide for Exchange 2003 Preparing for, Moving to, and Supporting Exchange Server 2003 by Steve Bryant iii Books Contents Chapter 3 Consolidating Your Exchange Services . 34 Server Ownership Costs . 34 Exchange Server Proliferation . 34 Consolidating Protocols . 35 Exchange 2003 and AD . 37 Front-End Exchange Servers . 39 Front-End Servers and Performance . 45 Balancing Front-End and Back-End Servers . 45 Consolidating Servers . 46 Storage Space and Recovery . 46 Configuration and Memeory . 47 Mailbox Consolidation Concerns . 47 Creating Server Redundancy . 48 Spreading the Load . 48 Clustering . 48 Deploying High- or Continuous-Availability Servers . 50 Consolidating Mailbox Servers . 50 Move Mailbox Tool . 50 Consolidating Sites . 51 Consolidating Your Exchange Organization . 52 Consolidating Exchange 2003 and Exchange 2000 Organizations . 52 Tools for Merging Exchange Organizations . 53 Using the Exchange Migration Wizard . 53 Copying Public Folder Data . 53 Copying the Organizational Forms Library . 54 Copying Contacts from One Organization to Another . 54 Collecting Group Distribution Memebership . 55 Completing the Consolidation . 57 More Consolidation Details . 64 Next: Installing Exchange 2003 . 64 34 Chapter 3: Consolidating Your Exchange Services At the heart of most successful and cost-effective Microsoft Exchange 2003 and Exchange 2000 deployments lies consolidation. Fewer Exchange servers translates to fewer server licenses, smaller data centers, easier administration, and a reduced cost of doing business. These benefits of consolidation are often the desired end results that prompt – and justify budgets for – upgrading and consolidating Exchange deployments. Estimating the savings that your consolidation efforts can realize will require some intelligent speculation because you’ll derive your overall savings from multiple sources.
    [Show full text]
  • Softice Patch
    Softice patch click here to download SoftICE is a kernel mode debugger for Microsoft Windows up to Windows XP. Crucially, it is Newer versions of SoftICE patch deep into Microsoft Windows. i have installed softice along with the windows xp patch. When i go to start softice however i get a message stating 16 bit MS-DOS Subsystem. THE SOFTiCE PRESERVATiON SOCiETY - NuMega SoftICE v NT with XP patch & French keyboard. Compuware DriverStudio v Compuware. WindowsXP-deadlyxdose crack Softice +Patch&Serial keygen >> Download Actual patch SoftICE Depositfiles. SoftICE from "SoftICE Driver Suite " is used for debugging my program. Even I try the patch, softice still doesn't break!! mesfet. 年11月18日 Softice patch serial. It is designed to run underneath windows such that the operating system isconvert softice v3. Softice patch serial. SoftICE/Win 95 Patch clavier QWERTY -> AZERTY 4 APR 97 SoftICE Command Reference 30 MAR 97 SoftICE User Guide 30 MAR Even if Softice is not running, Skype complains with this error message and then exits: "Skype is not To patch Skype, I've used Ollydbg, a free debugger. Loading SoftICE for Windows 9x. .. Using Windows NT//XP Symbol (DBG) Files with SoftICE. to prevent SoftICE from patching the keyboard driver. SoftICE can be used for local kernel debugging, which is a feature that is very Very useful for patching, disassembling, and debugging. www.doorway.ru accessories: ice iron on patches cute soft ice applique as iron-on badge made of denim to embellish your jeans jacket or repair your pants as knee patches. An uninstall of Softice is required for correct.
    [Show full text]
  • Configuring Mail Clients to Send Plain ASCII Text 3/13/17 2:19 PM
    Configuring Mail Clients to Send Plain ASCII Text 3/13/17 2:19 PM Sign In Sign-Up We have copied this page for reference in case it disappears from the web. The copyright notice appears at the end. If you want the latest version go to the original page: http://www.expita.com/nomime.html Turning Off HTML or MIME to use a Remailer System. Index (5 topics) Introduction E-mail client programs (Turning Off HTML or MIME to use a Remailer System) Suggestions for HTML users Examples of HTML/MIME messages References What is wrong with sending HTML or MIME messages? There are now six main reasons for NOT doing this: 1. Many E-mail and Usenet News reader programs, usually the mail and news reader programs that come with browser packages, allow users to include binary attachments (MIME or other encoding) or HTML (normally found on web pages) within their E-mail messages. This makes URLs into clickable links and it means that graphic images, formatting, and even color coded text can also be included in E-mail messages. While this makes your E-mail interesting and pretty to look at, it can cause problems for other people who receive your E- mail because they may use different E-mail programs, different computer systems, and different application programs whose files are often not fully compatible with each other. Any of these can cause trouble with in-line HTML (or encoded attachments). Most of the time all they see is the actual HTML code behind the message. And if someone replies to the HTML formatted message, the quoting can render the message even more unreadable.
    [Show full text]
  • Mastering Windows XP Registry
    Mastering Windows XP Registry Peter Hipson Associate Publisher: Joel Fugazzotto Acquisitions and Developmental Editor: Ellen L. Dendy Editor: Anamary Ehlen Production Editor: Elizabeth Campbell Technical Editor: Donald Fuller Electronic Publishing Specialist: Maureen Forys, Happenstance Type-O-Rama Proofreaders: Nanette Duffy, Emily Hsuan, Laurie O'Connell, Yariv Rabinovitch, Nancy Riddiough Book Designer: Maureen Forys, Happenstance Type-O-Rama Indexer: Ted Laux Cover Designer: Design Site Cover Illustrator: Sergie Loobkoff Copyright © 2002 SYBEX Inc., 1151 Marina Village Parkway, Alameda, CA 94501. World rights reserved. The author(s) created reusable code in this publication expressly for reuse by readers. Sybex grants readers limited permission to reuse the code found in this publication or its accompanying CD-ROM so long as the author is attributed in any application containing the reusable code and the code itself is never distributed, posted online by electronic transmission, sold, or commercially exploited as a stand-alone product. Aside from this specific exception concerning reusable code, no part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to photocopy, photograph, magnetic, or other record, without the prior agreement and written permission of the publisher. First edition copyright © 2000 SYBEX Inc. Library of Congress Card Number: 2002100057 ISBN: 0-7821-2987-0 SYBEX and the SYBEX logo are either registered trademarks or trademarks of SYBEX Inc. in the United States and/or other countries. Mastering is a trademark of SYBEX Inc. Screen reproductions produced with FullShot 99. FullShot 99 © 1991-1999 Inbit Incorporated. All rights reserved.FullShot is a trademark of Inbit Incorporated.
    [Show full text]
  • Browser Security Comparison – a Quantitative Approach Page| I of V Version 0.0 Revision Date: 12/6/2011
    Browser Security Comparison A Quantitative Approach Document Profile Version 0.0 Published 12/6/2011 Revision History Version Date Description 0.0 12/26/2011 Document published. Browser Security Comparison – A Quantitative Approach Page| i of v Version 0.0 Revision Date: 12/6/2011 Contents Authors .......................................................................................................................................................... v Executive Summary ....................................................................................................................................... 1 Methodology Delta ................................................................................................................................... 1 Results ....................................................................................................................................................... 2 Conclusion ................................................................................................................................................. 2 Introduction .................................................................................................................................................. 3 Analysis Targets ........................................................................................................................................ 4 Analysis Environment................................................................................................................................ 4 Analysis
    [Show full text]