• Content Count

  • Avg. Content Per Day

  • Joined

  • Last visited

Community Reputation

0 Neutral

About h19server

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. h19server

    Netsparker Standard 5.9 Cracked

    Hi The PASS : Ph0nus-reign is not correct, it says the password is incorrect!!!! can u pls give the password ????
  2. h19server

    Facebook Automation Premium v6.9 + Crack

    Hi the file does not exist, can you please reupload the file pls ??
    1. dEEpEst


      What you need?

    2. h19server



      i need the password of this crypter: 


    3. dEEpEst
  3. downloaded this version : did everything according to the instructions, and i was able to login, but i got 2 few problems: 1 : after changing the default password i was not able to login again with the new pass also with the default pass, so i had to delete the server.php form the server and re-upload it again to login with the default pass but with no default pass change 2 : after getting some targets the TCP option is disabled at all and not working, is only the HTTP / IRC work for me. is the any solutions to resolve these 2 problems for how can i change the default pass without any pro and the functionality of the TCP to be active and usable ???
  4. h19server

    MobiHok 4.0 - Android RAT [Original Released]

    Hi i downloaded it but it crash when executing, .NetFramework 4.8 was installed on my pc, i then install remove and reinstalled the older version .NetFramework 4.0, but the same error. [HIDE][/HIDE]
  5. h19server

    Guide to secure SSH on Centos 7

    1. Overview SSH is the default secured remote management protocol for almost all of Linux distributions. SSH provides a confidentiality and integrity by data encryption and passwords are no longer sent in plain text over the network. Nevertheless, a default configuration of SSH can put the server in a security risk. That is why it is important to follow a few simple steps to harden an SSH server that can dramatically reduce the risk. 2. Prerequisites In this document, it is assumed that: You have already install RHEL/CentOS 7 Linux server up and running. 3. Disable Root Logins For security concern, it is not recommended to use root user to login via SSH over a network. The best approach is to use normal user to login to the server and use command sudo to perform the task that required root privilege. For more detail about Sudo, please check Linux Privilege Delegation With Sudoers. To disable root login via SSH, update file /etc/ssh/sshd_config and restart SSH service as the following. 4. Limit User Logins By default, all valid users on the system are able access the server. For security reason, we should limit to only certain users who really need to have SSH access to the server. Add the parameter AllowUsers followed by a space separated list of usernames to file /etc/ssh/sshd_config. In the following example, there are only two users, “john” and “sysadmin” who can remote SSH to the server. 5. Disable Protocol 1 Using protocol 1 of SSH is less secure. We should be disabled it and always use protocol 2 only instead. Edit file /etc/ssh/sshd_config and restart SSH service as the following. 6. Change Default Port Port 22 is the default SSH listens port for incoming connections. The hacker can constantly scanning the server for port 22, and an effective method is to changing the default SSH port, for example to port 22224 as the following, to eliminate this attacks. Now we need to check SELinux what ports sshd is allowed to listen on by executing the following command. To allow sshd to listen on the new port 2223 we have to add a rule to SELinux and restart SSH service as the following 7. Limit Access With Firewall For security enhancement, we should filter the connections with firewall by adding a firewall rule in IPTables to limit access on the changed port 2223 to only an authorized IP addresses. Edit file /etc/sysconfig/iptables and restart IPTable service as the following. 8. Limit Idle Timeout Interval If a timeout period for SSH connections on a server is not setting up, it is a security risk. In many cases, people stay away from their computers without locking the screens and SSH is still connected to the server. Thus, it could be compromise. Edit file /etc/ssh/sshd_config as the following. The timeout interval is in seconds. So let set it to 300 seconds to have 5 minutes idle timeout. 9. Limit Maximum Fail Authentication Limiting a maximum fail authentication with SSH is a good method to stop the password brute-forcing attacks. If a user input the password incorrectly for N-1 times of the limited N time, the SSH remote session will be disconnected and will have to reconnect again. In below configuration, when user incorrectly input the password for times, the remote session will be disconnected. 10. Limit Listen Address The default configuration of SSH will listens on all available interfaces which it should be limited. If there are multiple interfaces on the server configured with different IP addresses, it is always best to limit the user to login to the server using management IP address only. 11. Disable Rhosts Files Support File .rhosts is used to control which computers trust other computers for SSH remote access to with a certain user account. If a computer trust another computer, then it will allow a specified user to remote SSH access to the trusted computers without having to enter a password. 12. Disable Empty Passwords Access In some case, a certain user account on the server might not have set a password or has empty password. It is a best to always disable these users connecting with remote SSH server. 13. Disable Host-Based Authentication Host-based authentication allows hosts to authenticate on behalf of all or some of the users using the public key. 14. Enable Informational Log Level It is good to configure SSH server to log INFO level information. Since SSH is an entry point to our server, it is recommended to log as much as possible, so we will a comprehensive log information when we run into a problem. 15. Reduce Maximum Start Up Connection Reducing the maximum number of concurrent connections to the SSH daemon can be helpful against a brute-force attack. The setting of MaxStartups 4 tells the ssh server to allow only 4 users to attempt logging in at the same time. 16. Reduce Login Grace Time When we try to remote SSH a server, the default configuration will us 2 minutes to login. If we do not do any thing or cannot successfully login within 2 minutes, SSH session will be disconnected. The default 2 minutes time to login successfully is too much. we should consider reduce it to 1 minute instead. [Hidden Content]
  6. There’s lots of articles on SSH tunneling, and plenty that cover how to create a tunnel with PuTTY, so why write another one? Because I spent longer than I should have trying to get this working the other day, and failing due to a simple order of operations issue. So I decided to spell it out step-by-step, for people like me who need that extra little bit of help. Step 1 – Load the Gateway First, if you have not already done so, create and save the SSH gateway server as you would any other. Next, select it from the Saved Sessions list and click ‘Load’ Step 2 – Configure the Tunnel In the left-hand side nav tree, click Connection > SSH > Tunnels. Enter the port that you want to connect to locally under “Source port”. Then supply the destination address (the server that is available from your SSH gateway, but not from your local machine) as “Destination” Step 3 – Open the Tunnel Click “Add”, which will set the configuration Then click “Open” to connect to your gateway. Login as usual. Now, as long as you leave that SSH terminal window open, all traffic to the Source Port on your localhost will be forwarded on to the Destination. If the destination port provides a web service, you can open a browser tab and visit [Hidden Content] in this example, and you should see the service from the Destination server. ref: [Hidden Content]