Bitcoin Forum
June 22, 2024, 01:14:46 AM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Need a little help with SSH  (Read 792 times)
BitCoiner2012 (OP)
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250



View Profile
August 11, 2013, 06:45:14 PM
 #1

Using Bitvise SSH. Set up server on primary computer, can connect with the client computer, but even though I put the correct username in it asks for a password (there was none to start), so I tried making one, still rejects the connection.

So I made a new Windows account and set it up with specific login and password like and other Windows "user" account, and tried that - bingo. Why can't I log into my primary account? The secondary user accoutns odn't seem to be capable of accessing the drivers and other things my server needs to mine. So I can't remotely control GPU, just CPU. Any thoughts on this? I tried giving admin priv to the new account and that doesn't change the driver issue. I can access files it seems (if I recall correctly), but that's it.


BTC Long.
bitcoinreactor
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
August 11, 2013, 08:30:36 PM
 #2

i'm not familiar with bitwise ssh, but it could be configured to refuse remote administrators logins.
This is a common option on sshd daemons, main idea behind that was (not only) to try to reduce chances of successful brute-force, where username is already known ("root" on many unix systems)

if bitwise ssh comes with configuration files, try to find such an option ("allow remote root login" or something like that). such a config file is often named "sshd_config" on other ssh servers.

BTC: 17CHqn3XE3Waf7Qfkm9p2MQE1VgB8gVbG4
rmyadsk
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
August 12, 2013, 07:25:50 PM
 #3

If it's a standard OpenSSH server, the configuration file is /etc/ssh/sshd_config. Search that file for the variable "PermitRootLogin" under the "Authentication:" section. The allows variables are: yes, no, without-password. Without-password is used when you have a key-based setup involved...which is a good idea for some systems.

On the client box:

ssh-keygen -t rsa
(accept defaults)
sftp/rsync/etc. the file ~/.ssh/id_rsa.pub to the server as /root/.ssh/authorized_keys.

On the server box:

Change sshd_config as desired
/etc/init.d/sshd (or equivalent) restart

Then attempt an SSH session from client to server. If the keys are probably in place you will not be prompted for a password.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!