<P> Many extensions were made for Telnet because of its negotiable options protocol architecture . Some of these extensions have been adopted as Internet standards, IETF documents STD 27 through STD 32 . Some extensions have been widely implemented and others are proposed standards on the IETF standards track (see below) Telnet is best understood in the context of a user with a simple terminal using the local Telnet program (known as the client program) to run a logon session on a remote computer where the user's communications needs are handled by a Telnet server program . </P> <Table> <Tr> <Td> </Td> <Td> This section does not cite any sources . Please help improve this section by adding citations to reliable sources . Unsourced material may be challenged and removed . (April 2010) (Learn how and when to remove this template message) </Td> </Tr> </Table> <Tr> <Td> </Td> <Td> This section does not cite any sources . Please help improve this section by adding citations to reliable sources . Unsourced material may be challenged and removed . (April 2010) (Learn how and when to remove this template message) </Td> </Tr> <P> When Telnet was initially developed in 1969, most users of networked computers were in the computer departments of academic institutions, or at large private and government research facilities . In this environment, security was not nearly as much a concern as it became after the bandwidth explosion of the 1990s . The rise in the number of people with access to the Internet, and by extension the number of people attempting to hack other people's servers, made encrypted alternatives necessary . </P>

What protocol would you use for remote access to get a console with an encrypted connection