DOCSLIB.ORG

Technical Guideline TR-02102-4 – Use of Secure Shell (SSH)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Technical Guideline TR-02102-4 – Use of Secure Shell (SSH) Technical Guideline TR-02102-4 Cryptographic Mechanisms: Recommendations and Key Lengths Part 4 – Use of Secure Shell (SSH) Version 2021-01 Document history Version Date Description 2019-01 2019-02-22 Adjustment of the periods of use, recommendations of Diffie-Hellman groups of RFC 8268 2020-01 2020-01-31 Adjustment of the periods of use, discontinuation of HMAC-SHA-1 2021-01 2021-03-12 Adjustment of the periods of use Federal Office for Information Security Post Box 20 03 63 D-53133 Bonn E-Mail: [email protected] Internet: https://www.bsi.bund.de © Federal Office for Information Security 2021 Table of Contents Table of Contents Document history.............................................................................................................................................................................. 2 1 Introduction......................................................................................................................................................................................... 5 2 Basic information............................................................................................................................................................................... 6 3 Recommendations............................................................................................................................................................................. 8 3.1 General notes................................................................................................................................................................................. 8 3.1.1 Periods of use.......................................................................................................................................................................... 8 3.1.2 Security level............................................................................................................................................................................ 8 3.2 SSH versions................................................................................................................................................................................... 8 3.2.1 Conformity to the SSH specification.............................................................................................................................8 3.3 Key agreement.............................................................................................................................................................................. 9 3.3.1 Key re-exchange.................................................................................................................................................................. 10 3.4 Encryption algorithms.............................................................................................................................................................. 10 3.5 MAC protection............................................................................................................................................................................ 10 3.6 Server authentication............................................................................................................................................................... 11 3.7 Client authentication................................................................................................................................................................. 11 4 Keys and random numbers......................................................................................................................................................... 13 4.1 Key storage................................................................................................................................................................................... 13 4.2 Handling of ephemeral keys................................................................................................................................................. 13 4.3 Random numbers....................................................................................................................................................................... 13 References........................................................................................................................................................................................... 14 Tables Table 1: Recommended key exchange methods............................................................................................................................... 9 Table 2: Recommended encryption algorithms.............................................................................................................................10 Table 3: Recommended functions for MAC protection..............................................................................................................10 Table 4: Recommended methods for sever authentication......................................................................................................11 Federal Office for Information Security 3 Introduction 1 1 Introduction This Technical Guideline provides recommendations for the use of the cryptographic protocol Secure Shell (SSH). This protocol can be used to establish a secure channel within an insecure network. The most common applications of the SSH protocol are logging on to a remote system (remote command-line login) and executing commands or running applications on remote systems. This Technical Guideline contains recommendations for the protocol version to be used and the cryptographic algorithms as a concretisation of the general recommendations in Part 1 of this Technical Guideline (see [TR-02102-1]). This Technical Guideline does not contain recommendations for specific applications, risk assessments or points of attack, which result from errors in the implementation of the protocol. Note: Even if all recommendations for the use of SSH are taken into account, data can leak from a cryptographic system to a considerable extent, e.g. by using side channels (measurement of timing behaviour, power consumption, data rates etc.). Therefore, the developer should identify possible side channels by involving experts in this field and implement corresponding countermeasures. Depending on the application, this also applies to fault attacks. Note: For the definitions of the cryptographic terms used in this document, please refer to the glossary in [TR-02102-1]. Federal Office for Information Security 5 2 Basic information 2 Basic information The SSH protocol consists of the three subprotocols Transport Layer Protocol, User Authentication Protocol and Connection Protocol. The Transport Layer Protocol (see [RFC4253]) allows server authentication, encryption, protection of the integrity and, optionally, data compression. It is based logically on the TCP/IP protocol. The User Authentication Protocol (see [RFC4252]) is used to authenticate the user to the server. It is based on the Transport Layer Protocol. The Connection Protocol (see [RFC4254]) is responsible for creating and managing logical channels within the encrypted tunnel. It is based on the User Authentication Protocol. For more detailed information about the protocol architecture of SSH, see [RFC4251]. The comprehensive specification of the SSH-2 (see Section 3.2) protocol can be found in the following RFCs: • RFC 4250: The Secure Shell (SSH) Protocol Assigned Numbers (January 2006) • RFC 4251: The Secure Shell (SSH) Protocol Architecture (January 2006) • RFC 4252: The Secure Shell (SSH) Authentication Protocol (January 2006) • RFC 4253: The Secure Shell (SSH) Transport Layer Protocol (January 2006) • RFC 4254: The Secure Shell (SSH) Connection Protocol (January 2006) • RFC 4256: Generic Message Exchange Authentication for the Secure Shell Protocol (SSH) (January 2006) • RFC 4335: The Secure Shell (SSH) Session Channel Break Extension (January 2006) • RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes (January 2006) The following RFCs contain extensions and additions to the SSH protocol: • RFC 4255: Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints (January 2006) • RFC 4419: Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol (March 2006) • RFC 4432: RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol (March 2006) • RFC 4462: Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol (May 2006) • RFC 4716: The Secure Shell (SSH) Public Key File Format (November 2006) • RFC 4819: Secure Shell Public Key Subsystem (March 2007) • RFC 5647: AES Galois Counter Mode for the Secure Shell Transport Layer Protocol (August 2009) • RFC 5656: Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer (December 2009) • RFC 6187: X.509v3 Certificates for Secure Shell Authentication (March 2011) • RFC 6239: Suite B Cryptographic Suites for Secure Shell (SSH) (May 2011) • RFC 6594: Use of the SHA-256 Algorithm with RSA: Digital Signature Algorithm (DSA): and Elliptic Curve DSA (ECDSA) in SSHFP Resource Records (April 2012) • RFC 6668: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol (July 2012) • RFC 8268: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH) (December 2017) 6 Federal Office for Information Security Basic information 2 • RFC 8270:
Load more

