SSH account and password of core miner
Publish: 2021-05-02 05:45:18
1. Use SecureCRT to create a new SSH2 connection. The host name is your routing IP, port 2232, and the user name and password are your login routing account and password
please accept it as a satisfactory answer.
please accept it as a satisfactory answer.
2. SSH
is a framework of java development, which is composed of struts
spring
hibernate. He's just a frame. Used to do java
Web page class. Just can make landing page with him, provided account number and password. It's not something that
can do
if you need other questions, you can ask me
I'm glad to answer for you
good luck
is a framework of java development, which is composed of struts
spring
hibernate. He's just a frame. Used to do java
Web page class. Just can make landing page with him, provided account number and password. It's not something that
can do
if you need other questions, you can ask me
I'm glad to answer for you
good luck
3. 1. SSH authentication should not use the native method of tortoise, but the openssh method of GIT, which is very important. If you have specified the method of tortoise, modify the environment variable GIT_ SSH is OK, of course, reload is also a way
2. Git Bash is used for configuration
3. By executing
SSH keygen - t RSA
to create a private key, the file is saved in ~ /. SSH / ID_ Just go to RSA. It's good to run all the way back
4. Create SSH config file, such as:
VI ~ /. SSH / config
the content is:
host GitHub. Com
proxycommand ~ /. SSH / SSH HTTPS tunnel% H% P ~ /. SSH / proxyauth
port 443
hostname SSH. GitHub. Com
here you can see a ~ /. SSH / proxyauth at the end of the second line. This is because our company's agent has a password, so we need to generate another proxyauth file. The format is: username:password . If you don't, just remove it
at the same time, the purpose of hostname is to create an alias. In fact, we use ssh.github.com, but we usually use it [email protected] , so in order not to modify it, create an alias
5. Download SSH HTTPS tunnel from http://zwitterion.org/software/ssh-https-tunnel/ssh-https-tunnel , and save it to your git ~ /. SSH directory
at the same time, to open this file for modification,
my $proxy = & quot& quot;;< br />my $proxy_ port = ;
change to your actual proxy address
6. Using SSH [email protected] To test
hi limodou! You' Ve successfully authenticated, but GitHub does not provide shell
access.
connection to ssh.github.com closed.
one of the difficulties here is the configuration of proxy authentication, which I found on the Internet. And GIT_ SSH settings. If tortoise SVN is installed and SSH client is selected, the proxy settings of SSH may pass, but git will make an error when using it, because it will look at the environment variables.
2. Git Bash is used for configuration
3. By executing
SSH keygen - t RSA
to create a private key, the file is saved in ~ /. SSH / ID_ Just go to RSA. It's good to run all the way back
4. Create SSH config file, such as:
VI ~ /. SSH / config
the content is:
host GitHub. Com
proxycommand ~ /. SSH / SSH HTTPS tunnel% H% P ~ /. SSH / proxyauth
port 443
hostname SSH. GitHub. Com
here you can see a ~ /. SSH / proxyauth at the end of the second line. This is because our company's agent has a password, so we need to generate another proxyauth file. The format is: username:password . If you don't, just remove it
at the same time, the purpose of hostname is to create an alias. In fact, we use ssh.github.com, but we usually use it [email protected] , so in order not to modify it, create an alias
5. Download SSH HTTPS tunnel from http://zwitterion.org/software/ssh-https-tunnel/ssh-https-tunnel , and save it to your git ~ /. SSH directory
at the same time, to open this file for modification,
my $proxy = & quot& quot;;< br />my $proxy_ port = ;
change to your actual proxy address
6. Using SSH [email protected] To test
hi limodou! You' Ve successfully authenticated, but GitHub does not provide shell
access.
connection to ssh.github.com closed.
one of the difficulties here is the configuration of proxy authentication, which I found on the Internet. And GIT_ SSH settings. If tortoise SVN is installed and SSH client is selected, the proxy settings of SSH may pass, but git will make an error when using it, because it will look at the environment variables.
4. Web port: install IIS service from 2K3 installation disk, and it will be opened naturally.
the web port will be opened ssh:2K3 There is no such thing in itself. Linux uses this by default, which is safe, stable and reliable. However, it can be implemented with third-party software. It is recommended that you use SSH tectia server Shh to do things made by your own family. Financial units all use this, and there is no need to talk nonsense about security.
DB? You mean the database port? Oracle port number is 1521, MySQL port number is 3306, and SQL server port number is 1433. Of course, this is only the default and can be changed.
Telnet, since you have SSH, why do you open this? It's very unsafe, The user name and password are all transmitted in clear text. It's easy to crack them. You can't set up a separate account. Only telnet is allowed, and IPSec has a trusted IP. It's not troublesome enough.
under CMD, netstat - an can see whether the port is open or not.
it's the same. IIS with less than 2K3 is 6.0, while XP can only support 5.1
the web port will be opened ssh:2K3 There is no such thing in itself. Linux uses this by default, which is safe, stable and reliable. However, it can be implemented with third-party software. It is recommended that you use SSH tectia server Shh to do things made by your own family. Financial units all use this, and there is no need to talk nonsense about security.
DB? You mean the database port? Oracle port number is 1521, MySQL port number is 3306, and SQL server port number is 1433. Of course, this is only the default and can be changed.
Telnet, since you have SSH, why do you open this? It's very unsafe, The user name and password are all transmitted in clear text. It's easy to crack them. You can't set up a separate account. Only telnet is allowed, and IPSec has a trusted IP. It's not troublesome enough.
under CMD, netstat - an can see whether the port is open or not.
it's the same. IIS with less than 2K3 is 6.0, while XP can only support 5.1
5. On my network space to see it, now more free VPN, general VPN and SSH one. However, the speed is fast and stable, it depends on you. You can sign up for free in two minutes. There are several sections in the space. The speed of personal trial is very good. FB, twitter and play games are awesome. Hope to help you.
6. Just install ssh server software on Linux
the following is the software name of ssh server:
openssh server
the following is the software name of ssh server:
openssh server
7. However, every time I need a password, and I need manual reconnection when I break the line. It's really a very troublesome thing. Referring to a series of information on the Internet, I assembled my own scheme, which can automatically link when I start up, save the password input, and automatically reconnect when I break the line
first of all, you need to create a key to save the password. On your command line, enter:
Local: ~ yourname $SSH keygen - t RSA
then press enter in turn to enter the password, which has nothing to do with the SSH account password
the whole interface looks similar:
Local: ~ yourname $SSH keygen - t RSA
generating public / private RSA key pair.
Enter file in which to save the key (/ U / Kim /. SSH / ID)_ RSA): [Enter]
enter password (empty for no password): [first password]
Enter same password again: [second password]
your identification has been saved in / U / Kim /. SSH / ID_ rsa.
Your public key has been saved in /u/kim/.ssh/id_ RSA. Pub.
then transfer the key file to your SSH account:
Local: ~ yourname $Cd ~ /. SSH
Local: ~ yourname $CP ID_ rsa.pub authorized_ keys
local:~ yourname$ scp -p ~/.ssh/authorized_ keys hrothgar:.ssh/
in the last step, you will be prompted to enter the password of the SSH account, not the password of the key you just created
if there is an error in the last step, it is usually e to the problem of remote permissions
you need to log in to the remote machine as root, create a relevant directory for the SSH account, and set permissions:
set the home directory for the SSH account:
first of all, you need to create a key to save the password. On your command line, enter:
Local: ~ yourname $SSH keygen - t RSA
then press enter in turn to enter the password, which has nothing to do with the SSH account password
the whole interface looks similar:
Local: ~ yourname $SSH keygen - t RSA
generating public / private RSA key pair.
Enter file in which to save the key (/ U / Kim /. SSH / ID)_ RSA): [Enter]
enter password (empty for no password): [first password]
Enter same password again: [second password]
your identification has been saved in / U / Kim /. SSH / ID_ rsa.
Your public key has been saved in /u/kim/.ssh/id_ RSA. Pub.
then transfer the key file to your SSH account:
Local: ~ yourname $Cd ~ /. SSH
Local: ~ yourname $CP ID_ rsa.pub authorized_ keys
local:~ yourname$ scp -p ~/.ssh/authorized_ keys hrothgar:.ssh/
in the last step, you will be prompted to enter the password of the SSH account, not the password of the key you just created
if there is an error in the last step, it is usually e to the problem of remote permissions
you need to log in to the remote machine as root, create a relevant directory for the SSH account, and set permissions:
set the home directory for the SSH account:
8. Check your Java. If your Java is prompted when installing SDM, and then automatically download the installed Java 6, it will not start normally. You need to find and download j2sdk-1 again_ 4_ 2_ 19-windows-i586-p Next, uninstall Java 6 and install j2sdk-1_ 4_ 2_ 19-windows-i586-p or 1.5. This should solve the problem.
9. Take a look at this
I won't say more
I've been using it for a long time
I'm very stable
I won't say more
I've been using it for a long time
I'm very stable
Hot content