-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jussi Ekholm <[EMAIL PROTECTED]> wrote:
(Replying to myself, sorry - just trying to provide extra information)
> Dietmar Goldbeck <[EMAIL PROTECTED]> wrote:
>> On Sat, Jun 22, 2002 at 02:20:20AM -0500, Rob VanFleet wrote:
>> It is very difficult to h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dietmar Goldbeck <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 22, 2002 at 02:20:20AM -0500, Rob VanFleet wrote:
>> On machine A, I run ssh-keygen, and generate an identity and
>> identity.pub. I copy identity.pub to ~/.ssh/authorized_keys on Machine
>> B,
Hi
Something strange has just happened to me. I've installed two very
different boxes (nela is K7/1.3 GHz, yolanda is IBM Pentium 100) using
ReiserFS boot disks for Woody, and one CD, and later upgraded via iNet.
After finishing installation of base system, and adding some other
packages (postfix
Howland, Curtis wrote:
>First question:
>
>Has it worked before now?
>
>Second question:
>
>What did you change between then and now?
>
>Curt-
>
>
>
>>Dear All,
>>
>>I have a problem with my ssh, when i try to connect to our
>>server using
>>ssh have an error like this :
>>
>>ssh -l [EMAIL PROT
The lastlog does work upon further inspection and I downgraded the bug to
"normal"
I was debugging another problem I had and I saw that one...which turned
out not to be a problem at all...just a inert bug.
Phil
On Fri, Jun 28, 2002 at 04:28:00PM -0400, Brian P. Flaherty wrote:
> Hello,
>
> I a
Hello,
I am running woody and I just logged into my machine with ssh, and my
lastlog was updated. On my machine, wtmp and lastlog are user root,
group utmp, and both are rw,rw,r only. Does this mean that priviledge
separation is not happening on my machine or is this a difference
between woody a
Forwarding this bug to debian-security as I feel it is related to our recent SSH
issues...
Bug number is 151297
Phil
- Forwarded message from Phillip <[EMAIL PROTECTED]> -
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Fri, 28 Jun 2002 14:21:34 -0400
From: Phillip <[EMAIL PROTECTED]>
To:
* Phillip Hofmeister ([EMAIL PROTECTED]) [020628 08:38]:
> *Jun 28 11:31:34 Genesis PAM-env[5338]: Unable to open config file:
> Permission denied*
It seems that this is related to the PAM breakage noted in the recent
versions with priv sep enabled. My guess would be that sinc
Hi Andreas,
It could be a couple of things:
Ok, what is your permissions on /etc/ssh/ssh_config,
and the ~/.ssh directory?
Also, ask your ISP if they've had networking problems.
They could have also change the sshd_config and you could
be doing DNS Name checking as well.
-Anne
This one time,
On Mon, Jun 24, 2002 at 07:33:12AM -0400, Anthony DeRobertis wrote:
>
> On Sunday, June 23, 2002, at 05:21 , Matthew Sackman wrote:
>
> >If I've missed something obvious, please shout at me ;-)
>
> Only problem is that a Snort that has reached its second
> birthday may not be happy with the new
[On 28 Jun, 2002, Andreas Syksa wrote in "Re[2]: YASP (Yet Ano ..."]
> Hello Wouter,
>
> Friday, June 28, 2002, 3:15:13 PM, you wrote:
>
> WvG> Have you tried removing the existing hostkey's from your know_host file
> WvG> on the client ?
>
> yes, I've already tried this as well - but this also
logcheck keeps flagging this and I was wondering if anyone
could provide some insight as to the cause
Thanks,
Phil
Jun 28 11:31:34 Genesis sshd[5336]: Accepted password for plhofmei from 127.0.0.
1 port 1154 ssh2
Jun 28 11:31:34 Genesis PAM_unix[5338]: (ssh) session opened for user plhofmei
Hello Wouter,
Friday, June 28, 2002, 3:15:13 PM, you wrote:
WvG> Have you tried removing the existing hostkey's from your know_host file
WvG> on the client ?
yes, I've already tried this as well - but this also does not work.
WvG> look in ~/.ssh.known_host or ~/.ssh.known_host2
I deleted the k
Hi,
Have you tried removing the existing hostkey's from your know_host file
on the client ?
Maybe your client is to strict, it sees a different key than expected and
kicks you out. So delete exeisting know keys for 23.42.23.42 on your
client en try to reconnect.
look in ~/.ssh.known_host or ~/.s
You can also use apt-get dselect-upgrade. I think the problem was
that one of the first ssh upgrades conflicted with an rsh package.
apt-get dselect-upgrade removed it for me and installed the new
ssh.
>
> Use apt-get -u upgrade to show what packages are being upgraded, then
> apt-get install th
Hello List,
I got a nasty problem after I've updated my OpenSSH to
Version 3.3:
Right after the update everything worked fine for me.
I could connect to the server - tested everything - fine.
At home, with my laptop in my bed I connected last time
and was suddenly kicked out.
I was not able to r
Title: unsubscribe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 27, 2002 at 09:25:52PM +0700, [EMAIL PROTECTED] wrote:
> Dear All,
>
> I have a problem with my ssh, when i try to connect to our server using
> ssh have an error like this :
>
> ssh -l [EMAIL PROTECTED]
> 2f65 7463 2f73 7368
> Disconnect
sorry JGB, pressed the wrong button in my last mail to you...
Jan-Benedict Glaw wrote:
If it is not this problem, this looks like you try to connect with a
ssh1 client to a ssh2 server...
i had the same problem (bad packet length) a week ago with a brand-new
out-of-the-box installation.
it
Join Excite! - http://www.excite.comThe most personalized portal on the Web!
On Fri, 2002-06-28 08:38:51 +0300, Sami Haahtinen <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> On Thu, Jun 27, 2002 at 09:25:52PM +0700, [EMAIL PROTECTED] wrote:
> > I have a problem with my ssh, when i try to connect to our server using
> > ssh have an error like this :
> >
> > ssh
On Thu, Jun 27, 2002 at 09:25:52PM +0700, [EMAIL PROTECTED] wrote:
> I have a problem with my ssh, when i try to connect to our server using
> ssh have an error like this :
>
> ssh -l [EMAIL PROTECTED]
> 2f65 7463 2f73 7368
> Disconnecting: Bad packet length 795178083.
>
> What's Wrong with my se
22 matches
Mail list logo
