Re: ssh-keygen as a regular user

On 12/05/2023 09:36, Vincent Lefevre wrote: On 2023-05-12 18:23:41 +0800, jeremy ardley wrote: cd mkdir .ssh chmod 700 .ssh ssh-keygen Is there any reason why ssh-keygen doesn't create a .ssh directory (with the right permissions) if it doesn't exist yet? It does, and even let's you know

Re: ssh-keygen as a regular user

On 2023-05-12 18:23:41 +0800, jeremy ardley wrote: > cd > > mkdir .ssh > > chmod 700 .ssh > > ssh-keygen Is there any reason why ssh-keygen doesn't create a .ssh directory (with the right permissions) if it doesn't exist yet? -- Vincent Lefèvre - Web: 100% accessibl

Re: ssh-keygen as a regular user

On 12/5/23 13:50, Jeremy Ardley wrote: ode[ ssh-keygen usually works better than ssh-keygem try cd mkdir .ssh ssh-keygen I now remember some ssh functions check file and directory permissions and will fail if not correct Improved procedure: cd mkdir .ssh chmod 700 .ssh ssh-keyge

Re: ssh-keygen as a regular user

On 11/5/23 11:22, Igor Korot wrote: [code] igor@wxTest:~/wxwidgets$ ssh-keygem bash: ssh-keygem: command not found igor@wxTest:~/wxwidgets$ su Password: root@wxTest:/home/igor/wxwidgets# apt-get install openssh-client Reading package lists... Done Building dependency tree Reading state informa

Re: ssh-keygen as a regular user

Hi, On Fri, May 12, 2023 at 12:19 AM Geert Stappers wrote: > > On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote: > > Hi, ALL, > > Is there a reason I can't run "ssh-keygen" as a regular user? > > Several :-) > > > > I am able to do it as "root" though, but I think it shouldn't happen.

Re: ssh-keygen as a regular user

On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote: > Hi, ALL, > Is there a reason I can't run "ssh-keygen" as a regular user? Several :-) > I am able to do it as "root" though, but I think it shouldn't happen. > > Can someone shed some light? Find a better way to open a discussion

Re: ssh-keygen as a regular user

On 12/5/23 13:07, Igor Korot wrote: Hi, ALL, Is there a reason I can't run "ssh-keygen" as a regular user? I am able to do it as "root" though, but I think it shouldn't happen. Check the file permissions and ownership of ~/.ssh files ? -- Jeremy (Lists)

Re: ssh-add after graphical login

Le 3/23/23 à 17:53, Erwan David a écrit : I create a shell script ~/bin/start-session.sh in this script I have the command ssh-add < - in System Settings > Startup and Shutdown > autostart I add this script as a login script Thanks Erwan, that's what I ended up doing. the ssh-add < - line l

Re: ssh-add after graphical login

Le 23/03/2023 à 09:42, Yassine Chaouche a écrit : Hello all, I'd like something to run ssh-add right after I login to my desktop (KDE). ssh-add needs to prompt me for my passphrase, and doesn't need any privileges. What are my options? Best, I  do this way : I create a shell script ~/bin/s

Re: ssh-add after graphical login

On 2023-03-23 09:42:53 +0100, Yassine Chaouche wrote: > I'd like something to run ssh-add right after I login to my desktop > (KDE). > ssh-add needs to prompt me for my passphrase, > and doesn't need any privileges. > > What are my options? FYI, with zsh, I'm using wrappers so that I don't need t

Re: ssh-add after graphical login

On Thu, Mar 23, 2023 at 8:57 AM Greg Wooledge wrote: > > On Thu, Mar 23, 2023 at 08:53:48AM -0400, Jeffrey Walton wrote: > > On Thu, Mar 23, 2023 at 4:43 AM Yassine Chaouche > > wrote: > > > > > > I'd like something to run ssh-add right after I login to my desktop > > > (KDE). > > > ssh-add needs

Re: ssh-add after graphical login

On Thu, Mar 23, 2023 at 08:53:48AM -0400, Jeffrey Walton wrote: > On Thu, Mar 23, 2023 at 4:43 AM Yassine Chaouche > wrote: > > > > I'd like something to run ssh-add right after I login to my desktop > > (KDE). > > ssh-add needs to prompt me for my passphrase, > > and doesn't need any privileges.

Re: ssh-add after graphical login

On Thu, Mar 23, 2023 at 4:43 AM Yassine Chaouche wrote: > > I'd like something to run ssh-add right after I login to my desktop > (KDE). > ssh-add needs to prompt me for my passphrase, > and doesn't need any privileges. > > What are my options? You can remove the passphrase from the key. Then you

Re: ssh-add after graphical login

Le 3/23/23 à 12:24, Greg Wooledge a écrit : ssh-add Ah! this is what I was missing! the whole problem was how to ssh-add in a graphical way, now that I have found a way, I can maybe put it in a script inside the XDG Autostart directory. This might leave more room for the ssh-agent to start

Re: ssh-add after graphical login

Le 3/23/23 à 12:56, basti a écrit : The ssh config inside ~/.ssh/ has an option 'AddKeysToAgent'. Why you don't use this? For example: Host *    ControlMaster auto    ControlPath /run/user/%i/%r@%h-%p    IdentityFile ~/.ssh/id_rsa    ControlPersist 3600    User root    AddKeysToAgent yes

Re: ssh-add after graphical login

Le 23 mars 2023 Greg Wooledge a écrit : > The only part I'm unsure of, for you, is how to ensure that this runs > *after* your ssh agent has already been started. I don't know how ssh > agent startup is handled with Display Manager logins, since I don't use > a DM, and I just start ssh-agent myse

Re: ssh-add after graphical login

The ssh config inside ~/.ssh/ has an option 'AddKeysToAgent'. Why you don't use this? For example: Host * ControlMaster auto ControlPath /run/user/%i/%r@%h-%p IdentityFile ~/.ssh/id_rsa ControlPersist 3600 User root AddKeysToAgent yes See man ssh_config On 23.03.23 09:42, Yas

Re: ssh-add after graphical login

On Thu, Mar 23, 2023 at 09:42:53AM +0100, Yassine Chaouche wrote: > I'd like something to run ssh-add right after I login to my desktop > (KDE). > ssh-add needs to prompt me for my passphrase, > and doesn't need any privileges. > > What are my options? On Debian you can create a ~/.xsessionrc fil

Re: ssh bug known_hosts?

On Thu, Mar 02, 2023 at 09:52:35AM +0800, Jeremy Ardley wrote: > On 2/3/23 05:51, Greg Wooledge wrote: > > unicorn:~$ namei -l ~/.ssh/config > > f: /home/greg/.ssh/config > > drwxr-xr-x root root / > > drwxr-xr-x root root home > > drwxr-xr-x greg greg greg > > drwxr-xr-x greg greg .ssh > > -rw-r--

Re: ssh bug known_hosts?

On Wed, Mar 1, 2023 at 8:53 PM Jeremy Ardley wrote: > [...] > However I've found the cause of the problem, but not necessarily > resolved the bug. > > For some reason on my journey /etc/ssh/ssh_config had acquired > > UserKnownHostsFile /etc/ssh/ssh_known_hosts > > changing to > > # UserKnow

Re: ssh bug known_hosts?

On 2/3/23 05:51, Greg Wooledge wrote: On Wed, Mar 01, 2023 at 02:43:38PM -0700, Charles Curley wrote: On Thu, 2 Mar 2023 03:48:49 +0800 jeremy ardley wrote: 2. The known hosts file used is /etc/ssh/known_hosts rather that ~/.ssh/known_hosts - which causes a permissions error I am not seein

Re: ssh bug known_hosts?

On 2/3/23 05:52, Jeffrey Walton wrote: On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote: I may have found a bug in openssh. [...] I have created a ~/.ssh/config file with contents Host jeremy_client HostName client.example.com User jeremy IdentityFile ~/.ssh/com.example.j

Re: ssh bug known_hosts?

On Wed, Mar 01, 2023 at 04:52:57PM -0500, Jeffrey Walton wrote: > On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote: > > > > I may have found a bug in openssh. > > [...] > > I have created a ~/.ssh/config file with contents > > > > Host jeremy_client > > HostName client.example.com > >

Re: ssh bug known_hosts?

On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote: > > I may have found a bug in openssh. > [...] > I have created a ~/.ssh/config file with contents > > Host jeremy_client > HostName client.example.com > User jeremy > IdentityFile ~/.ssh/com.example.jeremy.id_rsa Does ssh_config(

Re: ssh bug known_hosts?

On Wed, Mar 01, 2023 at 02:43:38PM -0700, Charles Curley wrote: > On Thu, 2 Mar 2023 03:48:49 +0800 > jeremy ardley wrote: > > > 2. The known hosts file used is /etc/ssh/known_hosts rather that > > ~/.ssh/known_hosts - which causes a permissions error > > I am not seeing that, for either root o

Re: ssh bug known_hosts?

On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote: > > I may have found a bug in openssh. > > I raise it here as the ssh mailing list is actually a newsgroup that > no-one seems to use. You might give comp.security.openssh a try: https://groups.google.com/g/comp.security.ssh . That is the genera

Re: ssh bug known_hosts?

On Thu, 2 Mar 2023 03:48:49 +0800 jeremy ardley wrote: > 2. The known hosts file used is /etc/ssh/known_hosts rather that > ~/.ssh/known_hosts - which causes a permissions error I am not seeing that, for either root or my regular non-root user. You indicated you created your ~/.ssh/config as s

Re: ssh pub.key

On Mon, Feb 20, 2023 at 8:21 PM wrote: > > Normaly i use the same ssh.pub.key for different servers; Does this mean you use the same SSH keys for your user account, and SSH into servers with the one key pair? If so, I think this is expected. Or do you mean all the servers/sshd use the same SSH k

Re: ssh pub.key

On 2/21/23 02:05, latin...@vcn.bc.ca wrote: Hello Normaly i use the same ssh.pub.key for different servers; but when i use it with a Debian totally encripted 4th option of the installer; i am not able to login! Is tgere something different in that case? - How so? - Do you see anything in th

Re: ssh -X authentication with sudo

I really didn't mean to kick this off ;) Original poster: instead of the GUI programm, I recommend you try cfdisk. It's not "graphical", but it has a nice UI, and it can do everything you need. `sudo cfdisk /dev/device` and you're going to be much happier. -- .''`. martin f. krafft @mart

Re: ssh -X authentication with sudo

On Wed, 05 Oct 2022 10:59:47 -0400 The Wanderer wrote: > > Sorry, must have missed the memo that made an apparently-typo-ed > > double question mark into an emoticon. > > It's not an emoticon. There is a convention, which if I'm not mistaken > goes back decades and originates well before emoti

Re: ssh -X authentication with sudo

On 2022-10-05 at 11:21, debian-u...@howorth.org.uk wrote: >> On 2022-10-05 at 10:48, debian-u...@howorth.org.uk wrote: >>> Perhaps you could explain why the debian manpage specifically >>> says it must be run as root then? >> >> What is "it" here? That is, what is the specific program to whose >

Re: ssh -X authentication with sudo

> On 2022-10-05 at 10:48, debian-u...@howorth.org.uk wrote: > > >> On Wed, Oct 05, 2022 at 10:30:37AM +0100, > >> debian-u...@howorth.org.uk wrote: > > >>> Yes, I am running a GUI as root. It won't run as normal user. > >> > >> You seem to have missed the implied criticism and/or incredulity

Re: ssh -X authentication with sudo

On 2022-10-05 at 10:48, debian-u...@howorth.org.uk wrote: >> On Wed, Oct 05, 2022 at 10:30:37AM +0100, >> debian-u...@howorth.org.uk wrote: >>> Yes, I am running a GUI as root. It won't run as normal user. >> >> You seem to have missed the implied criticism and/or incredulity. >> Hint: look at

Re: ssh -X authentication with sudo

> On Wed, Oct 05, 2022 at 10:30:37AM +0100, debian-u...@howorth.org.uk > wrote: > > > Regarding the following, written by "debian-u...@howorth.org.uk" > > > on 2022-10-04 at 13:52 Uhr +0100: > > > >PS as you surmised, I don't really want root ssh access. > > > > > > But you are running GUIs

Re: ssh -X authentication with sudo

On Wed, 05 Oct 2022 15:52:58 +0300 Anssi Saari wrote: Hello Anssi, >I only run one, GParted. As I don't mess around with partitions that >often I want a clear GUI tool that hopefully shows me if I'm about to do >something catastrophical. IOW, I don't see an alternative. AFAIR, you run GParted a

Re: ssh -X authentication with sudo

martin f krafft writes: > But you are running GUIs as root?? I only run one, GParted. As I don't mess around with partitions that often I want a clear GUI tool that hopefully shows me if I'm about to do something catastrophical. IOW, I don't see an alternative.

Re: ssh -X authentication with sudo

On Wed, Oct 05, 2022 at 10:30:37AM +0100, debian-u...@howorth.org.uk wrote: > > Regarding the following, written by "debian-u...@howorth.org.uk" on > > 2022-10-04 at 13:52 Uhr +0100: > > >PS as you surmised, I don't really want root ssh access. > > > > But you are running GUIs as root?? > > Yes

Re: ssh -X authentication with sudo

On 2022-10-05 at 05:30, debian-u...@howorth.org.uk wrote: >> Regarding the following, written by "debian-u...@howorth.org.uk" >> on 2022-10-04 at 13:52 Uhr +0100: >> >>> PS as you surmised, I don't really want root ssh access. >> >> But you are running GUIs as root?? > > Yes, I am running a GUI

Re: ssh -X authentication with sudo

> Regarding the following, written by "debian-u...@howorth.org.uk" on > 2022-10-04 at 13:52 Uhr +0100: > >PS as you surmised, I don't really want root ssh access. > > But you are running GUIs as root?? Yes, I am running a GUI as root. It won't run as normal user.

Re: ssh -X authentication with sudo

Regarding the following, written by "debian-u...@howorth.org.uk" on 2022-10-04 at 13:52 Uhr +0100: PS as you surmised, I don't really want root ssh access. But you are running GUIs as root?? -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.deb

Re: ssh -X authentication with sudo

On 4/10/22 8:52 pm, debian-u...@howorth.org.uk wrote: To use the display without ssh root login. ssh as normal user to host. Then echo $DISPLAY su - export DISPLAY=localhost:10 (or whatever your logged in user DISPLAY is set to) xauth add $(xauth -f ~/.Xauthority list | tail -1) xhost Tha

Re: ssh -X authentication with sudo

> On 4/10/22 7:39 pm, Greg Wooledge wrote: > > Change the sshd_config to allow direct root logins. > > Then do ssh -X r...@debian.box. > > > > If you're the paranoid type, or if the Debian system is exposed to > > the public Internet, then make sure you only permit root logins > > when using pubkey

Re: ssh -X authentication with sudo

On 4/10/22 7:39 pm, Greg Wooledge wrote: Change the sshd_config to allow direct root logins. Then do ssh -X r...@debian.box. If you're the paranoid type, or if the Debian system is exposed to the public Internet, then make sure you only permit root logins when using pubkey authentication, not p

Re: ssh -X authentication with sudo

On Tue, Oct 04, 2022 at 12:31:23PM +0100, Dave Howorth wrote: > I have a machine running debian that I access using ssh. I use the -X > with ssh and can successfully run e.g. xeyes on the debian machine > showing the display on my local machine. But now I want to run a > graphical program that need

Re: ssh certificate authentication: can one user and one server certificate work for any number of users or servers on a LAN?

rhkra...@gmail.com wrote: > I am (still) rather confused about using ssh certificate authentication. > > I am confused about a variety of specifics, but the biggie is this: I have > the > idea that I can create one user certificate and one server (host) > certificate, > and use that for any n

Re: SSH resources, specifically on certificates (certificate authentication)

On 7/15/22 05:32, Curt wrote: The question I ask myself preliminarily, before delving further into the matter, is whether certificate-based SSH authentication is appropriate for a home LAN with three users. +1 I decided SSH with publickey authentication and passphrase keys were plenty for

Re: SSH resources, specifically on certificates (certificate authentication)

On Friday, July 15, 2022 08:49:01 AM to...@tuxteam.de wrote: > On Fri, Jul 15, 2022 at 12:32:35PM -, Curt wrote: > > The question I ask myself preliminarily, before delving further into > > the matter, is whether certificate-based SSH authentication is > > appropriate for a home LAN with three

3 more surprising (to me) things about ssh (was: Re: SSH resources, specifically on certificates (certificate authentication))

Thanks for the response, and to dsr as well. I won't really ask a question here, but I will make some comments -- not sure how / where to fit them in -- will try to intersperse below. Or maybe I'll just top post them here: Surprise 2: Another surprising thing to me (with the evolution of the

Re: SSH resources, specifically on certificates (certificate authentication)

On Fri, Jul 15, 2022 at 12:32:35PM -, Curt wrote: > On 2022-07-14, Dan Ritter wrote: > > > > If you've got a very large organization, you may want to support > > the infrastructure to generate new SSH certs for people daily, > > with expiration dates of 24 hours. Then you need to make sure > >

Re: SSH resources, specifically on certificates (certificate authentication)

On 2022-07-14, Dan Ritter wrote: > > If you've got a very large organization, you may want to support > the infrastructure to generate new SSH certs for people daily, > with expiration dates of 24 hours. Then you need to make sure > that mechanism is working perfectly and has appropriate > redunda

Re: SSH resources, specifically on certificates (certificate authentication)

to...@tuxteam.de wrote: > See, asymmetrical encryption (e.g. RSA, Elliptic Curve) is far too expensive > to use on bulk data, so it typically is used to encrypt a key (generated on > the spot), called "session key". The latter is used to symmetrically (e.g. > AES) encrypt the bulk data. You use th

Re: SSH resources, specifically on certificates (certificate authentication)

On Thu, Jul 14, 2022 at 08:01:19PM -0400, rhkra...@gmail.com wrote: [...] > I'll probably start with a post to describe one of the most surprising things > I learned about ssh so far -- to jump ahead and spoil it, it turns out that > public key encryption is not used for the exchange of the rea

Re: SSH resources, specifically on certificates (certificate authentication)

On Thu 14 Jul 2022 at 10:00:29 (-0400), Frank Pikelner wrote: > SSH certificate authentication is not complicated and has many > advantages. Some organizations use SSH certificates to provide limited > access for admins to servers. In my opinion using SSH certificates is > preferred to just using

Re: SSH resources, specifically on certificates (certificate authentication)

Intentionally top posting. Thanks for the reply! I'm thinking of two or three paths forward -- one is to give up on this, but I've invested a lot of calandar days (and non-"spare" manhours so far, so I don't want to do that. Another is to make another pass through some of what I consider the b

Re: SSH resources, specifically on certificates (certificate authentication)

On 7/14/22 09:59, rhkra...@gmail.com wrote: On Wednesday, July 13, 2022 07:58:14 PM David Christensen wrote: Buy and read "TLS Mastery" by Lucas: https://mwl.io/nonfiction/networking#tls Replying off list intentionally: AFAIK, TLS doesn't have much, if anything, to do with ssh certificates.

Re: SSH resources, specifically on certificates (certificate authentication)

On Wednesday, July 13, 2022 07:09:33 PM Jeremy Ardley wrote: > I understand that certificate based SSH authentication has problems with > overall security management on a network. Password only has similar > problems. I'm not sure it has any more problems than ssh public key authentication, maybe

Re: SSH resources, specifically on certificates (certificate authentication)

On Thu, Jul 14, 2022 at 08:55:34AM -0400, rhkra...@gmail.com wrote: > > > dsr, Thanks for the reply! > > Like I said, I think I went down a rabbit hole, and I wish I had realized > that > before I went there. As someone else said, I agree that the certificate way is quite a bit more complex t

Re: SSH resources, specifically on certificates (certificate authentication)

On Thu, Jul 14, 2022 at 8:56 AM wrote: > > > > dsr, Thanks for the reply! > > Like I said, I think I went down a rabbit hole, and I wish I had realized that > before I went there. > > I've invested quite a few calendar days (and "spare" manhours) in trying to > figure this out, so I'm not quite r

Re: SSH resources, specifically on certificates (certificate authentication)

dsr, Thanks for the reply! Like I said, I think I went down a rabbit hole, and I wish I had realized that before I went there. I've invested quite a few calendar days (and "spare" manhours) in trying to figure this out, so I'm not quite ready to give up. I do have some ideas (an idea) for an

Re: SSH resources, specifically on certificates (certificate authentication)

Dan Purgert wrote: > On Jul 13, 2022, David Wright wrote: > > On Wed 13 Jul 2022 at 18:40:18 (-0400), Dan Purgert wrote: > > > On Jul 13, 2022, rhkra...@gmail.com wrote: > > > > I seem to have gone down a rabbit hole. > > > > > > > > I want(ed?) to set up ssh on my LAN using certificate authentic

Re: SSH resources, specifically on certificates (certificate authentication)

On Jul 13, 2022, David Wright wrote: > On Wed 13 Jul 2022 at 18:40:18 (-0400), Dan Purgert wrote: > > On Jul 13, 2022, rhkra...@gmail.com wrote: > > > I seem to have gone down a rabbit hole. > > > > > > I want(ed?) to set up ssh on my LAN using certificate authentication, and > > > am > > > havi

Re: SSH resources, specifically on certificates (certificate authentication)

On 7/13/22 13:11, rhkra...@gmail.com wrote: I seem to have gone down a rabbit hole. I want(ed?) to set up ssh on my LAN using certificate authentication, and am having a lot of trouble finding the information I need / would like to have. I won't go into much detail now, but I didn't realize how

Re: SSH resources, specifically on certificates (certificate authentication)

On Wed 13 Jul 2022 at 18:40:18 (-0400), Dan Purgert wrote: > On Jul 13, 2022, rhkra...@gmail.com wrote: > > I seem to have gone down a rabbit hole. > > > > I want(ed?) to set up ssh on my LAN using certificate authentication, and > > am > > having a lot of trouble finding the information I need

Re: SSH resources, specifically on certificates (certificate authentication)

On 14/7/22 6:40 am, Dan Purgert wrote: On Jul 13, 2022, rhkra...@gmail.com wrote: I seem to have gone down a rabbit hole. I want(ed?) to set up ssh on my LAN using certificate authentication, and am having a lot of trouble finding the information I need / would like to have. Which is what, ex

Re: SSH resources, specifically on certificates (certificate authentication)

On Jul 13, 2022, rhkra...@gmail.com wrote: > I seem to have gone down a rabbit hole. > > I want(ed?) to set up ssh on my LAN using certificate authentication, and am > having a lot of trouble finding the information I need / would like to have. Which is what, exactly? Other than the "active mai

Fwd: Re: SSH timeout logoff don't work!

Loïc Grenié thanks!! Work well! I was trying to do a script exactly like your script! Thanks and again thanks!  --- Begin Message --- Hi, Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit : > Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc > of my user: TMOUT=600

Re: SSH timeout logoff don't work!

Hi, Le mar. 21 juin 2022 à 10:14, Conti Stefano a écrit : > Hello! In My Debian 11 SSH timeout logoff not work! I must put in .bashrc > of my user: TMOUT=600 to loogut after 10 minutes. Work, of course, but > close all bash terminal! > > This is my sshd_config with info for timeout: > > TCPK

Re: : SSH timeout logoff don't work!

Le mardi 21 juin 2022 à 23:40 +0200, didier gaumet a écrit : [...] > - if you want to restrict the time of ssh connection and are in > position to modify the ssh command they use (an alias in their bashrc > for example?), perhaps you can try to force the ssh -o option with > the ConnectTimeout par

Re: : SSH timeout logoff don't work!

Le mardi 21 juin 2022 à 12:52 +0200, Conti Stefano a écrit : > If I put ClientAliveCountMax 1 with ClientAliveInterval 600 timeout > is 1200 inmy Debian 11. I have try all combinations but at the moment > nothing happen; session stay alive! There is somethng but i don't > understand what keep al

Re: SSH timeout logoff don't work!

On Tue, Jun 21, 2022 at 6:04 AM Greg Wooledge wrote: > On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote: > > Hello! In My Debian 11 SSH timeout logoff not work! I must put in > > .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of > > course, but close all bash termina

Re: SSH timeout logoff don't work!

On Tue, Jun 21, 2022 at 02:02:38PM +0200, Conti Stefano wrote: > Excuse me but i sure you that i use this practice from many years and > always work in the past. I've a other distro, an "old" Debian 9 and a > Centos 7 with SSH version 7.4p1 and i'm sure work all well because i > put  ClientAliveInt

Re: SSH timeout logoff don't work!

On Tue, Jun 21, 2022 at 10:05:43AM +0200, Conti Stefano wrote: > Hello! In My Debian 11 SSH timeout logoff not work! I must put in > .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of > course, but close all bash terminal! > > This is my sshd_config with info for timeout:  > > TCP

Re: SSH timeout logoff don't work!

Le mardi 21 juin 2022 à 10:05 +0200, Conti Stefano a écrit : > Hello! In My Debian 11 SSH timeout logoff not work! I must put in > .bashrc of my user: TMOUT=600 to loogut after 10 minutes. Work, of > course, but close all bash terminal! > > This is my sshd_config with info for timeout:  > > TC

Re: ssh-agent: I want to start using on all my remote hosts

On Sat, Jun 4, 2022 at 13:52 john doe wrote: > On 6/4/2022 8:28 PM, Tom Browder wrote: > > On Sat, Jun 4, 2022 at 10:02 Andy Smith wrote: > > ... > > > > You seem to be very reboot-happy. I recommend understanding the > >> impact of the changes you will make instead of assuming you need to > >>

Re: ssh-agent: I want to start using on all my remote hosts

On 6/4/2022 8:28 PM, Tom Browder wrote: On Sat, Jun 4, 2022 at 10:02 Andy Smith wrote: ... You seem to be very reboot-happy. I recommend understanding the impact of the changes you will make instead of assuming you need to reboot to make them effective. Andy. I know I'm "reboot happy," but

Re: ssh-agent: I want to start using on all my remote hosts

On Sat, Jun 4, 2022 at 10:02 Andy Smith wrote: ... You seem to be very reboot-happy. I recommend understanding the > impact of the changes you will make instead of assuming you need to > reboot to make them effective. Andy. I know I'm "reboot happy," but it's lazyness (no other users at the mom

Re: ssh-agent: I want to start using on all my remote hosts

Hello, On Fri, Jun 03, 2022 at 09:43:53AM -0500, Tom Browder wrote: > 1. Will starting the ssh-agent service interfere with my current ssh login > (using keys with NO passhrase). It only matters at the point of authentication, so existing SSH sessions will not be affected. > 2. Is there anything

Re: ssh-agent: I want to start using on all my remote hosts

Hello, On Fri, Jun 03, 2022 at 09:52:26AM -0500, Tom Browder wrote: > And edit file /etc/ssh/ssh_config to change > > # ForwardAgent no > > to > > ForwardAgent yes > > Then reboot. This is a config file for the ssh client, i.e. the "ssh" command. As such it's read every time you run s

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

Ahh, thanks Greg, I can now see those missing parts of the article -- it was NoScript, but, seeing most of the graphics in the article, somehow NoScript didn't come to mind as the cause of the problem. On Friday, June 03, 2022 02:29:45 PM Greg Wooledge wrote: > On Fri, Jun 03, 2022 at 01:16:45

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 3, 2022 at 13:46 wrote: > On Friday, June 03, 2022 02:16:45 PM Tom Browder wrote: > > I briefly looked at the article and didn't notice anything missing. Maybe > > if you could take some screen shots in those areas we could help. > > Thanks for the reply, and thanks, I'll do that. > >

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On 6/3/22 08:46, rhkra...@gmail.com wrote: On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: I have been using ssh for logging in to my remote hosts for many years, but I have NOT been using ssh-agent. I'm intentionally not addressing your specific questions. For me, your post is rather

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 03, 2022 at 01:16:45PM -0500, Tom Browder wrote: > On Fri, Jun 3, 2022 at 10:46 wrote: > > > > > > One problem with that article is that it se

Re: ssh-agent: I want to start using on all my remote hosts

On 6/3/22 07:43, Tom Browder wrote: I have been using ssh for logging in to my remote hosts for many years, but I have NOT been using ssh-agent. I have checked all those hosts looking for the env var SSH_AGENT_SOCK which one website says should be defined if the ssh-agent process is running, but

Re: How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Fri, Jun 3, 2022 at 10:46 wrote: > On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: > > I have been using ssh for logging in to my remote hosts for many years, > but > > I have NOT been using ssh-agent. > > I'm intentionally not addressing your specific questions. > > For me, your post

How about ssh certificates (was: Re: ssh-agent: I want to start using on all my remote hosts)

On Friday, June 03, 2022 10:43:53 AM Tom Browder wrote: > I have been using ssh for logging in to my remote hosts for many years, but > I have NOT been using ssh-agent. I'm intentionally not addressing your specific questions. For me, your post is rather timely, because I'm digging into ssh and w

Re: ssh-agent: I want to start using on all my remote hosts

On Fri, Jun 3, 2022 at 09:43 Tom Browder wrote: > I have been using ssh for logging in to my remote hosts for many years, > but I have NOT been using ssh-agent. > ... And edit file /etc/ssh/ssh_config to change # ForwardAgent no to ForwardAgent yes Then reboot. -Tom

Re: ssh -X and size of GUI elements (KDE/Qt)

Christian Britz wrote: > On 2022-02-15 17:26 UTC+0100, Dan Ritter wrote: > > It's probably a disagreement on screen dpi settings. Check your > > native setting and then replicate it on your headless server's > > KDE config? > > Wouldn't this mainly/exclusively affect the fonts? > I set dpi in bot

Re: ssh -X and size of GUI elements (KDE/Qt)

On 2022-02-15 17:26 UTC+0100, Dan Ritter wrote: > It's probably a disagreement on screen dpi settings. Check your > native setting and then replicate it on your headless server's > KDE config? Wouldn't this mainly/exclusively affect the fonts? I set dpi in both systemsettings5 tool explicitly to 9

Re: ssh -X and size of GUI elements (KDE/Qt)

Christian Britz wrote: > Hi, > > when I logon to my headless server via ssh -X, I can start graphical > applications and they are displayed on my local X server. > > The font size is excactly the same as on my dektop, but GUI elements > like buttons are somehow smaller in vertical size. It seems

Re: ssh access with all ports close.

On 12/10/2020 6:40 AM, latin...@vcn.bc.ca wrote: latincom writes: I am not able to access my server at home using ssh, but i can see in logs, that someone can access my home server! What, exactly, are you seeing? Copy and paste examples. -- John Hasler jhas...@newsguy.com Elmwood, WI USA D

Re: ssh tunnelling testing [solved]

On Mi, 09 dec 20, 10:58:48, Gary Dale wrote: > > My ISP has confirmed this seems to be a generic issue with that > modem/router. While I suspect that a firmware update could fix it, I can't > find any way to upgrade the firmware, which is another good reason for > having an inner and outer network

Re: ssh access with all ports close.

> latincom writes: >> I am not able to access my server at home using ssh, but i can see in >> logs, that someone can access my home server! > > What, exactly, are you seeing? Copy and paste examples. > -- > John Hasler > jhas...@newsguy.com > Elmwood, WI USA > Dec 9 20:48:58 xxx sshd[4945]: Fai

Re: ssh access with all ports close.

On 2020-12-09 16:33, latin...@vcn.bc.ca wrote: I had a Buster server at home, but the owner of the house close all ports in the router, i can not access it anymore; i rented a server without root access, and transfer the server. There are many vendors who can rent a Debian virtual private serv

Re: ssh access with all ports close.

latincom writes: > I am not able to access my server at home using ssh, but i can see in > logs, that someone can access my home server! What, exactly, are you seeing? Copy and paste examples. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: ssh tunnelling testing [solved]

On 2020-12-07 16:02, Gary Dale wrote: On 2020-12-07 14:23, john doe wrote: On 12/7/2020 8:11 PM, Gary Dale wrote: On 2020-12-07 14:03, john doe wrote: On 12/7/2020 7:54 PM, Gary Dale wrote: On 2020-12-07 13:24, john doe wrote: On 12/7/2020 6:38 PM, Gary Dale wrote: (actually through the

Re: ssh tunnelling testing [solved]

On Lu, 07 dec 20, 14:11:01, Gary Dale wrote: > > The thing is the forwarding setup is the same for port 22 as it is for port > 80. I know that the port 80 forwarding is working so why isn't the port 22 > forwarding? > > I still don't know the answer to that one, but when I changed the external >

Re: ssh tunnelling testing

On 2020-12-07 13:55, der.hans wrote: Am 07. Dec, 2020 schwätzte Gary Dale so: moin moin, First off, try one or more -v to your ssh command to get more verbosity. The -v will show you the step in building the connection that failed. Also, try -G to see what configuration will be used without a

Re: ssh tunnelling testing [solved]

On 2020-12-07 14:23, john doe wrote: On 12/7/2020 8:11 PM, Gary Dale wrote: On 2020-12-07 14:03, john doe wrote: On 12/7/2020 7:54 PM, Gary Dale wrote: On 2020-12-07 13:24, john doe wrote: On 12/7/2020 6:38 PM, Gary Dale wrote: (actually through the /etc/hosts file using the server's nam

Re: ssh tunnelling testing [solved]

On 2020-12-07 14:03, john doe wrote: On 12/7/2020 7:54 PM, Gary Dale wrote: On 2020-12-07 13:24, john doe wrote: On 12/7/2020 6:38 PM, Gary Dale wrote: (actually through the /etc/hosts file using the server's name). I've set up port forwarding on both my routers (I have an inner network

  1   2   3   4   5   6   7   8   9   10   >