| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_protocol_settings.robot | 30 Enable SSH Protocol And Verify
39 # Check if SSH login and commands on SSH session work.
48 # Disable SSH interface.
59 ... msg=SSH Login and commands are working after disabling SSH.
74 # Check if SSH login and commands on SSH session work.
83 # Disable SSH interface.
97 ... msg=SSH Login and commands are working after disabling SSH.
113 Verify Existing SSH Session Gets Closed On Disabling SSH
118 # Open SSH connection.
133 ... msg=Disabling SSH has not closed existing SSH sessions.
[all …]
|
| H A D | test_multiple_interfaces.robot | 180 Set SSH Value Via Eth1 ${True}
182 Verify SSH Protocol State Via Eth1 ${True}
183 # Check if SSH login and commands on SSH session work on both interfaces.
184 Verify SSH Login And Commands Work
192 Set SSH Value Via Eth1 ${False}
200 ... msg=SSH Login and commands are working after disabling SSH via eth1.
202 # Check if SSH login and commands fail.
204 ... Verify SSH Login And Commands Work
207 ... msg=SSH Login and commands are working after disabling SSH.
325 Set SSH Value Via Eth1
[all …]
|
| /openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
| H A D | test_policies_sub_menu.robot | 68 Enable SSH Via GUI And Verify
70 ... verify that SSH to BMC starts working after enabling SSH.
77 Disable SSH Via GUI And Verify
79 ... verify that SSH to BMC stops working after disabling SSH.
90 ... msg=SSH login still working after disabling SSH.
144 ... verify that SSH to BMC stops working after disabling SSH on BMC reboot.
157 ... msg=SSH login still working after disabling SSH.
256 # Verify SSH state value.
276 Set SSH And IPMI State Via GUI
287 # When SSH state is already set to given value, click SSH toggle
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | protocol_setting_utils.robot | 16 Enable SSH Protocol
17 [Documentation] Enable or disable SSH protocol.
21 # enable_value Enable or disable SSH, e.g. (true, false).
24 ${data}= Create Dictionary SSH=${ssh_state}
33 Verify SSH Login And Commands Work
34 [Documentation] Verify if SSH connection works and able to run command on SSH session.
41 # Check if we can open SSH connection and login.
47 Verify SSH Protocol State
48 [Documentation] verify SSH protocol state.
52 # state Enable or disable SSH, e.g. (true, false)
[all …]
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | test_bmc_stress_buster.robot | 2 Documentation Generic REST/SSH/IPMI stress buster program.
16 # Currently REST/SSH/IPMI session allowed.
34 Stress BMC SSH Server
35 [Documentation] Execute maximum allowed SSH operation.
37 Log To Console SSH call request burst ${SSH_BUSTER_MAX}
39 ... ${SSH_BUSTER_MAX} SSH Connect And Execute Command
41 ... msg=One or more SSH operations has failed.
72 SSH Connect And Execute Command
73 [Documentation] Execute SSH command execution operation.
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | manager.hpp | 20 SSH, enumerator
28 SSH, enumerator
59 {SerialConnectTypesSupported::SSH, "SSH"},
67 {CommandConnectTypesSupported::SSH, "SSH"},
|
| H A D | connection_method.hpp | 20 SSH, enumerator
36 {TunnelingProtocolType::SSH, "SSH"},
|
| H A D | key.hpp | 35 SSH, enumerator
79 {KeyType::SSH, "SSH"},
|
| H A D | certificate.hpp | 38 SSH, enumerator
79 {CertificateUsageType::SSH, "SSH"},
|
| /openbmc/openbmc-test-automation/templates/ |
| H A D | test_openbmc_setup.robot | 26 Test SSH Setup
27 [Documentation] Verify SSH works.
32 Fail BMC SSH login failed.
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/openssh/openssh/ |
| H A D | add-test-support-for-busybox.patch | 13 @@ -17,7 +17,7 @@ for c in `${SSH} -Q cipher`; do n=0; for
15 ( ${SSH} -o 'compression no' \
32 ${SSH} -q -F $OBJ/ssh_proxy somehost "cat > ${COPY}"
46 r=`${SSH} -q -F $OBJ/ssh_proxy somehost 'echo true'`
|
| /openbmc/linux/tools/testing/ktest/examples/include/ |
| H A D | bootconfig.conf | 16 ADD_BOOTCONFIG := ${SSH} "${BOOTCONFIG} -d ${INITRD} && ${BOOTCONFIG} -a /tmp/${BOOTCONFIG_FILE} ${…
24 CLEAR_BOOTCONFIG := ${SSH} "${BOOTCONFIG} -d ${INITRD}"
28 DO_TEST = scp ${BOOTCONFIG_PATH}${BOOTCONFIG_VERIFY} ${SSH_USER}@${MACHINE}:/tmp && ${SSH} /tmp/${B…
|
| H A D | defaults.conf | 50 SSH := ssh ${SSH_USER}@${MACHINE}
54 TEST = ${SSH} run-test
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | oeqa-fvp.md | 20 OEFVPTarget supports two different test interfaces - SSH and pexpect.
22 ## SSH section in OEQA on Arm FVPs
24 …-core, tests cases can run commands on the machine using SSH. It therefore requires that an SSH se…
32 …est cases depend on `ssh.SSHTest.test_ssh`, which first validates that the SSH connection is funct…
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/ |
| H A D | overview.rst | 53 refer to the serial device and its driver as Surface Serial Hub (SSH). When
55 SAM-over-SSH and SAM-over-HID.
57 Currently, this subsystem only supports SAM-over-SSH. The SSH communication
60 which) concepts of the SSH interface detailed below can be transferred to
66 As already elaborated above, the Surface Serial Hub (SSH) is the
|
| H A D | ssh.rst | 25 The Surface Serial Hub (SSH) is the central communication interface for the
28 SAM-over-SSH, as opposed to SAM-over-HID for the older generations.
30 On Surface devices with SAM-over-SSH, SAM is connected to the host via UART
47 SSH Packet Protocol: Definitions
50 The fundamental communication unit of the SSH protocol is a frame
54 .. flat-table:: SSH Frame
85 .. flat-table:: SSH Byte Sequences
107 .. flat-table:: SSH Frame Types
137 SSH Packet Protocol: Flow Sequence
207 .. flat-table:: SSH Command
|
| /openbmc/openbmc-test-automation/lib/pdu/ |
| H A D | schneider.robot | 9 Login To Schneider PDU Via SSH
10 [Documentation] Open PDU connection and login via SSH.
56 # SSH/SCP : Enabled SNMPv1 : Disabled
96 ${connection_status}= Login To Schneider PDU Via SSH
|
| /openbmc/openbmc-test-automation/ffdc/ |
| H A D | ffdc_config.yaml | 52 - "SSH"
117 - "SSH"
210 - "SSH"
231 - "SSH"
250 - "SSH"
276 - "SSH"
295 - "SSH"
320 - "SSH"
336 - "SSH"
363 - "SSH"
[all …]
|
| /openbmc/openbmc-test-automation/security/ |
| H A D | test_bmc_network_security.robot | 91 Send Network Packets Continuously To SSH Port
92 [Documentation] Send network packets continuously to SSH port and verify stability.
95 # Send large number of packets to SSH port.
101 # Check if SSH interface is functional.
183 Send Continuous TCP Connection Requests To SSH Interface And Check Stability
184 [Documentation] Establish large number of TCP connections to SSH interface
188 # Establish large number of TCP connections to SSH interface.
192 # Check if SSH interface is functional.
|
| /openbmc/openbmc-test-automation/systest/ |
| H A D | network_stability_test.robot | 33 # - Establish SSH connection session
42 # Post Power off and on, the OS SSH session needs to be established.
96 # 3. Close all open SSH connections.
|
| /openbmc/docs/security/ |
| H A D | network-security-considerations.md | 73 - SSH secure shell
87 - SSH for ssh and scp.
112 IPMI, SSH, and other BMC services, possibly by using shell commands like 'systemctl
134 ### TCP port 22 - Secure Shell (SSH) access to the BMC
136 The Secure Shell (SSH) protocol is provided, including secure shell (ssh
140 The default SSH server implementation is provided by Dropbear. All configuration
144 password, and SSH certificates (the `ssh-keygen` command).
147 SSH access to the BMC's shell is not the intended way to operate the BMC, gives
223 Access to the BMC's [host serial console][] is provided via the SSH protocol on
|
| /openbmc/openbmc/poky/meta/recipes-core/packagegroups/ |
| H A D | packagegroup-core-ssh-openssh.bb | 1 SUMMARY = "OpenSSH SSH client/server"
|
| H A D | packagegroup-core-ssh-dropbear.bb | 1 SUMMARY = "Dropbear SSH client/server"
|
| /openbmc/obmc-console/conf/ |
| H A D | obmc-console-ssh.socket.in | 2 Description=Phosphor Host Console SSH Per-Connection socket
|
| /openbmc/linux/drivers/platform/surface/aggregator/ |
| H A D | Kconfig | 25 built. This includes a driver for the Surface Serial Hub (SSH), which
37 devices using SAM-over-SSH are supported, whereas devices using
41 Choose m if you want to build the SAM subsystem core and SSH driver as
|