Re: PuTTY SSH client security

2014-07-14 Thread Virgo Pärna
On Sat, 12 Jul 2014 12:13:10 -0400 (EDT), Stephen Powell  
wrote:
>
> I think you meant to say "susceptible", not "suspectible".
> But otherwise, that's a good point.
>

Oops, sorry. 

-- 
Virgo Pärna 
virgo.pa...@mail.ee


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnls7012.fs2.virgo.pa...@dragon.gaiasoft.ee



Re: PuTTY SSH client security

2014-07-12 Thread Stephen Powell
On Fri, 11 Jul 2014 08:14:31 -0400 (EDT), Virgo Pärna wrote:
> 
> On Thu, 10 Jul 2014 10:24:50 +0100, Darac Marjal  
> wrote:
>>
>> PuTTY is *not* based on OpenSSL[1], so it has never been susceptible to
>> the heartbleed bug.
>>
> 
> And even if it were based on OpenSSL, it would not have  been suspectible to
> heartbleed bug, because ssh protocol was not suspectible to it.

I think you meant to say "susceptible", not "suspectible".
But otherwise, that's a good point.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/346088404.2734.1405181590096.javamail.r...@md01.wow.synacor.com



Re: PuTTY SSH client security

2014-07-11 Thread Virgo Pärna
On Thu, 10 Jul 2014 10:24:50 +0100, Darac Marjal  
wrote:
>
> PuTTY is *not* based on OpenSSL[1], so it has never been susceptible to
> the heartbleed bug.
>

And even if it were based on OpenSSL, it would not have  been suspectible to
heartbleed bug, because ssh protocol was not suspectible to it.

-- 
Virgo Pärna 
virgo.pa...@mail.ee


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnlrvl97.65f.virgo.pa...@dragon.gaiasoft.ee



Re: PuTTY SSH client security

2014-07-10 Thread Stephen Powell
On Thu, 10 Jul 2014 05:24:50 -0400 (EDT), Darac Marjal wrote:
> 
> On Thu, Jul 10, 2014 at 03:19:07AM -0600, Kitty Cat wrote:
>>I use PuTTY to connect to my Debian boxes.
>> 
>>I was concerned about whether PuTTY is susceptible to the Heartbleed bug,
>>etc. as I noticed that the program has not had any updates in quite some
>>time.
>> 
>>[1]http://www.chiark.greenend.org.uk/~sgtatham/putty/
>> 
>>Is this software still considered to be secure?
> 
> PuTTY is *not* based on OpenSSL[1], so it has never been susceptible to
> the heartbleed bug.
> 
> [1] https://the.earth.li/~sgtatham/putty/0.63/htmldoc/AppendixA.html#faq-misc

Darac is right, "Kitty Cat".  I also use PuTTY as an SSH client to connect
to Debian systems.  This is unrelated to your question, but I thought that
I would take this opportunity to pass on some tips for getting the most out
of PuTTY when used with a Debian host, based on my experience.

(1) The default locale on Debian systems is usually a UTF-8 locale.  For 
example,
en_US.UTF-8 for U.S. systems.  PuTTY should be set accordingly.

   Window -> Translation

Then, in the drop-down box under "Remote character set", select UTF-8.
Also, make sure that the "Use Unicode line drawing code points" radio
button is selected on the same screen.

(2) Assuming that you are running PuTTY under Windows, many Windows fonts
are incomplete.  Most of the fixed-width fonts are missing some of the
characters that are used in manual pages.  As a result, a hollow box
will appear in their place.  On my Windows machine at work, the only
installed font that I could find that would display a hyphen correctly
is Consolas.  An internet post I read also suggested DejaVu Sans Mono,
but I couldn't try it because it is not installed in my machine.
In PuTTY configuration, select

   Window -> Appearance

Then change the font.  Experiment with different fonts.  Display a
man page that has hyphens, such as

   man fstab

and see which fonts display a hyphen and which display a box.  Go
with one which displays the hyphen correctly.  I'd try Consolas first,
then see if you can find another one that's superior to Consolas.

(3) You want the Debian host to know what terminal type you have for
optimum performance.  I recommend using

   Connection -> Data -> Terminal type string : xterm-utf8

(This last setting cannot be changed on the fly.  It can only be set
in PuTTY configuration when there is no active session.)  There is
also a terminal type string "putty" that you can use, but then you lose
the xterm window title strings capability.  Don't use xterm, because
that implies that PuTTY will support VT100 box-drawing escape sequences,
which it won't in UTF-8 mode.  xterm-utf8 tells the host to translate
VT100 box-drawing escape sequences into equivalent UTF-8 sequences.
But it can still use the xterm window title commands, which PuTTY does
support, even in UTF-8 mode.

I hope this is helpful.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1779317973.520777.1405045429998.javamail.r...@md01.wow.synacor.com



Re: PuTTY SSH client security

2014-07-10 Thread Darac Marjal
On Thu, Jul 10, 2014 at 03:19:07AM -0600, Kitty Cat wrote:
>I use PuTTY to connect to my Debian boxes.
> 
>I was concerned about whether PuTTY is susceptible to the Heartbleed bug,
>etc. as I noticed that the program has not had any updates in quite some
>time.
> 
>[1]http://www.chiark.greenend.org.uk/~sgtatham/putty/
> 
>Is this software still considered to be secure?

PuTTY is *not* based on OpenSSL[1], so it has never been susceptible to
the heartbleed bug.

[1]
https://the.earth.li/~sgtatham/putty/0.63/htmldoc/AppendixA.html#faq-misc



signature.asc
Description: Digital signature