DOCSLIB.ORG

Using Cisco IOS for S/390 API and Socket Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using Cisco IOS for S/390 API and Socket Applications CHAPTER 10 Using Cisco IOS for S/390 API and Socket Applications This chapter describes some API and socket application programs that you might find useful. It includes these sections: • What Example Applications are Provided? Briefly describes how these examples are presented and their uses. • ACSHELLO This TSO command acts as a server that can be queried by clients to obtain information about the host on which the ACSHELLO program is executing. • FINGER This TSO command obtains information about users of a system. • TTCP This TSO command acts as a data source or sink facility. • WHOIS This TSO command queries a default or user-specified WHOIS server to obtain information about a user-specified name. What Example Applications are Provided? The FINGER, WHOIS, ACSHELLO, and TTCP application programs are provided in load module and source forms to illustrate use of the socket and basic C libraries. The ACSHELLO and WHOIS programs distributed as executable programs were created form the BHELLO and BWHOIS sample code. The TTCP program is provided in load module and source forms as an example of how to use the assembler API macro facilities. Any errors encountered by the programs described in this chapter are indicated to the user by error messages. For information about these error messages, see Cisco IOS for S/390 Prefixed Messages and Codes and Cisco IOS for S/390 Unprefixed Messages. These programs might prove valuable to network users. For more information on additional diagnostic commands, see the Cisco IOS for S/390 Customization Guide. These programs are invoked through TSO or a batch job. Instructions for using each program are provided in the following subsections. Using Cisco IOS for S/390 API and Socket Applications 10-1 ACSHELLO ACSHELLO The ACSHELLO program acts as a server that can be queried by clients to obtain information about the host on which the ACSHELLO program is executing. This is a nonstandard network service but might be useful to users as a demonstration of the network capabilities. It also provides a good example of the implementation of a network server. The program supports access only via TCP. This program runs until canceled or interrupted, or until an unrecoverable error is detected. ACSHELLO [PORT(TCP_port)] [SYSID(subsystem_ID)] Syntax Description ACSHELLO Invokes the ACSHELLO program. PORT(TCP_port) Defines the port the program will use to wait for client requests SYSID( subsystem_ID ) Lets the user specify the subsystem ID of Cisco IOS for S/390 other than the default used when Cisco IOS for S/390 was installed. Usage Notes The default port is 43; it is typically used as the WHOIS TCP service. The default subsystem ID is ACSS. Both the PORT and SYSID parameters are optional. Example The following is sample output of the ACSHELLO program when contacted by a client: ACSHELLO: Server starting at: Wed Feb 07 13:57:27 1990 ACSHELLO: Running on host: MF1.YOURCO.COM ACSHELLO: Host's internet address is: 129.192.192.129 ACSHELLO: MVS version level is: MVS/SP2.2.0 ACSHELLO: MVS SMF ID is: IPO1 ACSHELLO: CPU ID is: 000130614381 ACSHELLO: Server stopping at: Wed Feb 07 13:57:28 1990 Invoking ACSHELLO Typically this program is used by starting its execution on the mainframe and then querying it using Telnet or WHOIS, specifying the port that ACSHELLO is using to listen for requests. If you are using the WHOIS program to query the ACSHELLO server using the default port, invoke the program with this command: WHOIS NAME(ABC) HOST(my_host_name) 10-2 Cisco IOS for S/390 User’s Guide FINGER The FINGER TSO command processor is similar to the UNIX finger command. It obtains information about users of a system. If given only the name of the remote host, FINGER returns information about all users currently logged in on that system. If given the name of a user and the remote host, FINGER returns information about that user. The finger protocol is described in detail in RFC 742. FINGER NAME( lookup_name ) [ LONG ] [ SYSID( subsystem_ID ) ] Syntax Description FINGER is the command used to obtain information about users logged in to a remote host NAME( lookup_name ) specifies the user name for which information is requested LONG provides a more verbose listing of the remote system users' information if the lookup_name specifies only a remote host SYSID( subsystem_ID ) allows you to specify the subsystem ID of Cisco IOS for S/390 other than the default used when Cisco IOS for S/390 was installed Usage Notes: The remote host must be running a finger server program for the client to function properly. To obtain information about a single user, lookup_name should be a string in the form of userid @hostname. To obtain information about all users currently logged on to the host, type @hostname. The user ID is converted to lowercase before it is sent to the remote system. The finger server on the remote system should be case insensitive. The NAME(lookup_name) parameter is required. The LONG parameter is optional. The default subsystem ID is ACSS. The SYSID(subsystem_ID) parameter is optional. Example The following is sample output of the FINGER program: FINGER NAME(gaw@leo) (MF1.YOURCO.COM.) Login name: gaw In real life:..Glen......Directory:/home/gaw Shell: /bin/csh On since Feb 28 14:53:11 on ttyp2 6 hours 19 minutes Idle Time Using Cisco IOS for S/390 API and Socket Applications 10-3 TTCP TTCP The TTCP TSO command processor acts as a data source or sink facility. TTCP is basically a test program for exercising Cisco IOS for S/390 and API functions. TTCP is compatible with the TTCP program available through anonymous FTP for UNIX users. When run in transmit mode, TTCP performs one iteration and exits. When run in receive mode (as a server), TTCP runs until stopped. To stop TTCP when under TSO, use the particular TSO attention key for your terminal. To stop TTCP when running under the TSO TMP in a batch job, use the MVS STOP( P ) command. Any errors encountered by the TTCP program are indicated by error messages. For information about these error messages see Cisco IOS for S/390 Prefixed Messages and Codes. The syntax for the TTCP command is as follows: TTCP[RECEIVE/TRANSMIT] [TCP/UDP] [ASCII/EBCDIC] [ HOST( host_name ) ] [ PORT( port_number ) ] [ SYSID( subsystem_ID ) ] [ BUFLEN( buffer_length ) ] [ BUFNUM( number_of_buffers ) ] [ COUNT( transmit_buffer_count ) ] [ TASKS( number_of_receive_tasks ) ] Syntax Description: TTCP Name of the command to be executed RECEIVE Indicates that TTCP should run as a server to receive and discard (sink) all data from any host and port; RECEIVE may also be specified as RECV or RCV TRANSMIT Indicates that TTCP should run as a client to generate (source) and transmit data to a specified host and port Default is RECEIVE. RECEIVE/TRANSMIT parameter is optional. TCP Indicates that TCP (Transmission Control Protocol) transport services should be used; TCP may also be specified as COTS UDP Indicates that UDP (User Datagram Protocol) transport services should be used; UDP may also be specified as CLTS The default is TCP. The transport protocol parameter is optional. ASCII/EBCDIC In transmit mode, this parameter specifies the character set to use when generating data to be sent. In receive mode, the ASCII/EBCDIC parameter is ignored. ASCII—ASCII character set EBCDIC—EBCDIC character set If not specified in transmit mode, the default is ASCII. The ASCII/EBCDIC parameter is optional 10-4 Cisco IOS for S/390 User’s Guide HOST( host_name ) In transmit mode, the HOST parameter specifies the name of the remote host to which TTCP transmits data. In receive mode, the HOST parameter is ignored.If not specified in transmit mode, the default is 127.0.0.1 (standard loopback Internet address). The HOST parameter is optional. PORT( port_number ) Port number to use If not specified in transmit mode, the default is 9 (standard TCP/UDP discard port); if not specified in receive mode, the default is 2000. The PORT parameter is optional. SYSID( subsystem_ID ) Subsystem ID of the Cisco IOS for S/390 address space other than the default used when Cisco IOS for S/390 was installed. SYSID may also be specified as SSN. The default subsystem ID is ACSS The SYSID parameter is optional. BUFLEN( buffer_length ) Buffer length to be used In transmit mode, COUNT buffers of this length are transmitted. In receive mode, this is the length of each receive buffer. BUFLEN may also be specified as LENGTH If not specified, the default is 1024. The BUFLEN parameter is optional. BUFNUM( number_of_buffers ) Number of buffers to receive into or transmit from simultaneously; that is, the queue depth of buffering If BUFNUM is greater than 1, there will be transmit or receive overlap, which is generally more efficient. BUFNUM may also be specified as NUMBER or BUFCT. The default is 5. The BUFNUM parameter is optional. COUNT( transmit_buffer_count ) In transmit mode, COUNT specifies the number of buffers to transmit. COUNT may also be specified as CNT or CT. This parameter is silently ignored in receive mode. If not specified in transmit mode, the default is 1024. TASKS( number_of_receive_tasks ) In receive mode, specifies the maximum number of receive subtasks that can be active to receive data from remote hosts. This equates to the maximum number of remote hosts that can be transmitting to the TTCP receive server simultaneously. TASKS may also be specified as SUBTASKS. This parameter is silently ignored in transmit mode. The TASK parameter is optional; if not specified in receive mode, the default is 6. Using Cisco IOS for S/390 API and Socket Applications 10-5 TTCP Examples • The following is sample output of the TTCP program when in transmit mode: TTCPT: TRANSFER SECONDS 5.5 TSEND'S 1024, TSEND'S/SEC 185.5 BYTES SENT 1048576, BYTES/SEC 189959.4 • The following is sample output of the TTCP program when in receive mode: TTCPR: TRANSFER SECONDS 9.6 TRECV'S 1024, TRECV'S/SEC 34.6 BYTES RECEIVED 048576, BYTES/SEC 35448.8 10-6 Cisco IOS for S/390 User’s Guide WHOIS The WHOIS TSO command processor acts as a WHOIS client and queries a default or user-specified WHOIS server to obtain information about a user-specified name.
Load more

