Re: ssh doesn't work.

On 10/12/16 22:01, Joe wrote: > On Sat, 10 Dec 2016 13:54:56 +0900 > EenyMeenyMinyMoa wrote: > > >> I see. >> I thought the meaning of "bugger" as "wreck". > > > Pretty much any rude word, together with 'all', means 'nothing' in an > emphatic but not polite way, as in 'sod all' and 'f*** all'

Re: ssh doesn't work.

On Sat, 10 Dec 2016 13:54:56 +0900 EenyMeenyMinyMoa wrote: > I see. > I thought the meaning of "bugger" as "wreck". Pretty much any rude word, together with 'all', means 'nothing' in an emphatic but not polite way, as in 'sod all' and 'f*** all'. -- Joe

Re: ssh doesn't work.

2016-12-08 19:04 GMT+09:00 Lisi Reisz : > On Thursday 08 December 2016 04:19:00 EenyMeenyMinyMoa wrote: >> Hi, >> >> 2016-12-08 5:25 GMT+09:00 Brian : >>> Random script kiddy attacks are of absolutely no consequence. Annoying >>> perhaps, but no threat whatsoever. In terms of security, changing the

Re: ssh doesn't work.

Hi. On Thu, 8 Dec 2016 15:37:45 + Darac Marjal wrote: > On Thu, Dec 08, 2016 at 01:18:38AM +0300, Reco wrote: > >On Wed, 7 Dec 2016 15:54:46 -0500 > >Henning Follmann wrote: > > > >> On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: > >> > Hi. > >> > > >> > On Wed, 7 Dec 2016 2

Re: ssh doesn't work.

On Thu, Dec 08, 2016 at 01:18:38AM +0300, Reco wrote: On Wed, 7 Dec 2016 15:54:46 -0500 Henning Follmann wrote: On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: >Hi. > > On Wed, 7 Dec 2016 21:14:51 +0200 > Antti Talsta wrote: > > > On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Woole

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 11:35:36PM -0800, emetib wrote: > > > Sorry, you have to stop this. Now! > > > > I thought that to be a basic manner as the original questioner. > > Why do you think isn't that good? > > Everybody else, how do you think? > > he's saying don't change 4 things at once. >

Re: ssh doesn't work.

On Thursday 08 December 2016 04:19:00 EenyMeenyMinyMoa wrote: > Hi, > > 2016-12-08 5:25 GMT+09:00 Brian : > > Random script kiddy attacks are of absolutely no consequence. Annoying > > perhaps, but no threat whatsoever. In terms of security, changing the > > port number for ssh does bugger all. > >

Re: ssh doesn't work.

> > Sorry, you have to stop this. Now! > > I thought that to be a basic manner as the original questioner. > Why do you think isn't that good? > Everybody else, how do you think? he's saying don't change 4 things at once. change one, test change another, test that's how you trouble shoot

Re: ssh doesn't work.

2016-12-08 1:07 GMT+09:00 Henning Follmann : >> > Thank you for your reply, Andy. >> > > Please be so nice and trim your post to be meaningful and concise. Don't > just slapp something on the top. 2016-12-08 3:23 GMT+09:00 Henning Follmann : >> Thank you for the quick response, Henning. >> > > Sor

Re: ssh doesn't work.

Hi, 2016-12-08 5:25 GMT+09:00 Brian : > Random script kiddy attacks are of absolutely no consequence. Annoying > perhaps, but no threat whatsoever. In terms of security, changing the > port number for ssh does bugger all. What security risk can changing the port number for ssh cause? Cheers, Een

Re: ssh doesn't work.

Hi, 2016-12-08 2:52 GMT+09:00 Greg Wooledge : > On Thu, Dec 08, 2016 at 02:37:09AM +0900, EenyMeenyMinyMoa wrote: >> $ ls -ls /home/testac/.ssh >> total 12 >> 4 -rwx-- 1 u1 u1 776 Dec 8 11:05 authorized_keys >> 4 -rw-r--r-- 1 u1 u1 388 Dec 6 11:57 id_rsa_test.pub >> 4 -rwx-- 1 u1 u1 444

Re: ssh doesn't work.

On Wed, 7 Dec 2016 15:54:46 -0500 Henning Follmann wrote: > On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: > > Hi. > > > > On Wed, 7 Dec 2016 21:14:51 +0200 > > Antti Talsta wrote: > > > > > On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Wooledge wrote: > > > > > > > Changing the p

Re: ssh doesn't work.

On Wed, 7 Dec 2016 22:46:16 +0200 Antti Talsta wrote: > On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: > > > How fail2ban can help against an army of bots trying one single > > password per bot? > > It doesn't. My point exactly. Using sshd on non-standard port does, as bots are too stup

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: > How fail2ban can help against an army of bots trying one single > password per bot? It doesn't. -- Antti Talsta signature.asc Description: Digital signature

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 11:28:53PM +0300, Reco wrote: > Hi. > > On Wed, 7 Dec 2016 21:14:51 +0200 > Antti Talsta wrote: > > > On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Wooledge wrote: > > > > > Changing the port at least decreases the number of brute force attacks > > > against you,

