On 14/08/2019 03:18, Keith Steensma wrote:
On 8/13/2019 5:29 PM, Keith Steensma wrote:
On 8/13/2019 1:16 PM, Michael Howard wrote:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
On 8/13/19 10:18 PM, Keith Steensma wrote:
On 8/13/2019 5:29 PM, Keith Steensma wrote:
On 8/13/2019 1:16 PM, Michael Howard wrote:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
On 8/13/2019 5:29 PM, Keith Steensma wrote:
On 8/13/2019 1:16 PM, Michael Howard wrote:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM
On 8/13/2019 1:16 PM, Michael Howard wrote:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
On 8/12/2019 4:
On 8/13/2019 1:16 PM, Michael Howard wrote:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
On 8/12/2019 4:
On 13/08/2019 18:40, Keith Steensma wrote:
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
On 8/12/2019 4:00 PM, elvis wrote:
On 12/8/19 11:23 pm, Keith
On 8/13/2019 7:40 PM, Keith Steensma wrote:
>
>
> On 8/13/2019 11:35 AM, Michael Howard wrote:
>> On 13/08/2019 16:31, Joe wrote:
>>> On Tue, 13 Aug 2019 15:28:04 +0200
>>> wrote:
>>>
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
>
> On 8/12/2019 4:00 PM, elvis wrote
On 8/13/2019 11:35 AM, Michael Howard wrote:
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
On 8/12/2019 4:00 PM, elvis wrote:
On 12/8/19 11:23 pm, Keith Steensma wrote:
The same thing happens if
On 13/08/2019 16:31, Joe wrote:
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
On 8/12/2019 4:00 PM, elvis wrote:
On 12/8/19 11:23 pm, Keith Steensma wrote:
The same thing happens if I fill in 'root' as the login even
though a 'roo
On Tue, 13 Aug 2019 15:28:04 +0200
wrote:
> On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
> >
> >
> > On 8/12/2019 4:00 PM, elvis wrote:
> > >On 12/8/19 11:23 pm, Keith Steensma wrote:
> > >>
> > >>The same thing happens if I fill in 'root' as the login even
> > >>though a
On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
>
>
> On 8/12/2019 4:00 PM, elvis wrote:
> >On 12/8/19 11:23 pm, Keith Steensma wrote:
> >>
> >>The same thing happens if I fill in 'root' as the login even
> >>though a 'root' login is not permitted in the default
> >>'sshd_config'
On 8/12/2019 4:00 PM, elvis wrote:
On 12/8/19 11:23 pm, Keith Steensma wrote:
The same thing happens if I fill in 'root' as the login even though a
'root' login is not permitted in the default 'sshd_config'
configuration. Even when I change the configuration to allow for
'root' login, 'r
On 12/8/19 11:23 pm, Keith Steensma wrote:
The same thing happens if I fill in 'root' as the login even though a
'root' login is not permitted in the default 'sshd_config'
configuration. Even when I change the configuration to allow for
'root' login, 'root' can never login.
Try a local
On 2019-08-12 15:45, Keith Steensma wrote:
Just shows SSH started and stopped.?? I may have to modify the start up
routine to include something.
I think I might have had an issue going from windows putty to Linux with
the windows line endings in the public key.
I think I've changed the encodi
On Lu, 12 aug 19, 08:23:17, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
> that both version seem to have the same problem. It's like I'm doing
> something wrong. But these are fresh installs - no modificat
have the same problem. It's like I'm
>>> doing something wrong. But these are fresh installs - no modification.
>>>
>>> With Secure Shell server installed and running on port 22 (or any other
>>> port of your choice) and iptable Chain Input and Output P
o have the same problem. It's like I'm doing
something wrong. But these are fresh installs - no modification.
With Secure Shell server installed and running on port 22 (or any other port
of your choice) and iptable Chain Input and Output Policy Accept All. When
I try to connect fro
ster' (Stable) and found
>>>> that both version seem to have the same problem. It's like I'm doing
>>>> something wrong. But these are fresh installs - no modification.
>>>>
>>>> With Secure Shell server installed and running on port
e are fresh installs - no modification.
With Secure Shell server installed and running on port 22 (or any
other port of your choice) and iptable Chain Input and Output Policy
Accept All. When I try to connect from a Windows machine using
'putty' (without letting 'putty'
nstalls - no modification.
With Secure Shell server installed and running on port 22 (or any other
port of your choice) and iptable Chain Input and Output Policy Accept
All. When I try to connect from a Windows machine using 'putty'
(without letting 'putty' fill in any user
On 2019-08-12 15:22, Keith Steensma wrote:
Using
"PermitRootLogin Yes"
"PubkeyAuthentication yes"
and a SSH key created under putty and placed in the proper location in
the 'root' directory, still gives a "Server refused our Key"
I can't remember.
perhaps you have to restart sshd after changing
table) and
> > > found
> > > that both version seem to have the same problem. It's like I'm doing
> > > something wrong. But these are fresh installs - no modification.
> > >
> > > With Secure Shell server installed and running on port 22 (or an
t; that both version seem to have the same problem. It's like I'm doing
> > > something wrong. But these are fresh installs - no modification.
> > >
> > > With Secure Shell server installed and running on port 22 (or any other
> > > port
> > >
ing wrong. But these are fresh installs - no modification.
With Secure Shell server installed and running on port 22 (or any other port
of your choice) and iptable Chain Input and Output Policy Accept All. When
I try to connect from a Windows machine using 'putty' (without letting
'p
no modification.
>
> With Secure Shell server installed and running on port 22 (or any other port
> of your choice) and iptable Chain Input and Output Policy Accept All. When
> I try to connect from a Windows machine using 'putty' (without letting
> 'putty' fil
On 8/12/2019 3:23 PM, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
> found that both version seem to have the same problem. It's like I'm
> doing something wrong. But these are fresh installs - no modifica
x27;s like I'm
doing something wrong. But these are fresh installs - no
modification.
With Secure Shell server installed and running on port 22 (or any
other
port of your choice) and iptable Chain Input and Output Policy Accept
All. When I try to connect from a Windows machine using '
ong. But these are fresh installs - no modification.
>
> With Secure Shell server installed and running on port 22 (or any other
> port of your choice) and iptable Chain Input and Output Policy Accept
> All. When I try to connect from a Windows machine using 'putty'
> (w
I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
found that both version seem to have the same problem. It's like I'm
doing something wrong. But these are fresh installs - no modification.
With Secure Shell server installed and running on port
hi ya...
been collecting the list of ssh clients for windows...
and its urls...
http://www.Linux-Consulting.com/Security/ssh.windows.txt
have fun
alvin
http://www.linux-1u.net... 1U Raid5 .. aka 1U with 6x80Gb drives ...
On Thu, 30 Nov 2000, Keith G. Murphy wrote:
> Harry Henry Gebel wrote:
+ On Thu, 30 Nov 2000 05:27:24 -0500
+ Subject recommend a secure shell client for Windows
Harry Henry Gebel writes:
|A friend of mine wants me to set up an account for him on our server, and
|since I do not allow telnet logins he needs a Windows SSH client. I checked
|around and there are
Hi,
I have both putty and SecureCRT, here's my oppinions:
putty:
better color terminal emulation
Un*x like cut & paste mouse events
More Un*x like feel
also has available scp client, though you don't need putty to get
pscp.exe
FREE
SecureCRT:
Better port forwarding
More Windows-like (pulldown m
November 30, 2000 7:47 AM
Subject: Re: recommend a secure shell client for Windows
> terraterm with the SSH plugin works very well with exceed.
>
> Slin
>
>
> - Original Message -
> From: "Silver" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, Nove
Am 30.11.2000 17:08 Uhr schrieb Keith G. Murphy unter
[EMAIL PROTECTED]:
> Harry Henry Gebel wrote:
>>
>> A friend of mine wants me to set up an account for him on our server, and
...
search for putty!
fke
Harry Henry Gebel wrote:
>
> A friend of mine wants me to set up an account for him on our server, and
> since I do not allow telnet logins he needs a Windows SSH client. I checked
> around and there are quite a number of them out there, can anybody
> recommend which is the best? I do not have a W
I wondered if anyone was going to mention teraterm with the SSH plugin
(available as a separate download). It's what we use here at the university,
but now I'm curious about putty. Anyone know the feature differences?
Chas
[EMAIL PROTECTED]
> terraterm with the SSH plugin works very well with exc
terraterm with the SSH plugin works very well with exceed.
Slin
- Original Message -
From: "Silver" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 30, 2000 8:09 PM
Subject: Re: recommend a secure shell client for Windows
> Ok, everyone is saying putty is work
11:27 AM
Subject: recommend a secure shell client for Windows
> A friend of mine wants me to set up an account for him on our server, and
> since I do not allow telnet logins he needs a Windows SSH client. I
checked
> around and there are quite a number of them out there, can anybody
>
> A friend of mine wants me to set up an account for him on our server, and
> since I do not allow telnet logins he needs a Windows SSH client. I
> checked
> around and there are quite a number of them out there, can anybody
> recommend which is the best?
I use putty:
- No ablity to save passwor
On Thu, Nov 30, 2000 at 05:27:24AM -0500, Harry Henry Gebel wrote:
> A friend of mine wants me to set up an account for him on our server, and
> since I do not allow telnet logins he needs a Windows SSH client. I checked
> around and there are quite a number of them out there, can anybody
> recomme
At 05:27 AM 11/30/2000 -0500, Harry Henry Gebel wrote:
>A friend of mine wants me to set up an account for him on our server, and
>since I do not allow telnet logins he needs a Windows SSH client.
Everyone here recommeded Putty to me when i had the same problem and its
certainly working well for
A friend of mine wants me to set up an account for him on our server, and
since I do not allow telnet logins he needs a Windows SSH client. I checked
around and there are quite a number of them out there, can anybody
recommend which is the best? I do not have a Windows machine to test them
out on,
> directory called .ssh in my home, it has permissions 711
700 should be enough, i think.
> (chmod 600 authorized_keys). But I dont know how to place the key in that
> file(authorize_keys).
simply paste the contents of the public key file. it should be a single
line, which is in the same format, as
I need help with using and setting up ssh. I downloaded a secure shell
client(ttssh. and now I am working on setting up the server side. I ran
ssh-keygen and created a RSA key. Where will I place the key. I have made a
directory called .ssh in my home, it has permissions 711
(chmod 711 .ssh
Jim McCloskey <[EMAIL PROTECTED]> writes:
> When I did an upgrade against `froozen' today, the post-install script
> for OpenBSD Secure Shell hung. PS reports it as a zombie process. The
> last message to the console was:
>
> Unpacking replacement ssh ...
> Setting
; From: Jim McCloskey [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 21, 2000 12:57 AM
> > To: debian-user@lists.debian.org
> > Cc: [EMAIL PROTECTED]
> > Subject: OpenBSD Secure Shell
> >
> >
> >
> > When I did an upgrade against `froozen&#x
s.debian.org
> Cc: [EMAIL PROTECTED]
> Subject: OpenBSD Secure Shell
>
>
>
> When I did an upgrade against `froozen' today, the post-install script
> for OpenBSD Secure Shell hung. PS reports it as a zombie process. The
> last message to the console was:
>
> Unp
A ctrl-C, then a re-install worked just fine.
Thus spake Pollywog ([EMAIL PROTECTED]):
>
> On 20-Apr-2000 22:56:31 Jim McCloskey wrote:
> >
> > When I did an upgrade against `froozen' today, the post-install
> > script
> > for OpenBSD Secure Shell hung
On 20-Apr-2000 22:56:31 Jim McCloskey wrote:
>
> When I did an upgrade against `froozen' today, the post-install
> script
> for OpenBSD Secure Shell hung. PS reports it as a zombie process.
> The
> last message to the console was:
It stalled on me while installi
When I did an upgrade against `froozen' today, the post-install script
for OpenBSD Secure Shell hung. PS reports it as a zombie process. The
last message to the console was:
Unpacking replacement ssh ...
Setting up ssh (1.2.3-2) ...
Starting OpenBSD Secure Shell server: sshd.
The server wa
On Thu, Feb 26, 1998 at 04:05:52PM -, Paulo Jorge de Almeida wrote:
> I am looking for pre-compiled ready-to-install SOCKS5 1.0r4
I can't find a socks5 package. If you are interested in making a package for
it, please check out http://www.debian.org/devel/help.html .
> and S
Hi!
I am looking for pre-compiled ready-to-install SOCKS5 1.0r4 and Secure Shell
debian packages. I already have the source code, but since I am installing
these aplications on quite a few machines, it would make my job easier if I
could install them directly without having to compile
"D. Hageman" <[EMAIL PROTECTED]> writes:
> Where can I get a version of Secure Shell for Debian?
>
> I tried to compile the source I retrieved off the internet, but it didn't
> work for me.
>
> ~ D. Hageman ([EMAIL PROTECTED])
IF ssh were available
hu, 22 Jan 1998, D. Hageman wrote:
> Where can I get a version of Secure Shell for Debian?
>
> I tried to compile the source I retrieved off the internet, but it didn't
> work for me.
>
> ~ D. Hageman ([EMAIL PROTECTED])
>
>
> --
> TO UNSUBSCRIBE FROM THIS M
Where can I get a version of Secure Shell for Debian?
ftp://nonus.debian.org/debian-non-US
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Where can I get a version of Secure Shell for Debian?
I tried to compile the source I retrieved off the internet, but it didn't
work for me.
~ D. Hageman ([EMAIL PROTECTED])
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trou
On Wed, 8 Oct 1997, Chi Wong wrote:
> I was wondering is there a debain package for secure shell?
yup. Hit the package search page (start at www.debian.org) and search for
ssh.
Will
[EMAIL PROTEC
I was wondering is there a debain package for secure shell?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
58 matches
Mail list logo