Recommended publications
  • Dig, a DNS Query Tool for Windows and Replacement for Nslookup 2008-04-15 15:29
    dig, a DNS query tool for Windows and replacement for nslookup 2008-04-15 15:29 Disclaimer dig (dig for Windows ) (dig is a powerful tool to investigate [digging into] the DNS system) Source of the binary is from ftp.isc.org Manual Page of dig, in the cryptic Unix style, for reference only. (1) Download: Windows 2000 or Windows XP or Windows Vista ( dig version 9.3.2) Create a folder c:\dig Download this dig-files.zip and save it to c:\dig Use winzip or equivalent to extract the files in dig-files.zip to c:\dig Note: If msvcr70.dll already exists in %systemroot%\system32\ , then you can delete c:\dig\msvcr70.dll Note: Included in dig-files.zip is a command line whois, version 4.7.11: The canonical site of the whois source code is http://ftp.debian.org/debian/pool/main/w/whois/ The whois.exe file inside dig-files.zip is compiled using cygwin c++ compiler. (2) Do a file integrity check (why ? Because some virus checkers destroy dll files) Click Start.. Run ... type CMD (a black screen pops up) cd c:\dig sha1 * You should see some SHA1 hashes (in here, SHA1 hash is used as an integrity check, similar to checksums). Compare your hashes with the following table. SHA1 v1.0 [GPLed] by Stephan T. Lavavej, http://stl.caltech.edu 6CA70A2B 11026203 EABD7D65 4ADEFE3D 6C933EDA cygwin1.dll 57487BAE AA0EB284 8557B7CA 54ED9183 EAFC73FA dig.exe 97DBD755 D67A5829 C138A470 8BE7A4F2 6ED0894C host.exe D22E4B89 56E1831F F0F9D076 20EC19BF 171F0C29 libbind9.dll 81588F0B E7D3C6B3 20EDC314 532D9F2D 0A105594 libdns.dll E0BD7187 BBC01003 ABFE7472 E64B68CD 1BDB6BAB libeay32.dll F445362E 728A9027 96EC6871 A79C6307 054974E4 libisc.dll B3255C0E 4808A703 F95C217A 91FFCD69 40E680C9 libisccfg.dll DFBDE4F9 E25FD49A 0846E97F D813D687 6DC94067 liblwres.dll 61B8F573 DB448AE6 351AE347 5C2E7C48 2D81533C msvcr70.dll BDA14B28 7987E168 F359F0C9 DD96866D 04AB189B resolv.conf 1112343A 319C3EEE E44BF261 AE196C96 289C70E2 sha1.exe 21D20035 2A5B64E2 69FEA407 4D78053F 3C7A2738 whois.exe If your hashes are the same as the above table, then your files pass the integrity check.
    [Show full text]
  • How to Investigate and Solve Cybercrime
    1 DomainTools Cybercrime Investigation Connecting the Dots of Online DNA DOMAINTOOLS SOLUTION BRIEF WWW.DOMAINTOOLS.COM WWW.DOMAINTOOLS.COM 2 INTRODUCTION UNDERSTANDING THE DNA OF DNS DATA As anyone who has watched modern crime television knows, DNA of some form is often left behind at the scene of a crime. Similarly, when a cybercrime is perpetrated it is not unusual that traces of evidence are left behind in the form of Domain Name System (DNS) and Whois data. Cybercrime costs businesses billions every year. A 2012 Ponemon study found that cyber crime cost businesses on average $8.9 million each year (based on a study of 56 organizations), with a range of $1.4 million to $46 million. And attacks are becoming more frequent—The same study found that attacks were up 42% from the previous year. Whether it’s cybersquatting, the theft of valuable intellectual property, financial account hacking or the sale of counterfeit goods on a fraudulent domain, cybercriminals continue to grow more brazen and sophisticated in their tactics. To effectively combat this costly criminal behavior, cyber investigators must employ a range of new tools and techniques to quickly and proactively identify attackers. RESPONSE AND INVESTIGATION Whether you are attacked via a DDOS, phishing, malware or Advanced Persistent Threat tactics, one thing is consistent: in every case, there is a communication protocol applied. That is, all types of cyber attack involve sending information from one node on the Internet to another. DomainTools can help map these nodes and their connections, thereby providing investigators and response teams with the necessary information to stop further attacks and identify perpetrators.
    [Show full text]
  • Who Is .Com? Learning to Parse WHOIS Records
    Who is .com? Learning to Parse WHOIS Records Suqi Liu Ian Foster Stefan Savage [email protected] [email protected] [email protected] Geoffrey M. Voelker Lawrence K. Saul [email protected] [email protected] Department of Computer Science and Engineering University of California, San Diego ABSTRACT 1. INTRODUCTION WHOIS is a long-established protocol for querying information about Most common Internet protocols today offer standardized syntax the 280M+ registered domain names on the Internet. Unfortunately, and schemas. Indeed, it is the ability to easily parse and normal- while such records are accessible in a “human-readable” format, ize protocol fields that directly enables a broad array of network they do not follow any consistent schema and thus are challeng- measurement research (e.g., comparing and correlating from dis- ing to analyze at scale. Existing approaches, which rely on manual parate data sources including BGP route tables, TCP flow data and crafting of parsing rules and per-registrar templates, are inherently DNS measurements). By contrast, the WHOIS protocol—the sole limited in coverage and fragile to ongoing changes in data repre- source of information mapping domain names to their rich owner- sentations. In this paper, we develop a statistical model for parsing ship and administrative context—is standard only in its transport WHOIS records that learns from labeled examples. Our model is mechanism, while the format and contents of the registration data a conditional random field (CRF) with a small number of hidden returned varies tremendously among providers. This situation sig- states, a large number of domain-specific features, and parameters nificantly hampers large-scale analyses using WHOIS data, and even that are estimated by efficient dynamic-programming procedures those researchers who do use it commonly document the complexi- for probabilistic inference.
    [Show full text]
  • Getting Started with Domaintools for Cybercrime Investigation
    Best Practices Guide: Getting Started with DomainTools for Threat Intelligence and Incident Forensics Common Attack Vectors Introduction Cybercrime represents a major threat to both government The following four methods represent the most common forms of cyber-attack: and businesses, costing the economy hundreds of billions of dollars in losses every year. Often, the most challenging part DDoS – Distributed Denial of Service: A form of for an investigator is discovering the who behind an attack. Is cyber attack meant to ‘take down’ a website. it a coordinated attack orchestrated by a criminal syndicate By flooding a webserver(s) with traffic from hundreds or thousands of IP addresses or an amateur hacker looking for a backdoor into your simultaneously, a DDoS attack can render a network? If the actual individual cannot be identified—as is webserver unable to respond to normal user too often the case—then investigators can build a Threat requests, effectively making a website Intelligence Profile on the suspect that uniquely “finger inaccessible. prints” the organization and how they act. Threat Phishing: A form of cyber-attack, normally investigators need to use all the tools at their disposal in administered via email, which attempts to trick order to identify the individuals and organizations involved a user into thinking the email is from a trusted in an online attack. DNS and Whois data is an essential tool source, and whose embedded links send a user that should be leveraged by every incident response team. to a fake site which hosts some kind of malware or nefarious attempt to capture the user’s login credentials.
    [Show full text]
  • 1206 FTP Software, Inc. FYI: 4 A. Marine Obsoletes: RFC 1177 SRI February 1991
    Network Working Group G. Malkin Request for Comments: 1206 FTP Software, Inc. FYI: 4 A. Marine Obsoletes: RFC 1177 SRI February 1991 FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions Status of this Memo This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. Distribution of this memo is unlimited. Table of Contents 1. Introduction................................................. 1 2. Acknowledgements............................................. 2 3. Questions About the Internet................................. 2 4. Questions About TCP/IP....................................... 4 5. Questions About the Domain Name System....................... 4 6. Questions About Internet Documentation....................... 5 7. Questions about Internet Organizations and Contacts.......... 9 8. Questions About Services..................................... 13 9. Mailing Lists................................................ 16 10. Miscellaneous "Internet lore" questions..................... 17 11. Suggested Reading........................................... 18 12. References.................................................. 19 13. Condensed Glossary.......................................... 20 14. Security Considerations....................................
    [Show full text]
  • From WHOIS to WHOWAS: a Large-Scale Measurement Study of Domain Registration Privacy Under the GDPR
    From WHOIS to WHOWAS: A Large-Scale Measurement Study of Domain Registration Privacy under the GDPR Chaoyi Lu∗†, Baojun Liu∗†¶B, Yiming Zhang∗†, Zhou Li§, Fenglu Zhang∗, Haixin Duan∗¶B, Ying Liu∗, Joann Qiongna Chen§, Jinjin LiangY, Zaifeng ZhangY, Shuang Hao∗∗ and Min Yang†† ∗Tsinghua University, †Beijing National Research Center for Information Science and Technology, flcy17, zhangyim17, zfl[email protected], flbj, [email protected], [email protected] §University of California, Irvine, fzhou.li, [email protected], ¶Qi An Xin Group, Y360 Netlab, fliangjinjin, [email protected], ∗∗University of Texas at Dallas, [email protected], ††Fudan University, m [email protected] Abstract—When a domain is registered, information about the [39], online advertising [55], [96], [103], [102] and usability registrants and other related personnel is recorded by WHOIS of privacy notices [104], [78], [79], [90], [50], [49], [27], [72]. databases owned by registrars or registries (called WHOIS providers jointly), which are open to public inquiries. However, Due to its broad scope, not only does the GDPR protect due to the enforcement of the European Union’s General Data normal users browsing websites, users setting up websites and Protection Regulation (GDPR), certain WHOIS data (i.e., the the associated infrastructure are also protected. One example records about EEA, or the European Economic Area, registrants) is domain registration. After a user registers a domain name, needs to be redacted before being released to the public. Anec- e.g., example.com, its sponsoring registrar and upper-stream dotally, it was reported that actions have been taken by some registry will store his/her personal information like name and WHOIS providers.
    [Show full text]
  • Domain Name System 1 Domain Name System
    Domain Name System 1 Domain Name System The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service translates queries for domain names (which are easier to understand and utilize when accessing the internet) into IP addresses for the purpose of locating computer services and devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the domain name www.example.com translates to the addresses 192.0.43.10 (IPv4) and 2620:0:2d0:200::10 (IPv6). The Domain Name System makes it possible to assign domain names to groups of Internet resources and users in a meaningful way, independent of each entity's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). Users take advantage of this when they recite meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates them. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain.
    [Show full text]
  • Community Experiences with the Internic Whois Data Problem Reports System
    Community Experiences with the InterNIC Whois Data Problem Reports System 31 March 2006 Contents Executive Summary...........................................................................................................1 Introduction........................................................................................................................2 I. Applicable Provisions of the ICANN Registrar Accreditation Agreement ..............3 II. Implementation of the WDPRS...................................................................................4 III. Statistics from Operation of the WDPRS................................................................. 5 IV. Impact of the WDPRS on Improved Whois Data Accuracy................................. 11 Executive Summary This Report summarizes ICANN's experience with the operation of the Whois Data Problem Report System (WDPRS) during a 12-month reporting period that ended 28 February 2006. ICANN developed this system to receive and track complaints about inaccurate or incomplete Whois data entries. Individuals who encounter such entries may notify ICANN by completing an online form, which is then forwarded to the registrar of record for appropriate action. The WDPRS is one of the tools that ICANN uses to improve the accuracy of Whois data. Through the WDPRS, ICANN is able to track how many reports are filed and confirmed by the reporter so they may be sent to the registrar of record. After forty-five days, ICANN asks the person filing the report to complete the process by performing a follow- up review, which involves checking the Whois data again and indicating whether (i) the data was fixed; (ii) the domain name was deleted; (iii) the data was unchanged; or (iv) there is some other disposition. On average, there were 4,305 reports completed each month during the reporting period, totaling 51,664 total reports for which ICANN received follow-up responses. Of these, 25,219 represented unique domain names. Thus, 26,445 duplicate reports were submitted.
    [Show full text]
  • An Introduction to Socket Programming
    An Introduction to Socket Programming (by) Reg Quinton <[email protected]> © $Id: socket.html,v 1.8 1997/05/02 20:17:16 reggers Exp $ Contents: Introduction BEWARE Existing Services Netstat Observations Host names and IP numbers Programming Calls Services and Ports Programming Calls Socket Addressing File Descriptors and Sockets File Descriptors Sockets Client Connect Client Communication Stdio Buffers Server Applications Server Bind Listen and Accept Inetd Services Inetd Comments Whois Daemon Running the Daemon The Code Connecting to the Server Whois Client Perl Socket Programming Final Comments Note Well Suggested Reading Author Introduction: These course notes are directed at Unix application programmers who want to develop client/server applications in the TCP/IP domain (with some hints for those who want to write UDP/IP applications). Since the Berkeley socket interface has become something of a standard these notes will apply to programmers on other platforms. Fundamental concepts are covered including network addressing, well known services, sockets and ports. Sample applications are examined with a view to developing similar applications that serve other contexts. Our goals are to develop a function, tcpopen(server,service), to connect to service. to develop a server that we can connect to. This course requires an understanding of the C programming language and an appreciation of the programming environment (ie. compilers, loaders, libraries, Makefiles and the RCS revision control system). If you want to know about socket programming with perl(1) then see below but you should read everything first. Our example is the UWO/ITS whois(1) service -- client and server sources available in: Network Services: http://www.uwo.ca/its/ftp/pub/unix/network Look for the whois(1) client and the whoisd(8) server.
    [Show full text]
  • Applications: Telnet, Rlogin, Ftp, Sun RPC, Nfs, Finger, Whois, X
    1 Applications: Telnet, rlogin, ftp, Sun RPC, nfs, ®nger, whois, X Remote login ➠ remote login to host from host to host telnet, rlogin rlogin: mostly Unix systems rlogin: simpler (no option negotiation) both use client/server (rlogind, telnetd) one TCP connection low volume, short packets, asymmetric 2 Remote login: components Telnet/rlogin Telnet/rlogin login client server shell kernel kernel terminal TCP TCP pseudo-terminal driver IP IP driver subnet subnet TCP connection (port 513) Multiple connections How two clients connect to the login server: D1 S.login D1.1022 S S.login D2.1023 D2 3 rlogin protocol client server \0 user \0 login_as \0 terminal/speed \0 0 Password: secret 0x80 0xffff s s rows cols x y ➠ password sent as cleartext (snooping!) Kerberos ➠ .rhosts ®le (host list) bypasses login check security risk! echoing done by server everything typed sent to server, everything received displayed rlogin server-client interaction ➠ ¯ow control must be done by client (pipe!) XON/XOFF ASCII (control-s/q) client interrrupt (control-c): stop display locally ! server client commands via TCP urgent mode ± ¯ush output (server sends after interrupt) ± client stops performing ¯ow control ± client resumes performing ¯ow control ± please send window size ! client server commands: window size changes in-band via escape sequence 0xffff 4 telnet: remote login one of the oldest Internet applications (1969) network virtual terminal: dumb terminal, 7-bit ASCII common to FTP, SMTP, ®nger, whois: CRLF for end-of-line in-band signaling
    [Show full text]
  • Chapter 5 Phase 1: Reconnaissance Reconnaissance
    Chapter 5 Phase 1: Reconnaissance Reconnaissance ♦ Finding as much information about the target as possible before launching the first attack packet ♦ Reconnaissance techniques – Low tech methods – General web searches – Whois databases – DNS Low-Technology Reconnaissance ♦ Social Engineering ♦ Physical Break-In ♦ Dumpster Diving Social Engineering ♦ Finding pretext to obtain privileged information or services ♦ Defense – user awareness Physical Break-In ♦ Methods – Walking past unlocked doors to data center – Piggyback behind legitimate employee ♦ Defense – security badges – track computers leaving premises – physically lock down servers – Use locks on cabinets containing sensitive information – Use automatic password-protected screen savers – Encrypt stored files Dumpster Diving ♦ Retrieving sensitive information from trash ♦ Defense – Paper shredder Reconnaissance via Searching the Web ♦ Searching an organization’s own web site ♦ Using search engines ♦ Listen in at the virtual watering hole: USENET Searching an Organization’s Own Web Site ♦ Employees’ contact information and phone numbers ♦ Clues about the corporate culture and language ♦ Business partners ♦ Recent mergers and acquisitions ♦ Server and application platforms in use Using Search Engines ♦ Conduct search based on organization name, product names, employee names ♦ Retrieve information about history, current events, and future plans of the target organization ♦ Search for links to target organization via “link:www.companyname.com” in a search engine Listening in at the
    [Show full text]
  • WHOIS Review Team
    WHOIS Review Team Final Report (Draft) Executive Summary 5 December 2011 Table of Contents Chapter 1: Executive Summary ................................................................................................... 3 PART I – Scope of Work and Definitions .................................................................................14 Chapter 2: The WHOIS Review Team, Scope of Work & Key Definitions ....................14 PART II – ICANN WHOIS Policy and its Implementation ...................................................21 Chapter 3: The Complex History of WHOIS Policy ..............................................................21 Chapter 4: Implementation of WHOIS policy – ICANN’s Compliance Efforts ............36 Chapter 5: Implementation of WHOIS Policy in Relation to Internationalized Domain Names ................................................................................................................................41 PART III – The Extent to which ICANN’s Existing Policy and its Implementation Are Effective in Meeting Stakeholder Needs ........................................................................45 Chapter 6: Understanding the Needs of Stakeholders ......................................................45 Chapter 7: Gap Analysis ...............................................................................................................80 Chapter 8: Recommendations ...................................................................................................88 Chapter 1: Executive Summary The
    [Show full text]