Ssh Access Control

Test suite for validating SSH access control options

SSH User Deny

Description

Check that enforcing a user denial will work as expected. Test_user is set to be denied through SSH connection, then a connection through this user is tried expecting failure to connect. Admin user that hasn’t been denied is also tested to confirm unchanged behavior in this case.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.215.168.20/24
set service ssh access-control deny user test_user
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system login user test_user authentication encrypted-password '$6$6RrUTbJY7lzkkhB.$hkrmWyduaZJxrsr0a7xms0OcPcxUUYL36YOjpjpMxWYecKVZ1dcZ5Pj6rTOhcuLO1Fjbx9sDoSutR.louRXpP/'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.215.168.21/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping the IP address 10.215.168.20 from DUT1:

admin@DUT1$ ping 10.215.168.20 count 1 size 56 timeout 1

Step 4: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user test_user which is expected to fail:

admin@DUT1$ ssh test_user@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

Step 5: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user admin:

admin@DUT1$ ssh admin@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

SSH User Allow

Description

Check that allowing a user will only let that user connect to the device. Test_user is set to be unallowed through SSH connection, then a connection through this user is tried expecting to connect unsuccessfully. The next step will try a SSH connection through Admin which is the allowed user, then the connection is succesfull.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.215.168.20/24
set service ssh access-control allow user admin
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system login user test_user authentication encrypted-password '$6$bdulGZniJdu81eMe$SZPygPfCL0xWPGwMOLiRlOJs4e0n84VmMtHVZxvizwad11s76a7CdwhuluJ2qsK7/OemlbgZ6QNAeRaWQghOW1'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.215.168.21/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping the IP address 10.215.168.20 from DUT1:

admin@DUT1$ ping 10.215.168.20 count 1 size 56 timeout 1

Step 4: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user test_user which is expected to fail:

admin@DUT1$ ssh test_user@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

Step 5: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user admin:

admin@DUT1$ ssh admin@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

SSH Role Deny

Description

Check that enforcing a role denial will work as expected. Test_user and test_role are created and then the role is assigned to the user. The role is set to be unallowed through SSH connection, then a connection through this user is tried expecting a failure. The admin user is also tried to ensure that users that haven’t been denied can still access the router.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.215.168.20/24
set service ssh access-control deny role test_role
set system login role test_role level 14
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system login user test_user authentication encrypted-password '$6$hpYldj5kxITR.vxt$XiLiXHvh/lRqGqKhJffsHEb8M8fV2fWrRBNKH.C7C1J3Ls7buD1BA7lT9LBcwwENUHx.tyyJux446frHYtqDR0'
set system login user test_user role test_role

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.215.168.21/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping the IP address 10.215.168.20 from DUT1:

admin@DUT1$ ping 10.215.168.20 count 1 size 56 timeout 1

Step 4: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user test_user which is expected to fail:

admin@DUT1$ ssh test_user@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

Step 5: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user admin:

admin@DUT1$ ssh admin@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

SSH Role Allow

Description

Check that enforcing a role permission will work as expected. Two users and two roles are created. The roles are assigned to each of the users. Test_role is then allowed and an SSH connection is tried with the test_user assigned that role, expecting to succeed. Test_user2 is tried to ensure the deny by default behavior once an allow is set.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.215.168.20/24
set service ssh access-control allow role test_role
set system login role test_role level 14
set system login role test_role2 level 13
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set system login user test_user authentication encrypted-password '$6$nuwpm23RcGhMkxXw$UPDQB5g2lMcwVZ94/MyUvn9yeYwPmfDSfPvq3em3lLxzEYUkXajIOlTdz5dzLYtbHfmMl9UMvVG1L.4niKuLu1'
set system login user test_user role test_role
set system login user test_user2 authentication encrypted-password '$6$2WicLjc08EICPSZz$eVEKpJ4/PUenYDhburUa1UKblU.OQA4UvCeuBzMFPF39MteF5O.C6GU.tt64QLPm8R5cbqDXtPbRMljVie2Oq.'
set system login user test_user2 role test_role2

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.215.168.21/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping the IP address 10.215.168.20 from DUT1:

admin@DUT1$ ping 10.215.168.20 count 1 size 56 timeout 1

Step 4: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user test_user:

admin@DUT1$ ssh test_user@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null

Step 5: Initiate an SSH connection from DUT1 to IP address 10.215.168.20 using user test_user2 which is expected to fail:

admin@DUT1$ ssh test_user2@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null