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 modification.
>
> With Secure Shell server i
On 8/12/2019 4:42 PM, Keith Steensma wrote:
>
>
> On 8/12/2019 9:18 AM, john doe wrote:
>> 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 someth
On 8/12/2019 9:34 AM, Dan Ritter wrote:
Keith Steensma wrote:
On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
that both version seem to have the same
On 8/12/2019 4:34 PM, Dan Ritter wrote:
> Keith Steensma wrote:
>>
>>
>> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
>>> On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
that both version seem t
Is there anything useful in /var/log/sshd.log?
Bruce
On 8/12/19 9:23 AM, 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 m
On 8/12/2019 9:18 AM, john doe wrote:
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 modification.
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
On Mon, Aug 12, 2019 at 09:32:42AM -0500, Keith Steensma wrote:
>
>
> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
> > On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
> > > I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
> > > found
> > > that both versio
Keith Steensma wrote:
>
>
> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
> > On Mon, Aug 12, 2019 at 08:23:17AM -0500, 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 li
On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
On Mon, Aug 12, 2019 at 08:23:17AM -0500, 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 fre
On Mon, Aug 12, 2019 at 08:23:17AM -0500, 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 modification.
>
> With Secure
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 modification.
>
> With Secure Shell server installe
On 2019-08-12 14:33, Judah Richardson wrote:
Try logging in as a user that has sudo power.
On Mon, Aug 12, 2019, 08:31 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 some
Try logging in as a user that has sudo power.
On Mon, Aug 12, 2019, 08:31 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 -
> 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
"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 on US debian mirrors for download from outside
You can find a Debian package for it on a non-US mirror. View the file
README.non-US in the Debian root ftp dir for a current list of mirrors.
Dennis
--
dpk <[EMAIL PROTECTED]>, Network Administrator | work: 353.4844
Division of Engineering Computing Services | page: 222.5875
On Thu, 22
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] .
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 PROTECTED]
33 matches
Mail list logo
