1
00:00:00,005 --> 00:00:02,002
- [Instructor] Secure Shell is a protocol

2
00:00:02,002 --> 00:00:06,003
to allow encrypted remote console access over a network.

3
00:00:06,003 --> 00:00:08,001
This is most closely associated

4
00:00:08,001 --> 00:00:10,000
with connecting to a Linux server,

5
00:00:10,000 --> 00:00:12,008
router or switch for configuration.

6
00:00:12,008 --> 00:00:17,007
It uses TCP port 22 for reliable delivery of packets.

7
00:00:17,007 --> 00:00:20,007
Though, it is most closely associated with Linux servers,

8
00:00:20,007 --> 00:00:24,000
Microsoft announced in 2015 that moving forward,

9
00:00:24,000 --> 00:00:27,006
Windows Server will have native support for SSH.

10
00:00:27,006 --> 00:00:30,002
It was originally designed to be a secure replacement

11
00:00:30,002 --> 00:00:32,007
for plain text methods like Telnet.

12
00:00:32,007 --> 00:00:36,003
SSH uses public key cryptography via certificates

13
00:00:36,003 --> 00:00:38,007
to verify remote computers,

14
00:00:38,007 --> 00:00:41,005
and public or private certificate can be generated

15
00:00:41,005 --> 00:00:44,009
and installed, or as is most often the case,

16
00:00:44,009 --> 00:00:47,004
the server will just generate its own certificate.

17
00:00:47,004 --> 00:00:50,006
Authentication of usernames is often done via accounts

18
00:00:50,006 --> 00:00:52,003
on the server being logged into

19
00:00:52,003 --> 00:00:55,000
or via a centralized authentication system

20
00:00:55,000 --> 00:00:56,005
for better control.

21
00:00:56,005 --> 00:01:00,008
Beyond remote access, SSH has some additional features.

22
00:01:00,008 --> 00:01:02,000
It supports tunneling,

23
00:01:02,000 --> 00:01:04,003
which allows you to securely send traffic

24
00:01:04,003 --> 00:01:06,004
over an SSH session.

25
00:01:06,004 --> 00:01:08,006
An admin can securely transfer files

26
00:01:08,006 --> 00:01:13,001
using SSH file transfer, more often known as SFTP.

27
00:01:13,001 --> 00:01:15,006
While SSH is native to most systems,

28
00:01:15,006 --> 00:01:17,008
additional programs are often necessary

29
00:01:17,008 --> 00:01:19,002
on a Windows machine.

30
00:01:19,002 --> 00:01:22,000
PuTTY is an open source SSH client

31
00:01:22,000 --> 00:01:24,007
that also supports SSH tunneling.

32
00:01:24,007 --> 00:01:29,004
WinSCP is also open source and provides SFTP access.

33
00:01:29,004 --> 00:01:33,004
Version one of SSH was released in 1995.

34
00:01:33,004 --> 00:01:35,004
It was released as freeware initially,

35
00:01:35,004 --> 00:01:36,007
and eventually evolved

36
00:01:36,007 --> 00:01:39,004
into a pay-to-play proprietary system.

37
00:01:39,004 --> 00:01:43,002
In 1999, developers took the most recent open source version

38
00:01:43,002 --> 00:01:46,003
of SSH and began to develop and improve it.

39
00:01:46,003 --> 00:01:48,009
This project became known as OpenSSH

40
00:01:48,009 --> 00:01:51,004
and is still the widest deployment footprint

41
00:01:51,004 --> 00:01:54,004
of any open source SSH implementation.

42
00:01:54,004 --> 00:01:57,005
Version two is unfortunately incompatible

43
00:01:57,005 --> 00:01:59,005
with SSH version one.

44
00:01:59,005 --> 00:02:03,002
It boasts both security and feature improvements.

45
00:02:03,002 --> 00:02:05,007
It's likely the bulk of your network configuration

46
00:02:05,007 --> 00:02:08,007
and server administration will be via this protocol,

47
00:02:08,007 --> 00:02:12,000
so it's best to familiarize yourself with it now.