Recommended publications
  • BALG: Bypassing Application Layer Gateways Using Multi-Staged Encrypted Shellcodes
    Sebastian Roschke, Feng Cheng, Christoph Meinel: "BALG: Bypassing Application Layer Gateways Using Multi-Staged Encrypted Shellcodes" in Proceedings of the 12th IFIP/IEEE International Symposium on Integrated Network Management (IM 2011), IEEE Press, Dublin, Ireland, pp. 399-406, 5, 2011. ISBN: 978-1-4244-9219-0. BALG: Bypassing Application Layer Gateways Using Multi-Staged Encrypted Shellcodes Sebastian Roschke Feng Cheng Christoph Meinel Hasso Plattner Institute (HPI) Hasso Plattner Institute (HPI) Hasso Plattner Institute (HPI) University of Potsdam University of Potsdam University of Potsdam 14482, Potsdam, Germany 14482, Potsdam, Germany 14482, Potsdam, Germany Email: [email protected] Email: [email protected] Email: [email protected] Abstract—Modern attacks are using sophisticated and inno- easily penetrated by simple tunneling. IDS needs to handle vative techniques. The utilization of cryptography, self-modified efficient evasion techniques. ALGs provide more restrictions code, and integrated attack frameworks provide more possibili- for network access by combining filtering on the application ties to circumvent most existing perimeter security approaches, such as firewalls and IDS. Even Application Layer Gateways layer and IDS techniques, such as deep packet inspection. (ALG) which enforce the most restrictive network access can be Most of ALG implementations provide filtering due to ap- exploited by using advanced attack techniques. In this paper, plication layer protocol compliance and even allow to block we propose a new attack for circumventing ALGs. By using certain commands within a specific protocol. Although ALGs polymorphic and encrypted shellcode, multiple shellcode stages, enforce a very restrictive access policy, it is still possible to protocol compliant and encrypted shell tunneling, and reverse channel discovery techniques, we are able to effectively bypass circumvent such devices by using modern attack techniques.
    [Show full text]
  • VPN 3000 Series Concentrator Reference Volume II: Administration and Monitoring Release 3.6 August 2002
    VPN 3000 Series Concentrator Reference Volume II: Administration and Monitoring Release 3.6 August 2002 Corporate 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 526-4100 Customer Order Number: DOC-7814742= Text Part Number: 78-14742-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]
  • Configuring SSH and Telnet
    Configuring SSH and Telnet This chapter describes how to configure Secure Shell Protocol (SSH) and Telnet on Cisco NX-OS devices. This chapter includes the following sections: • About SSH and Telnet, on page 1 • Licensing Requirements for SSH and Telnet, on page 3 • Prerequisites for SSH and Telnet, on page 3 • Guidelines and Limitations for SSH and Telnet, on page 3 • Default Settings for SSH and Telnet, on page 4 • Configuring SSH , on page 4 • Configuring Telnet, on page 15 • Verifying the SSH and Telnet Configuration, on page 17 • Configuration Example for SSH, on page 18 • Configuration Example for SSH Passwordless File Copy, on page 19 • Additional References for SSH and Telnet, on page 21 About SSH and Telnet This section includes information about SSH and Telnet. SSH Server You can use the SSH server to enable an SSH client to make a secure, encrypted connection to a Cisco NX-OS device. SSH uses strong encryption for authentication. The SSH server in the Cisco NX-OS software can interoperate with publicly and commercially available SSH clients. The user authentication mechanisms supported for SSH are RADIUS, TACACS+, LDAP, and the use of locally stored usernames and passwords. SSH Client The SSH client feature is an application that runs over the SSH protocol to provide device authentication and encryption. The SSH client enables a Cisco NX-OS device to make a secure, encrypted connection to another Cisco NX-OS device or to any other device that runs the SSH server. This connection provides an outbound Configuring SSH and Telnet 1 Configuring SSH and Telnet SSH Server Keys connection that is encrypted.
    [Show full text]
  • Secured Connectivity Why It Matters and How to Protect Your Organization
    Secured Connectivity Why it Matters and How to Protect Your Organization While every attempt has been made to ensure the accuracy and completeness of the information in this document, some typographical or technical errors may exist. Hummingbird Connectivity – a division of Open Text cannot accept responsibility for customers’ losses resulting from the use of this document. The information contained in this document is subject to change without notice. This document contains proprietary information that is protected by copyright. This document, in whole or in part, may not be photocopied, reproduced, or translated into another language without prior written consent from Hummingbird Connectivity. This edition published September 2008 www.hummingbird.com 2 Contents The Security Challenge 4 Security in Organizations 5 Driving Security 6 Structural Factors 6 External Factors 6 Connectivity — A Definition 7 Security Risks in a Connectivity World 8 Weak Authentication 8 Easy Protocol Decoding 8 Data Authenticity and Integrity Tampering 8 Solutions for Secured Connectivity 9 SSL 9 Kerberos 10 Secure Shell 11 ® Connectivity SecureTerm 12 ™ Connectivity Secure Shell 14 Connectivity Secure Server 16 Secure Replacement for Telnet and FTP 16 High Performance and Scalability 16 Glossary of Terms 18 www.hummingbird.com 3 The Security Challenge Security is the hot topic today. Although, companies have been slow to recognize the importance of security things have changed during the last decade. Security is a top priority and there are no indications that this will end any time soon. The costs of security (or lack thereof) have now been clearly identified, and the picture does not look very good.
    [Show full text]
  • NBAR2 Standard Protocol Pack 1.0
    NBAR2 Standard Protocol Pack 1.0 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 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
    [Show full text]
  • Fdc3302e Frequency Distribution Chassis
    "Smarter Timing Solutions" FDC3302e Frequency Distribution Chassis User Manual USM3302-0800-000 Revision 2 March 2019 FDC3302e Frequency Distribution Chassis User Manual Preface Thank you for purchasing the Frequency Distribution Chassis. Our goal in developing this product is to bring you a distribution chassis that will quickly, easily and reliably meet or exceed your system requirements. Your new FDC3302e is fabricated using the highest quality materials and manufactur- ing processes available today, and will give you years of trouble-free service. About EndRun Technologies EndRun Technologies is dedicated to the development and refinement of the technologies required to fulfill the demanding needs of the time and frequency community. The instruments produced by EndRun Technologies have been selected as the timing reference for a variety of industries and applications - computer networks, satellite earth stations, power utilities, test ranges, broadcast and telecommunications systems and more. EndRun Technologies is committed to fulfilling your precision timing needs by providing the most advanced, reliable and cost-effective time and frequency equipment available in the market today. Trademark Acknowledgements IBM-PC, UNIX, Windows NT are registered trademarks of the respective holders. Part No. USM3302-0800-000 Revision 2 March 2019 Copyright © EndRun Technologies 2007-2019 FDC3302e User Manual About This Manual This manual will guide you through simple installation and set up procedures. Introduction – The Frequency Distribution Chassis, how it works, where to use it, its main features. Basic Installation – How to connect, configure and test your distribution chassis. Console Port – Description of the console commands for use over the serial port or optional network port.
    [Show full text]
  • An Adaptive Multi-Layer Botnet Detection Technique Using Machine Learning Classifiers
    applied sciences Article An Adaptive Multi-Layer Botnet Detection Technique Using Machine Learning Classifiers Riaz Ullah Khan 1,* , Xiaosong Zhang 1, Rajesh Kumar 1 , Abubakar Sharif 1, Noorbakhsh Amiri Golilarz 1 and Mamoun Alazab 2 1 Center of Cyber Security, School of Computer Science & Engineering, University of Electronic Science and Technology of China, Chengdu 611731, China; [email protected] (X.Z.); [email protected] (R.K.); [email protected] (A.S.); [email protected] (N.A.G.) 2 College of Engineering, IT and Environment, Charles Darwin University, Casuarina 0810, Australia; [email protected] * Correspondence: [email protected]; Tel.: +86-155-2076-3595 Received: 19 March 2019; Accepted: 24 April 2019; Published: 11 June 2019 Abstract: In recent years, the botnets have been the most common threats to network security since it exploits multiple malicious codes like a worm, Trojans, Rootkit, etc. The botnets have been used to carry phishing links, to perform attacks and provide malicious services on the internet. It is challenging to identify Peer-to-peer (P2P) botnets as compared to Internet Relay Chat (IRC), Hypertext Transfer Protocol (HTTP) and other types of botnets because P2P traffic has typical features of the centralization and distribution. To resolve the issues of P2P botnet identification, we propose an effective multi-layer traffic classification method by applying machine learning classifiers on features of network traffic. Our work presents a framework based on decision trees which effectively detects P2P botnets. A decision tree algorithm is applied for feature selection to extract the most relevant features and ignore the irrelevant features.
    [Show full text]
  • Getting Started with Your Dedicated Server
    Getting Started Guide Getting Started With Your Dedicated Server Setting up and hosting a domain on your Linux® Dedicated Server using Plesk 8.0®. Getting Started with Your Dedicated Server ‐ Plesk 8.0 Version 1.1 (06.23.08) © Copyright 2008. All rights reserved. Distribution of this work or derivative of this work is prohibited unless prior written permission is obtained from the copyright holder. Trademarks Used in This Book Linux® is a registered trademark of Linus Torvalds. Plesk® is a registered trademark of SW­soft Holdings, LTD. SSH® and Secure Shell® are trademarks of SSH Communications Security, Inc. RedHat® and Fedora® are registered trademarks of Red Hat Software, Inc. Mac® is a registered trademark of Apple Computer, Inc. UNIX® is a registered trademark of The Open Group. Windows XP®, Entourage®, and Outlook® are registered trademarks of Microsoft Corporation in the United States and/or other countries. Thunderbird™ is an unregistered trademark of the Mozilla Foundation. All other trademarks and copyrights are the property of their respective owners. Table of Contents Introduction iv Security Information iv Reprovisioning Your Server vi Getting Help vi Other Resources vii 1 Setting Up Your Dedicated Server 1 Choosing a Host Name, User ID, and Password 1 Choosing a Host Name 1 Choosing a User ID 2 Choosing a Password for Your Server 2 Logging in to Your Manager for the First Time 3 2 Connecting to Your Dedicated Server 5 Connecting to Your Server Using Plesk 5 Connecting to Your Server Using SSH 10 Gaining Root Access on Your
    [Show full text]
  • Remote File Access System for Generic Ericsson Processor Boards
    Remote File Access System for Generic Ericsson Processor Boards DANIEL JESÚS GARCÍA MORAL KTH Information and Communication Technology Degree project in Communication Systems Second level, 30.0 HEC Stockholm, Sweden Remote File Access System for Generic Ericsson Processor Boards File transfer service, Random Access Memory-based file system and secure file transfer solution research DANIEL JESÚS GARCÍA MORAL Master’s Degree Project Supervisor: Lukas Karlsson Examiner: Mark Smith Stockholm, Sweden October 2011 iii Abstract Generic Ericsson Processor boards are general purpose hardware platforms which provide generic processing services. They support the Unified Exten- sible Firmware Interface Specification. They have several network interfaces available and they are connected to Ericsson’s laboratory network. Several servers are also connected to this network. These boards require periodic firmware upgrades. They also require acquiring new firmware components and data files. Currently, an application to download or upload files from and to Ericsson’s laboratory servers when an Operating System has not already been booted does not exist. Therefore, the files have to be transferred to USB drives which are connected later to the boards in order to transfer the files. This is a time consuming operation which decreases Er- icsson’s productivity. In addition, although Generic Ericsson Processor boards have an optional solid-state drive as secondary storage, Ericsson wants to be able to operate without it. This is because this secondary storage is not al- ways available and Ericsson does not want to use it when the Generic Ericsson Processor boards are operating before an Operating System has been loaded. They prefer to use Random Access Memory storage.
    [Show full text]
  • Securing the Border Gateway Protocol by Stephen T
    September 2003 Volume 6, Number 3 A Quarterly Technical Publication for From The Editor Internet and Intranet Professionals In This Issue The task of adding security to Internet protocols and applications is a large and complex one. From a user’s point of view, the security- enhanced version of any given component should behave just like the From the Editor .......................1 old version, just be “better and more secure.” In some cases this is simple. Many of us now use a Secure Shell Protocol (SSH) client in place of Telnet, and shop online using the secure version of HTTP. But Securing BGP: S-BGP...............2 there is still work to be done to ensure that all of our protocols and associated applications provide security. In this issue we will look at Securing BGP: soBGP ............15 routing, specifically the Border Gateway Protocol (BGP) and efforts that are underway to provide security for this critical component of the Internet infrastructure. As is often the case with emerging Internet Virus Trends ..........................23 technologies, there exists more than one proposed solution for securing BGP. Two solutions, S-BGP and soBGP, are described by Steve Kent and Russ White, respectively. IPv6 Behind the Wall .............34 The Internet gets attacked by various forms of viruses and worms with Call for Papers .......................40 some regularity. Some of these attacks have been quite sophisticated and have caused a great deal of nuisance in recent months. The effects following the Sobig.F virus are still very much being felt as I write this. Fragments ..............................41 Tom Chen gives us an overview of the trends surrounding viruses and worms.
    [Show full text]
  • Secure Shell (SSH)
    Secure SHell (SSH) © André Zúquete Advanced Network Security SSH (Secure SHell, RFC 4251): Goals An application and a secure communication protocol over TCP/IP Allows the establishment of secure remote sessions Replacing insecure telnet/rlogin sessions Allows the multiplexing of many data flows over a secure session Secure tunneling Security mechanisms Confidentiality and integrity control Including data flow hiding Key distribution Session key Mutual authentication Server host (or server) Client user © André Zúquete Advanced Network Security SSH: Exploitation Secure remote logins Instead of telnet/rlogin Secure remote command execution Instead of rsh/rcmd/rexec Secure file transfer and backup Secure FTP / Secure copy Port forwarding and tunneling For adding security to multiple data flows through a single SSH session © André Zúquete Advanced Network Security SSH: History Created by Tatu Ylönen First version released in 1995 Second version released in 1998 Not compatible with the previous one Björn Grönvall developed OSSH in 1999 From the last open source release of SSH OpenBSD launched the OpenSSH project (www.openssh.org ) Extending OSSH © André Zúquete Advanced Network Security SSH: Architecture Client-server architecture Server usually on port 22 Services include login, ftp, file copy and TCP tunneling © André Zúquete Advanced Network Security SSH: Protocols Transport Layer Protocol (RFC 4253) Key distribution Session key computing with ephemeral DH values Server authentication With pre-distributed,
    [Show full text]
  • Enhancing the Communication Channel Through Secure Shell And
    S.R.M.Krishna et al. / International Journal on Computer Science and Engineering (IJCSE) Enhancing the Communication Channel Through Secure Shell And Irrational DES S.R.M.Krishna,Paradeep singh jamwal,K.padma priya,P.Hema Vishnu Abstract:--- As the internet grows in popularity and therefore also in size more and more transmission takes place mainly because the technology is more readily available and applications have become more user friendly allowing entry to less sophisticated user over a broad spectrum.most data transfer are mainly text based not secure and vulnerable to various forms of security risks. So the model that uses SSH for securing channel like intranet/internet which provides client authentication encryption and decryption with high degree of security by transferring the data in an encrypted format, up on this model enhances the efficiency of data transmission by encrypting or decrypting the data with irrational DES. DES is a cryptographic standard however,the applications of it limited because of small key space based on irrational number.Moreover the permutation controlled by data can be performed at high speed in generic cpu.this scheme also expands the key space without costing more to run.and also finally through the combination of secure shell(ssh) and irrational DES not only enhances the security of communication channel.it also provides varius applications like remote user creation,remote user deletion,remote command execution,remote system shutdown ,remote file transfer applications in an highly secure manner. Index Terms – remote ssh, irrational DES, remote Administration. INTRODUCTION This paper addresses the problem of providing a secure means of client to client or server to server or client to server over an insecure channel like internet.The paper aims to use the SSH and irrational DES which is the which is the enhanced DES algorithm for securing the transmission channel between any two remote computers.
    [Show full text]