- Using the Cisco IOS Command-Line Interface
- EXEC Commands in Configuration Mode
- show Command Output Redirection
- Overview Basic Configuration of a Cisco Networking Device
- Using Setup Mode to Configure a Cisco Networking Device
- Using AutoInstall to Remotely Configure Cisco Networking Devices
- Configuring Operating Characteristics for Terminals
- Managing Connections Menus and System Banners
- Using the Cisco IOS Web Browser User Interface
- Unique Device Identifier Retrieval
- ACL Authentication of Incoming rsh and rcp Requests
Contents
- ACL Authentication of Incoming rsh and rcp Requests
- Feature Overview
- Related Documents
- Supported Platforms
ACL Authentication of Incoming rsh and rcp Requests
Feature History
|
Release |
Modification |
|---|---|
|
12.2(8)T |
This feature was introduced. |
This document describes the ACL Authentication of Incoming RSH and RCP Requests feature in Cisco IOS Release 12.2(8)T. It includes the following sections:
Feature Overview
To enable the Cisco IOS software to receive incoming remote shell (rsh) protocol and remote copy (rcp) protocol requests, customers must configure an authentication database to control access to the router. This configuration is accomplished by using the iprcmdremote-hostcommand.
Currently, when using this command, customers must specify the local user, the remote host, and the remote user in the database authentication configuration. For users who can execute commands to the router from multiple hosts, multiple database authentication configuration entries must be used, one for each host, as shown below.
ip rcmd remote-host local-user1 remote-host1 remote-user1 ip rcmd remote-host local-user1 remote-host2 remote-user1 ip rcmd remote-host local-user1 remote-host3 remote-user1 ip rcmd remote-host local-user1 remote-host4 remote-user1
This feature allows customers to specify an access list for a given user. The access list identifies the hosts to which the user has access. A new argument, access-list , has been added that can be used with this command to specify the access list, as shown below.
ip rcmd remote-host local-user1 access-list remote-user1
To allow a user access to the hosts identified in the access list, first define the access list. If the access list is not already defined, access to the host will be denied. For information about defining an access list, refer to the Cisco IOS Security Configuration Guide , Release 12.2.
For more information about using the modified iprcmdremote-host command, see the “Command Reference” section later in this document.
Related Documents
Cisco IOS Configuration Fundamentals Command Reference, Release 12.2
Cisco IOS Security Configuration Guide , Release 12.2
Cisco IOS Security Command Reference, Release 12.2
Supported Platforms
Cisco 805
Cisco 806
Cisco 828
Cisco 1400 series
Cisco 1600 series
Cisco 1710
Cisco 1720
Cisco 1721
Cisco 1750
Cisco 1751
Cisco 2420
Cisco 3620
Cisco 3631
Cisco 3640
Cisco 3660
Cisco 3725
Cisco 3745
Cisco 2500 series
Cisco 2600 series
Cisco 7100 series
Cisco 7200 series
Cisco 7500 series
Cisco uBR7200 series
Cisco Voice Gateway 200
URM (Universal Route Module)
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL: