On Sun, Jun 16, 2024 at 10:33 PM George at Clug wrote:
>
> Rayan,
>
> On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:
> > On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> > > On one of my machines, I have some interesting interference. Bluetooth
> > > works just fine, and
On 6/16/24 19:27, George at Clug wrote:
Rayan,
On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:
On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
On one of my machines, I have some interesting interference. Bluetooth
works just fine, and so does networking. Bluetooth is
Rayan,
On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:
> On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> > On one of my machines, I have some interesting interference. Bluetooth
> > works just fine, and so does networking. Bluetooth is normally disabled.
> > However, when
On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> On one of my machines, I have some interesting interference. Bluetooth
> works just fine, and so does networking. Bluetooth is normally disabled.
> However, when I have Bluetooth turned on (and after I turn it off), SSH
> is *slow*.
On one of my machines, I have some interesting interference. Bluetooth
works just fine, and so does networking. Bluetooth is normally disabled.
However, when I have Bluetooth turned on (and after I turn it off), SSH
is *slow*.
I gather that the network controller is also the Bluetooth controller:
Hi,
You should enable kernel dump logs. auth log is worst place for searching
the cause of crashing.
2016-02-18 23:13 GMT+02:00 Chris :
> Dear All,
>
> after the following entry
>
> Feb 18 17:48:05 jupiter sshd[30204]: pam_unix(sshd:auth): authentication
> failure;
On Thu, Feb 18, 2016 at 10:13:48PM +0100, Chris wrote:
> Dear All,
>
> after the following entry
>
> Feb 18 17:48:05 jupiter sshd[30204]: pam_unix(sshd:auth): authentication
> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.93
> user=root
>
On Thu, 18 Feb 2016, Chris wrote:
> after the following entry
>
> Feb 18 17:48:05 jupiter sshd[30204]: pam_unix(sshd:auth): authentication
> failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.93
> user=root
>
Hi Claudius,
Am Sunday 11 November 2012 schrieb Claudius Hubig:
Hello Rainer,
[ Removed useless crap from quote, cf.
20122039.14270...@bokomoko.de for original ]
Rainer Dorsch m...@bokomoko.de wrote:
Am Sunday 11 November 2012 schrieb Selim T. Erdogan:
Rainer Dorsch, 11.11.2012:
Rainer Dorsch m...@bokomoko.de writes:
Hi Claudius,
Am Sunday 11 November 2012 schrieb Claudius Hubig:
Hello Rainer,
[ Removed useless crap from quote, cf.
20122039.14270...@bokomoko.de for original ]
Rainer Dorsch m...@bokomoko.de wrote:
Am Sunday 11 November 2012 schrieb Selim
Hello,
I have on a Debian squeeze server an issue, that I can only login as user rd,
not as user gpxrecorder, although there seems to be no difference in the
accounts:
bokomoko:~# diff ~rd/.ssh/authorized_keys ~gpxrecorder/.ssh/authorized_hosts
bokomoko:~# ls -l ~rd/.ssh/authorized_keys
On 11/11/2012 14:39, Rainer Dorsch wrote:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user rd,
not as user gpxrecorder, although there seems to be no difference in the
accounts:
bokomoko:~# diff ~rd/.ssh/authorized_keys ~gpxrecorder/.ssh/authorized_hosts
Rainer Dorsch, 11.11.2012:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user rd,
not as user gpxrecorder, although there seems to be no difference in the
accounts:
bokomoko:~# diff ~rd/.ssh/authorized_keys ~gpxrecorder/.ssh/authorized_hosts
bokomoko:~# ls
On 11/11/12 11:39, Rainer Dorsch wrote:
I have on a Debian squeeze server an issue, that I can only login as user rd,
not as user gpxrecorder, although there seems to be no difference in the
accounts:
bokomoko:~# diff ~rd/.ssh/authorized_keys ~gpxrecorder/.ssh/authorized_hosts
Have you
Am Sunday 11 November 2012 schrieb staticsafe:
On 11/11/2012 14:39, Rainer Dorsch wrote:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user
rd, not as user gpxrecorder, although there seems to be no difference in
the accounts:
bokomoko:~# diff
On Sunday, November 11, 2012 02:39:14 PM Rainer Dorsch wrote:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user
rd, not as user gpxrecorder, although there seems to be no difference in
the accounts:
I'll bet some key files in .ssh/ are readable by other than
Am Sunday 11 November 2012 schrieb Selim T. Erdogan:
Rainer Dorsch, 11.11.2012:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user
rd, not as user gpxrecorder, although there seems to be no difference in
the accounts:
bokomoko:~# diff
Am Sunday 11 November 2012 schrieb David Christensen:
On 11/11/12 11:39, Rainer Dorsch wrote:
I have on a Debian squeeze server an issue, that I can only login as user
rd, not as user gpxrecorder, although there seems to be no difference in
the accounts:
bokomoko:~# diff
On 11/11/2012 16:44, Rainer Dorsch wrote:
Am Sunday 11 November 2012 schrieb staticsafe:
On 11/11/2012 14:39, Rainer Dorsch wrote:
Hello,
I have on a Debian squeeze server an issue, that I can only login as user
rd, not as user gpxrecorder, although there seems to be no difference in
the
On 11/11/12 13:48, Rainer Dorsch wrote:
Hmm...authorized_keys contain keys from the user who wants to login. I does
not make sense to generate keys for the gpxrecorder account (?).
I typically create user keys on both ends. The O/S installer and/or
package manager typically create host keys
Am Sunday 11 November 2012 schrieb Selim T. Erdogan:
How come you're diffing authorized_keys for rd and authorized_hosts for
gpxrecorder?
Good eyes. I use only authorized_keys on my machines.
I suggest renaming authorized_hosts to authorized_keys for gpxrecorder.
David
--
To
Hello Rainer,
[ Removed useless crap from quote, cf.
20122039.14270...@bokomoko.de for original ]
Rainer Dorsch m...@bokomoko.de wrote:
Am Sunday 11 November 2012 schrieb Selim T. Erdogan:
Rainer Dorsch, 11.11.2012:
bokomoko:~# ls -l ~rd/.ssh/authorized_keys
On Sun, Nov 11, 2012 at 02:22:34PM -0800, David Christensen wrote:
On 11/11/12 13:48, Rainer Dorsch wrote:
Hmm...authorized_keys contain keys from the user who wants to login. I does
not make sense to generate keys for the gpxrecorder account (?).
I typically create user keys on both ends.
On 13 March 2011 02:28, Adrian Levi adrian.l...@gmail.com wrote:
On the server to get key based auth working you must:
1)Have the correct permissions on .ssh/*
Permissions on all ~/.ssh are fine and correct at 0644
2) have your public key in authorized_keys
Both authorized_keys on the server
This is now solved. MaxAuthRetries was set to 1, so when the server
rejected the ID, it exceeded the value.
Increasing this amount so the server could procede to password
interactive login worked and let me send the new keyfile to server.
Thanks for all your help.
--
To UNSUBSCRIBE, email to
I've got a slight issue with logging into my server using public keys.
It was working fine, until I had to rebuild my desktop machine. I had
the key copied to the server, and passwordless logins where fine.
However now I have rebuilt my desktop, I cant get to the login.
So heres whats happend.
I've got a slight issue with logging into my server using public keys.
It was working fine, until I had to rebuild my desktop machine. I had
the key copied to the server, and passwordless logins where fine.
However now I have rebuilt my desktop, I cant get to the login.
So heres whats happend.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 13/03/2011 00:00, Michael Thompson a écrit :
I've got a slight issue with logging into my server using public keys.
Could you paste the output of « grep sshd /var/log/auth.log »?
- --
Aeris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11
On 13 March 2011 08:37, Michael Thompson maverickapo...@gmail.com wrote:
I've got a slight issue with logging into my server using public keys.
It was working fine, until I had to rebuild my desktop machine. I had
the key copied to the server, and passwordless logins where fine.
However now
29 matches
Mail list logo