Re: ssh doesn't work.

Hi. On Wed, 7 Dec 2016 21:14:51 +0200 Antti Talsta wrote: > On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Wooledge wrote: > > > Changing the port at least decreases the number of brute force attacks > > against you, which saves resources (bandwidth, CPU) that are otherwise > > wasted b

Re: ssh doesn't work.

On Wed 07 Dec 2016 at 13:49:34 -0500, Greg Wooledge wrote: > On Wed, Dec 07, 2016 at 01:23:23PM -0500, Henning Follmann wrote: > > Also changing the port to a nonstandard port is not a safety measure. Not a > > reasonable at least. Unless there is some sane reason (like the network > > operator pr

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Wooledge wrote: > Changing the port at least decreases the number of brute force attacks > against you, which saves resources (bandwidth, CPU) that are otherwise > wasted by the attackers. How about fail2ban for that? -- Antti Talsta signature.as

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 01:49:34PM -0500, Greg Wooledge wrote: > On Wed, Dec 07, 2016 at 01:23:23PM -0500, Henning Follmann wrote: > > Also changing the port to a nonstandard port is not a safety measure. Not a > > reasonable at least. Unless there is some sane reason (like the network > > operator

Re: ssh doesn't work.

On Wednesday, December 7, 2016 at 11:40:04 AM UTC-6, EenyMeenyMinyMoa wrote: > > $ ls -ls /home/testac/.ssh > total 12 > 4 -rwx-- 1 u1 u1 776 Dec  8 11:05 authorized_keys > 4 -rw-r--r-- 1 u1 u1 388 Dec  6 11:57 id_rsa_test.pub > 4 -rwx-- 1 u1 u1 444 Dec  6 20:46 known_hosts > check the pe

Re: ssh doesn't work.

On Wed, Dec 07, 2016 at 01:23:23PM -0500, Henning Follmann wrote: > Also changing the port to a nonstandard port is not a safety measure. Not a > reasonable at least. Unless there is some sane reason (like the network > operator prevents using port 22) keep it! I disagree with this. Changing the

Re: ssh doesn't work.

On Thu, Dec 08, 2016 at 02:37:09AM +0900, EenyMeenyMinyMoa wrote: > Thank you for the quick response, Henning. > Sorry, you have to stop this. Now! I think it is great that you want to learn how to use ssh. It is an important skill for admins and users. However you are approaching it the wrong way

Re: ssh doesn't work.

On Thu, Dec 08, 2016 at 02:37:09AM +0900, EenyMeenyMinyMoa wrote: > $ ls -ls /home/testac/.ssh > total 12 > 4 -rwx-- 1 u1 u1 776 Dec 8 11:05 authorized_keys > 4 -rw-r--r-- 1 u1 u1 388 Dec 6 11:57 id_rsa_test.pub > 4 -rwx-- 1 u1 u1 444 Dec 6 20:46 known_hosts Which machine is that -- the

Re: ssh doesn't work.

Thank you for the quick response, Henning. 2016-12-08 1:07 GMT+09:00 Henning Follmann : > Please revert to your original configs. Key login works be default and > requires no change. By reverting to my original configs : PasswordAuthentication yes I was able to ssh. $ ssh -p testac@192.168.

Re: ssh doesn't work.

On Thu, Dec 08, 2016 at 12:27:53AM +0900, EenyMeenyMinyMoa wrote: > Thank you for your reply, Andy. > Please be so nice and trim your post to be meaningful and concise. Don't just slapp something on the top. > ufw was enabled on the server machine. > Because I don't have enough knoledge about ip

Re: ssh doesn't work.

Thank you for your reply, Andy. ufw was enabled on the server machine. Because I don't have enough knoledge about iptables, I did $ sudo ufw allow proto tcp from 192.168.0.3 to any port on the server machine. Then I successfully connected from the client machine by ssh. And next I want to do

Re: ssh doesn't work.

Hi, On Tue, Dec 06, 2016 at 01:33:07PM +0900, EenyMeenyMinyMoa wrote: > But when I execute either of these commands > $ ssh -p testac@192.168.0.5 > $ ssh -p -l testac -i ~/.ssh/id_rsa_test 192.168.0.5 > , the terminal doesn't resopnd for minutes and finally gives this message. > ssh: con

ssh doesn't work.

Hi. I'm using jessie and trying to connect from one jessie machine to another jessie machine by ssh. I succeeded the following commands at the server machine. $ ssh -p testac@localhost $ ssh -p -l testac -i ~/.ssh/id_rsa_test localhost But when I execute either of these commands $ ssh -p

Re: SSH doesn't work with RSA keys

On Wed, 03 Jan 2007 17:50:40 -0300, Alejandro wrote > People, I have generated the key pair RSA from my root linux's user and > then I copy my RSA public key to /root/.ssh/authorized_keys from the > linux ssh server. After that I edit the sshd_config file and put permit > rootlogin no and the corre

Re: SSH doesn't work with RSA keys

Hi again, * on Jan 04, 2007, I wrote: > * on Jan 03, 2007, Alejandro wrote: > > >On Wed, Jan 03, 2007 at 05:50:40PM -0300, Alejandro wrote: > > > > > >>People, I have generated the key pair RSA from my root linux's user and > > >>then I copy my RSA public key to /root/.ssh/authorized_keys from t

Re: SSH doesn't work with RSA keys

Hi, * on Jan 03, 2007, Alejandro wrote: > >On Wed, Jan 03, 2007 at 05:50:40PM -0300, Alejandro wrote: > > > >>People, I have generated the key pair RSA from my root linux's user and > >>then I copy my RSA public key to /root/.ssh/authorized_keys from the > >>linux ssh server. After that I edit t

Re: SSH doesn't work with RSA keys

On Wed, Jan 03, 2007 at 10:27:36PM -0300, Alejandro wrote: > 1) What are the lines I should setup in > /etc/ssh/sshd_config from the server side Just > *AuthorizedKeysFile %h/.ssh/authorized_keys* or what else > ??? You shouldn't need to put anything. The sshd server in Debian will assume a d

Re: SSH doesn't work with RSA keys

On Wed, Jan 03, 2007 at 10:27:36PM -0300, Alejandro wrote: > > 2) Some people say if I use SSH version 2, I have to use an > *authorized_keys2* file instead of an *authorized_keys* file...is it OK > ??? > This is only true for the ssh.com proprietary ssh server. The openssh server does not requ

