[root@stapp01 ~]# ssh [email protected]
The authenticity of host ‘172.16.238.10 (172.16.238.10)’ can’t be established.
ECDSA key fingerprint is SHA256:piuKeEVGLN6vHokyWOfV6diwsG4l5LJfXHf7ThSiEA0.
ECDSA key fingerprint is MD5:7d:ff:fb:0b:d7:34:0e:f3:49:7e:be:7d:fe:50:ab:c6.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘172.16.238.10’ (ECDSA) to the list of known hosts. [email protected]’s password:
This service allows sftp connections only.
Connection to 172.16.238.10 closed.
@Inderpreet@q69145
how to verify this task?
if I have completed all the action items correctly?
I have followed below google article and updated as per the question.
From your original answer it seems like when you clicked on Finish, your changes were not complete and tested. The testing screenshots you shared above seems to be taken after clicking on Finish and after making some additional changes. Please not that any changes made after clicking on Finish are not included in the original answer.
That is not true. All my changes were completed and tested before I clicked on Finish.
All screenshot were taken after the failed result and have all the steps and all the tests I did until the end.
As you can see in the screenshots I used 2 terminal, one for working and the other for the testing.
@wfranca Just checked your second screenshot and noticed that after login into SFTP user it seems like its landing into wrong location, there must be some particular location been given in question I think.
My 3rd screenshot has the content of the sshd_config with the configuration of the chroot directory pointing to /var/www/webdata and the output of the getent shows the user was configured with shell /bin/false.
The task is marked as failed because “user was able to login through ssh and not able do make sftp connection” both 1st and 2nd screenshot shows that it is not true and the user was able to login through sftp and not through ssh
@wfranca the error messages are generic in some cases, so when it checked SFTP maybe it was able to login but since it landed to wrong location so that is the reason it failed.