DOCSLIB.ORG

Reassembleable Disassembling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Reassembleable Disassembling Reassembleable Disassembling Shuai Wang, Pei Wang, and Dinghao Wu, The Pennsylvania State University https://www.usenix.org/conference/usenixsecurity15/technical-sessions/presentation/wang-shuai This paper is included in the Proceedings of the 24th USENIX Security Symposium August 12–14, 2015 • Washington, D.C. ISBN 978-1-939133-11-3 Open access to the Proceedings of the 24th USENIX Security Symposium is sponsored by USENIX Reassembleable Disassembling Shuai Wang, Pei Wang, and Dinghao Wu College of Information Sciences and Technology The Pennsylvania State University szw175, pxw172, dwu @ist.psu.edu { } Abstract struction level to enforce certain security policies. To ensure program control-flow integrity (CFI, meaning that Reverse engineering has many important applications in program execution is dictated to a predetermined control- computer security, one of which is retrofitting software flow graph) [1, 4, 43, 17, 29, 37] without source code, the for safety and security hardening when source code is not original control-flow graph must be recovered from a bi- available. By surveying available commercial and aca- nary executable and the binary must be retrofitted with demic reverse engineering tools, we surprisingly found the CFI enforcement facility embedded [50, 49]. Sym- that no existing tool is able to disassemble executable bolic taint analysis [34] on binaries must recover assem- binaries into assembly code that can be correctly assem- bly code and data faithfully. The defending techniques bled back in a fully automated manner, even for simple against return-oriented programming (ROP) attacks also programs. Actually in many cases, the resulted disas- rely on binary analysis and reconstruction to identify and sembled code is far from a state that an assembler ac- eliminate ROP gadgets [44, 9, 47, 22, 39]. cepts, which is hard to fix even by manual effort. This Despite the fact that many security hardening tech- has become a severe obstacle. People have tried to over- niques are highly dependent on reverse engineering, flex- come it by patching or duplicating new code sections for ible and easy-to-use binary manipulation itself remains retrofitting of executables, which is not only inefficient an unsolved problem. Current binary decompilation, but also cumbersome and restrictive on what retrofitting analysis, and reconstruction techniques still cannot fully techniques can be applied to. fulfill many of the requirements from downstream. To In this paper, we present UROBOROS, a tool that can the best of our knowledge, there is no reverse engineer- disassemble executables to the extent that the gener- ing tool that can disassemble an executable into assem- ated code can be assembled back to working binaries bly code which can be reassembled back in a fully au- without manual effort. By empirically studying 244 tomated manner, especially when the processed objects binaries, we summarize a set of rules that can make are commercial-off-the-shelf (COTS) binaries with most the disassembled code relocatable, which is the key to symbol and relocation information stripped. reassembleable disassembling. With UROBOROS, the We have investigated many existing tools from both disassembly-reassembly process can be repeated thou- the industry and academia, including IDA Pro [24], sands of times. We have implemented a prototype of Phoenix [42], Dagger [12], MC-Semantics [32], Second- UROBOROS and tested over the whole set of GNU Core- Write [3], BitBlaze [45], and BAP [8]. Unfortunately, utils, SPEC2006, and a set of other real-world applica- these tools focus more on recovering as much informa- tion and server programs. The experiment results show tion, such as data and control structures, as possible for that our tool is effective with a very modest cost. analysis purpose mainly, but less on producing assembly code that can be readily assembled back without manual 1 Introduction effort. Hence, none of them provide the desired disas- sembly and reassembly functionality that we consider, In computer security, many techniques and applications even if the processed binary is small and simple. depend on binary reverse engineering, i.e., analyzing and Due to lack of support from reverse engineering tools, retrofitting software binaries with the source code un- people build high-level security hardening applications available. For example, software fault isolation (SFI) based on partial binary retrofitting techniques, including [33, 46, 2, 19, 18] rewrites untrusted programs at the in- binary rewriting tools such as Alto [35], Vulcan [16], USENIX Association 24th USENIX Security Symposium 627 Diablo [13], and binary reuse tools such as BCR [11] support from existing tools. We have confirmed that the and TOP [48]. We consider binary rewriting as a par- key to reassembility is making the assembly code relo- tial retrofitting technique because it can only instrument catable. Relocation is a linker concept, which is basi- or patch binaries, thus not suitable for program-wide cally for ensuring program elements defined in different transformations and reconstructions. As for binary reuse source files can correctly refer to each other after linked tools, they work by dynamically recording execution together. Being relocatable is also a premise for support- traces and combining the traces back to an executable, ing program-wide assembly transformations. In COTS meaning the new binary is only an incomplete part of binaries, however, the information necessary for mak- the original binary due to the incomplete coverage of dy- ing disassembly results relocatable is mostly unavailable. namic program analysis. There has been research trying to address the relocation Partial retrofitting has notable drawbacks and limita- issue [11, 48, 26], but existing work mostly relies on dy- tions: namic analysis which is unlikely to cover the whole pro- gram. • Patch-based rewriting could introduce non- In this paper, we present UROBOROS, a disassembler negligible runtime overhead. Since the patch that does reassembleable disassembling. In UROBOROS, usually lives in an area different from the original we develop a set of methods to precisely recover each code of the binary, interactions between the patch part of a binary executable. In particular, we are the and the original code usually require a large amount first to be capable of not only recovering code, but also of control-flow transfers. data and meta-information from COTS binaries with- • Patch-based rewriting usually relocates instructions out manual effort. We have implemented a prototype at the patch point to somewhere else to make space of UROBOROS and tested it on 244 binaries, including for the inserted code. As a result, it requires the the whole set of GNU Coreutils and the C programs in affected instructions to be relocatable by default. SPEC2006 (including both 32-bit and 64-bit versions). In our experiments, most programs reassembled from • Instrumentation-based rewriting expands binary UROBOROS’s output can pass functionality tests with sizes significantly, sometimes generating nearly negligible execution overhead, even after repeated dis- double-sized products. assembly and reassembly. Our preliminary study shows that UROBOROS can provide support for program-wide • Binary reuse often requires a binary component to transformations on COTS binaries. be small enough for dynamic analysis to cover; oth- In summary, we make the following contributions: erwise the correctness cannot be guaranteed. • We initiate a new focus on reverse engineering. Having investigated previous research on binary ma- Complementary to historical work which mostly fo- nipulation and reconstruction, we believe that it could be cuses on recovering high-level semantic informa- a remarkable improvement if we are able to automati- tion from binary executables or providing support cally recover the assembly from binaries and make the for binary analysis, our work seeks to deliver re- assembly code ready for reassembly. When a binary assembility, meaning we disassembles binaries in a can be reconstructed from assembly code, many high- way that the disassembly results could be directly level and program-wide transformations become feasi- assembled back into working executables, without ble, leading to new opportunities for research based on manual edits. binary retrofitting such as CFI, diversification, and ROP defense. • We identify the key challenge is to make the disas- Our goal is quite different from previous reverse engi- sembled program relocatable, and propose our key neering research. Instead of trying to recover high-level technique to recover references among immediate data and control structures from program binaries which values in the disassembled code, namely “symbol- helps binary code analysis, we aim at a more basic objec- ization”. tive, i.e., producing assembly code that can be readily re- • With reassembility, our research enables direct assembled back without manual effort, which we call the binary-based transformation without resort to the reassembility of disassembling. Although the research previously used patching method, and can poten- community has made notable progress on binary reverse tially become the foundation of binary-based soft- engineering, reassembility is still somewhat a blank due ware retrofitting. to lack of attention. In this sense, our contribution is complementary to existing work. • We implement a prototype of UROBOROS and eval- With that said, we believe that the technical challenge uate its strength on
Load more