Re: SSH doesn't work with RSA keys

Andrew M.A. Cater wrote: On Wed, Jan 03, 2007 at 05:50:40PM -0300, Alejandro wrote: People, I have generated the key pair RSA from my root linux's user and then I copy my RSA public key to /root/.ssh/authorized_keys from the linux ssh server. After that I edit the sshd_config file and put per

Re: SSH doesn't work with RSA keys

On Wed, Jan 03, 2007 at 10:02:30PM +, Andrew M.A. Cater wrote: > On Wed, Jan 03, 2007 at 05:50:40PM -0300, Alejandro wrote: > > People, I have generated the key pair RSA from my root linux's user and > > then I copy my RSA public key to /root/.ssh/authorized_keys from the > > linux ssh server.

Re: SSH doesn't work with RSA keys

On Wed, Jan 03, 2007 at 05:50:40PM -0300, Alejandro wrote: > People, I have generated the key pair RSA from my root linux's user and > then I copy my RSA public key to /root/.ssh/authorized_keys from the > linux ssh server. After that I edit the sshd_config file and put permit > rootlogin no and th

Re: SSH doesn't work with RSA keys

Alejandro: > > People, I have generated the key pair RSA from my root linux's user and > then I copy my RSA public key to /root/.ssh/authorized_keys from the > linux ssh server. Good. > After that I edit the sshd_config file and put permit > rootlogin no Erm, "to permit" means "to allow". You ju

SSH doesn't work with RSA keys

People, I have generated the key pair RSA from my root linux's user and then I copy my RSA public key to /root/.ssh/authorized_keys from the linux ssh server. After that I edit the sshd_config file and put permit rootlogin no and the correct path to the authorized_keys file. But when I execute from

Re: X-forwarding with ssh doesn't work

For people who care: I figured it out. It seems that since I upgraded to testing lo (loopback interface) isn't broadup at boottime. I don't understand why by the way. I have a line saying 'auto lo' in my /etc/network/interfaces. Further more I had to make a line 'ALL : 127.0.0.1' in my etc/

Re: X-forwarding with ssh doesn't work

Tim Dijkstra, 2001-Nov-16 23:52 +0100: > nate wrote: > > >Tim Dijkstra said: > > > > > >>debug1: Requesting pty. > >>debug1: Requesting X11 forwarding with authentication spoofing. > >>debug1: Requesting shell. > >>debug1: Entering interactive session. > >> > >>Is that enough? Does anybody with X-

Re: X-forwarding with ssh doesn't work

nate wrote: Tim Dijkstra said: debug1: Requesting pty. debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting shell. debug1: Entering interactive session. Is that enough? Does anybody with X-forw working correctly gets the same output? pretty much. how bout w

Re: X-forwarding with ssh doesn't work

Tim Dijkstra said: > debug1: Requesting pty. > debug1: Requesting X11 forwarding with authentication spoofing. > debug1: Requesting shell. > debug1: Entering interactive session. > > Is that enough? Does anybody with X-forw working correctly gets the > same output? pretty much. how bout when yo

X-forwarding with ssh doesn't work

Hi, I posted something about this problem a while ago, but I'am still stuck. The problem is that X-forwarding stopt working when I upgraded from potato to testing. I tried downgrading ssh and the x-server, but didn't help. I now even tried ssh-nonfree, still nothing. OK, what is supposed to