Recommended publications
  • Fill Your Boots: Enhanced Embedded Bootloader Exploits Via Fault Injection and Binary Analysis
    IACR Transactions on Cryptographic Hardware and Embedded Systems ISSN 2569-2925, Vol. 2021, No. 1, pp. 56–81. DOI:10.46586/tches.v2021.i1.56-81 Fill your Boots: Enhanced Embedded Bootloader Exploits via Fault Injection and Binary Analysis Jan Van den Herrewegen1, David Oswald1, Flavio D. Garcia1 and Qais Temeiza2 1 School of Computer Science, University of Birmingham, UK, {jxv572,d.f.oswald,f.garcia}@cs.bham.ac.uk 2 Independent Researcher, [email protected] Abstract. The bootloader of an embedded microcontroller is responsible for guarding the device’s internal (flash) memory, enforcing read/write protection mechanisms. Fault injection techniques such as voltage or clock glitching have been proven successful in bypassing such protection for specific microcontrollers, but this often requires expensive equipment and/or exhaustive search of the fault parameters. When multiple glitches are required (e.g., when countermeasures are in place) this search becomes of exponential complexity and thus infeasible. Another challenge which makes embedded bootloaders notoriously hard to analyse is their lack of debugging capabilities. This paper proposes a grey-box approach that leverages binary analysis and advanced software exploitation techniques combined with voltage glitching to develop a powerful attack methodology against embedded bootloaders. We showcase our techniques with three real-world microcontrollers as case studies: 1) we combine static and on-chip dynamic analysis to enable a Return-Oriented Programming exploit on the bootloader of the NXP LPC microcontrollers; 2) we leverage on-chip dynamic analysis on the bootloader of the popular STM8 microcontrollers to constrain the glitch parameter search, achieving the first fully-documented multi-glitch attack on a real-world target; 3) we apply symbolic execution to precisely aim voltage glitches at target instructions based on the execution path in the bootloader of the Renesas 78K0 automotive microcontroller.
    [Show full text]
  • Radare2 Book
    Table of Contents introduction 1.1 Introduction 1.2 History 1.2.1 Overview 1.2.2 Getting radare2 1.2.3 Compilation and Portability 1.2.4 Compilation on Windows 1.2.5 Command-line Flags 1.2.6 Basic Usage 1.2.7 Command Format 1.2.8 Expressions 1.2.9 Rax2 1.2.10 Basic Debugger Session 1.2.11 Contributing to radare2 1.2.12 Configuration 1.3 Colors 1.3.1 Common Configuration Variables 1.3.2 Basic Commands 1.4 Seeking 1.4.1 Block Size 1.4.2 Sections 1.4.3 Mapping Files 1.4.4 Print Modes 1.4.5 Flags 1.4.6 Write 1.4.7 Zoom 1.4.8 Yank/Paste 1.4.9 Comparing Bytes 1.4.10 Visual mode 1.5 Visual Disassembly 1.5.1 2 Searching bytes 1.6 Basic Searches 1.6.1 Configurating the Search 1.6.2 Pattern Search 1.6.3 Automation 1.6.4 Backward Search 1.6.5 Search in Assembly 1.6.6 Searching for AES Keys 1.6.7 Disassembling 1.7 Adding Metadata 1.7.1 ESIL 1.7.2 Scripting 1.8 Loops 1.8.1 Macros 1.8.2 R2pipe 1.8.3 Rabin2 1.9 File Identification 1.9.1 Entrypoint 1.9.2 Imports 1.9.3 Symbols (exports) 1.9.4 Libraries 1.9.5 Strings 1.9.6 Program Sections 1.9.7 Radiff2 1.10 Binary Diffing 1.10.1 Rasm2 1.11 Assemble 1.11.1 Disassemble 1.11.2 Ragg2 1.12 Analysis 1.13 Code Analysis 1.13.1 Rahash2 1.14 Rahash Tool 1.14.1 Debugger 1.15 3 Getting Started 1.15.1 Registers 1.15.2 Remote Access Capabilities 1.16 Remoting Capabilities 1.16.1 Plugins 1.17 Plugins 1.17.1 Crackmes 1.18 IOLI 1.18.1 IOLI 0x00 1.18.1.1 IOLI 0x01 1.18.1.2 Avatao 1.18.2 R3v3rs3 4 1.18.2.1 .intro 1.18.2.1.1 .radare2 1.18.2.1.2 .first_steps 1.18.2.1.3 .main 1.18.2.1.4 .vmloop 1.18.2.1.5 .instructionset 1.18.2.1.6
    [Show full text]
  • The UN Works for International Peace and Security
    Did You Know? 7 Since 1945, the UN has assisted in negotiating more than 170 peace settlements that have ended regional conflicts. 7 The United Nations played a role in bringing about independence in more than 80 countries that are now sovereign nations. 7 Over 500 multinational treaties – on human rights, terrorism, international crime, refugees, disarmament, commodities and the oceans – have been enacted through the efforts of the United Nations. 7 The World Food Programme, the world’s largest humanitarian agency, reaches on average 90 million hungry people in 80 countries every year. 7 An estimated 90 per cent of global conflict-related deaths since 1990 have been civilians, and 80 percent of these have been women and children. 7 If each poor person on the planet had the same energy-rich lifestyle as an average person in Germany or the United Kingdom, four planets would be needed to safely cope with the pollution. That figure rises to nine planets when compared with the average of the United States or Canada. 07-26304—DPI/1888/Rev.3—August 2008—15M Everything You Always Wanted to Know About the United Nations FOR STUDENTS AT INTERMEDIATE AND SECONDARY LEVELS United Nations Department of Public Information New York, 2010 An introduction to the United Nations i Material contained in this book is not subject to copyright. It may be freely reproduced, provided acknowledgement is given to the UNITED NATIONS. For further information please contact: Visitors Services, Department of Public Information, United Nations, New York, NY 10017 Fax 212-963-0071; E-mail: [email protected] All photos by UN Photo, unless otherwise noted Published by the United Nations Department of Public Information Printed by the United Nations Publishing Section, New York Table of contents 1 Introduction to the United Nations .
    [Show full text]
  • Reverse Software Engineering As a Project-Based Learning Tool
    Paper ID #33764 Reverse Software Engineering as a Project-Based Learning Tool Ms. Cynthia C. Fry, Baylor University CYNTHIA C. FRY is currently a Senior Lecturer of Computer Science at Baylor University. She worked at NASA’s Marshall Space Flight Center as a Senior Project Engineer, a Crew Training Manager, and the Science Operations Director for STS-46. She was an Engineering Duty Officer in the U.S. Navy (IRR), and worked with the Naval Maritime Intelligence Center as a Scientific/Technical Intelligence Analyst. She was the owner and chief systems engineer for Systems Engineering Services (SES), a computer systems design, development, and consultation firm. She joined the faculty of the School of Engineering and Computer Science at Baylor University in 1997, where she teaches a variety of engineering and computer science classes, she is the Faculty Advisor for the Women in Computer Science (WiCS), the Director of the Computer Science Fellows program, and is a KEEN Fellow. She has authored and co- authored over fifty peer-reviewed papers. Mr. Zachary Michael Steudel Zachary Steudel is a 2021 graduate of Baylor University’s computer science department. In his time at Baylor, he worked as a Teaching Assistant under Ms. Cynthia C. Fry. As part of the Teaching Assistant role, Zachary designed and created the group project for the Computer Systems course. Zachary Steudel worked as a Software Developer Intern at Amazon in the Summer of 2019, a Software Engineer Intern at Microsoft in the Summer of 2020, and begins his full-time career with Amazon in the summer of 2021 as a software engineer.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Reassembleable Disassembling
    Reassembleable Disassembling Shuai Wang, Pei Wang, and Dinghao Wu College of Information Sciences and Technology The Pennsylvania State University fszw175, pxw172, [email protected] Abstract struction level to enforce certain security policies. To ensure program control-flow integrity (CFI, meaning that Reverse engineering has many important applications in program execution is dictated to a predetermined control- computer security, one of which is retrofitting software flow graph) [1,4, 43, 17, 29, 37] without source code, the for safety and security hardening when source code is not original control-flow graph must be recovered from a bi- available. By surveying available commercial and aca- nary executable and the binary must be retrofitted with demic reverse engineering tools, we surprisingly found the CFI enforcement facility embedded [50, 49]. Sym- that no existing tool is able to disassemble executable bolic taint analysis [34] on binaries must recover assem- binaries into assembly code that can be correctly assem- bly code and data faithfully. The defending techniques bled back in a fully automated manner, even for simple against return-oriented programming (ROP) attacks also programs. Actually in many cases, the resulted disas- rely on binary analysis and reconstruction to identify and sembled code is far from a state that an assembler ac- eliminate ROP gadgets [44,9, 47, 22, 39]. cepts, which is hard to fix even by manual effort. This Despite the fact that many security hardening tech- has become a severe obstacle. People have tried to over- niques are highly dependent on reverse engineering, flex- come it by patching or duplicating new code sections for ible and easy-to-use binary manipulation itself remains retrofitting of executables, which is not only inefficient an unsolved problem.
    [Show full text]
  • A.5.1. Linux Programming and the GNU Toolchain
    Making the Transition to Linux A Guide to the Linux Command Line Interface for Students Joshua Glatt Making the Transition to Linux: A Guide to the Linux Command Line Interface for Students Joshua Glatt Copyright © 2008 Joshua Glatt Revision History Revision 1.31 14 Sept 2008 jg Various small but useful changes, preparing to revise section on vi Revision 1.30 10 Sept 2008 jg Revised further reading and suggestions, other revisions Revision 1.20 27 Aug 2008 jg Revised first chapter, other revisions Revision 1.10 20 Aug 2008 jg First major revision Revision 1.00 11 Aug 2008 jg First official release (w00t) Revision 0.95 06 Aug 2008 jg Second beta release Revision 0.90 01 Aug 2008 jg First beta release License This document is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License [http:// creativecommons.org/licenses/by-nc-sa/3.0/us/]. Legal Notice This document is distributed in the hope that it will be useful, but it is provided “as is” without express or implied warranty of any kind; without even the implied warranties of merchantability or fitness for a particular purpose. Although the author makes every effort to make this document as complete and as accurate as possible, the author assumes no responsibility for errors or omissions, nor does the author assume any liability whatsoever for incidental or consequential damages in connection with or arising out of the use of the information contained in this document. The author provides links to external websites for informational purposes only and is not responsible for the content of those websites.
    [Show full text]
  • A Survey of Reverse Engineering Tools for the 32-Bit Microsoft Windows Environment
    A Survey of Reverse Engineering Tools for the 32-Bit Microsoft Windows Environment RAYMOND J. CANZANESE, JR., MATTHEW OYER, SPIROS MANCORIDIS, and MOSHE KAM College of Engineering Drexel University, Philadelphia, PA, USA Reverse engineering is defined by Chikosfky and Cross as the process of analyzing a subject system to identify the system's components and their relationships, and to create representations of the system in another form or at a higher level of abstraction. The process of reverse engineering is accomplished using specific tools that, for the 32-bit Microsoft Windows environment, are categorized as hex editors, disassemblers/debuggers, decompilers, or related technologies such as code obfuscators, unpackers, and PE editors. An evaluation of each tool is provided that identifies its domain of applicability and usability. Categories and Subject Descriptors: A.1 [General]: Introductory and Survey; D.2.5 [Software Engineering]: Testing and Debugging General Terms: Security, Documentation Additional Key Words and Phrases: Reverse Engineering, Disassemblers, Debuggers, Decompilers, Code Obfuscators, PE Editors Unpackers, Hex Editors 1. INTRODUCTION 1.1 The Reverse Engineering Process Software engineers are sometimes asked to understand the behavior of a program given that program's binary executable file. If they have access to the appropriate reverse engineering tools, they might choose to adhere to the following process. First, a general disassembler/debugger is used to determine the basic functionality of the program. If disassembly and debugging shows that the binary code has been obfuscated, the next step would be to determine whether the obfuscator used is a common commercial obfuscator or a custom protection scheme. A PE editor would be used to make this determination.
    [Show full text]
  • Implementing the UCSD PASCAL System on the MODCOMP Computer
    TDA Progress Report 42-60 September and October 1960 Implementing the UCSD PASCAL System on the MODCOMP Computer T. Wolfe DSN Data Systems Section This article describes the UCSD PASCAL system developed by the University of California, San Diego, now available on the MODCOMP computer. The system includes a Pascal compiler and many useful utility programs. A BASIC compiler and a FORTRAN 77 compiler are also avatkble. There is currently a large amount of software availabie written in UCSD PASCAL, including a data base system, word processing systems and a MODULA compiler. I. Introduction Assembly language subroutines thus produced may also be called from either Pascal or FORTRAN. Currently the assem- The UCSD PASCAL* System is a complete interactive bler has not been modified to produce MODCOMP machine software development system consisting of an operating sys- code. A system library program may be used to build libraries tem, compilers (Pascal, BASIC, FORTRAN 77) two text of useful subroutines and the system linker used to link them editors (screen editor and line-oriented editor), a linker and to user programs. many useful utility programs. The system is written and main- tained in Pascal. The compiler generates code for an idealized processor known as the “pseudo-machine.” The “pseudo- Interpreters currently exist for Z80/8080, PDP 11 /LSI-1 1, code” (p-code) generated by the compiler is interpreted at 6800, 9900 and 6502 computers and are being developed for runtime by a program (known as the interpreter) which emu- other computers. Thus, software could be developed on an lates the pseudo-machine.
    [Show full text]
  • Rome Statute of the International Criminal Court
    Rome Statute of the International Criminal Court The text of the Rome Statute reproduced herein was originally circulated as document A/CONF.183/9 of 17 July 1998 and corrected by procès-verbaux of 10 November 1998, 12 July 1999, 30 November 1999, 8 May 2000, 17 January 2001 and 16 January 2002. The amendments to article 8 reproduce the text contained in depositary notification C.N.651.2010 Treaties-6, while the amendments regarding articles 8 bis, 15 bis and 15 ter replicate the text contained in depositary notification C.N.651.2010 Treaties-8; both depositary communications are dated 29 November 2010. The table of contents is not part of the text of the Rome Statute adopted by the United Nations Diplomatic Conference of Plenipotentiaries on the Establishment of an International Criminal Court on 17 July 1998. It has been included in this publication for ease of reference. Done at Rome on 17 July 1998, in force on 1 July 2002, United Nations, Treaty Series, vol. 2187, No. 38544, Depositary: Secretary-General of the United Nations, http://treaties.un.org. Rome Statute of the International Criminal Court Published by the International Criminal Court ISBN No. 92-9227-232-2 ICC-PIOS-LT-03-002/15_Eng Copyright © International Criminal Court 2011 All rights reserved International Criminal Court | Po Box 19519 | 2500 CM | The Hague | The Netherlands | www.icc-cpi.int Rome Statute of the International Criminal Court Table of Contents PREAMBLE 1 PART 1. ESTABLISHMENT OF THE COURT 2 Article 1 The Court 2 Article 2 Relationship of the Court with the United Nations 2 Article 3 Seat of the Court 2 Article 4 Legal status and powers of the Court 2 PART 2.
    [Show full text]
  • 1958 9Th Special Session Journal of The
    THE JOURNAL OF THE ASSEMBLY CH' THE SPECIAL SESSION LEGISLATURE OF THE STATE OF NEVADA 1958 BEGUN ON MONDAY, THE THIRTIETH DAY OF JUNE, AND ENDED ON TUESDAY, THE FIRST DAY OF JULY CARSON C ITY. NEVADA STATE PRINTING OFFICE - - JACK MCCARTHY, STATE PRINTER 1958 ARRANGEMENT AND CONTENTS OF VOLUME l'AGE Ll£GISLAT1VE CALl£NlJAl-L ..................................-..................................... ........ V INDEX TO ASSEMBLY BILLS...................................... ............... ..................... VI I:-.rDEX TO ASSEMBLY RESOLUTIONS AND MEMORIALS ......_. .. ........ VII I :'>/UI<;X TO SENA'l'E BILLS................................................................................. VII l'F.R80 'KEL OF THl£ K:l£VADA ASSEMBLY ............................................... VIII .\.SSE:\lBLY PROCEEDINGS.................................................................................. 1 NOTE: Due to the brevit y of the 1958 Special Session t here is no Genera l Index to the proceedings in this volume. ASSEMBLY LEGISLATIVE CALENDAR Lef}iS IC&t-ive day Date Page number l ...................................... June 30, 1958.... ............................................ l 2 ...................................... Jnly 1, 1958..... ............................................. 11 INDEX TO ASSEMBLY BILLS No. 1'i.tle, Jnti·ucZ.we1· and Page 1.... An Act directing the employment security departme nt of the State of Nevada to enter into an agreement with the Secretary of Labor to provide for temporary unemployment compensation paymen ts under
    [Show full text]
  • V850 Series Development Environment Pamphlet
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]