TCL scripter
  • Content count

  • Joined

  • Last visited

  • Time Online

    13h 30m 11s

Community Reputation

8 Neutral

1 Follower

About zeke

  • Rank
    The Beasts Trainer

Contact Methods

  • Website URL

Profile Information

  • Gender

Recent Profile Visitors

2,901 profile views
  1. A New home for Tcl Scripts Archive Read the news about the changes here. The new site is located at http://www.tclarchive.org, hosts the old tcl scripts from egghelp.org and is accepting new tcl scripts submissions. Good news, considering that slennox @ egghelp.org hasn't been active for quite some time and tcl scripts submissions were closed. The egghelp.org tcl archive was one of the web's premier repositories of Tcl scripts for Eggdrop, allowing you to search or browse hundreds of scripts that enhanced your bot's functionality. At last update 7 October 2014 it reached over 1743 hosted tcl scripts by 939 authors.
  2. BlackToolS 2.5

    Minor text fixes: spelling and grammar mistakes. The download links were already updated with the fixes. Enjoy! * DONT FORGET: to report your newly found bugs to us!
  3. BlackTools.es.lang.tcl

    Version .2.4

    1 download

    SPANISH LANGUAGE for Blacktools 2.4 Translation provided by Cadaver @ NationCHAT.Org

    2.00 EUR

  4. BlackTools 2.5 Release

  5. Eggdrop v1.8.2 Stable Release

    The final release of Eggdrop version 1.8.2 is here! The major changes are:- CBC mode option for blowfish (only relevant for Tcl scripts, thanks to Cizzle for the significant patch)- Starting Eggdrop with -nt gives full access on the terminal now to simplify debugging- Eggdrop won't quit with the error message "CAN'T WRITE TO TEMP DIR" anymore (temp dir is optional for filesys/transfer mod)- The Tcl command getuser can now retrieve a list of key/value pairs to get all settings for a user- Portuguese language file added (thanks TheMythPT)- Fixed an issue with ./configure --with-ssllib, which prevented users from using a non-standard OpenSSL installation locationYou can follow development and report bugs on https://github.com/eggheads/eggdrop Download Eggdrop v1.8.2 here
  6. A New home for Tcl Scripts Archive Read the news about the changes here. The new site is located at http://www.tclarchive.org, hosts the old tcl scripts from egghelp.org and is accepting new tcl scripts submissions. Good news, considering that slennox @ egghelp.org hasn't been active for quite some time and tcl scripts submissions were closed. The egghelp.org tcl archive was one of the web's premier repositories of Tcl scripts for Eggdrop, allowing you to search or browse hundreds of scripts that enhanced your bot's functionality. At last update 7 October 2014 it reached over 1743 hosted tcl scripts by 939 authors.
  7. Fail2Ban is a simple script designed to scan log files for repeated failed login attempts and to ban IP addresses that make too many failures. Commonly that’s a brute force attempt to find correct password combination to login to a server via SSH. Step 1 – Login to your server via your favorite SSH client. Windows users can simply use Putty, it is free, small, portable and awesome. If you’ve disabled root login, then simply login with the username you setup then type “su” followed by entering your root password. Step 2 – Now issue this command syntax to install fail2ban on your server: You may firstly need to update your apt (not necessary but you may): | apt-get update then this command is the one to install fail2ban | apt-get install fail2ban screenshot: Step 3 – Now you have to setup Fail2ban’s configuration. By default, Fail2ban configuration has included many of possible services that may need the protection. Before you make changes to default config file, you have to make a copy first. Issue following command: | cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local It should look like this Step 4 – The command above copies “jail.conf” file to “jail.local” which you can make some changes to the config there. Now edit that file using our favorite text editor, Nano: | nano /etc/fail2ban/jail.local It should look like this.. Step 5 – Now make some changes (if you wish and if you need to) in the first section of the config. The first section called “DEFAULT” which is covering all basic rules that fail2ban will follow. The main important part is “ignore ip”. You can add your own IP address there so in case if you forgot the password you won’t be banned for trying some combinations no matter how many times you try. It means by adding your IP in the white list you can avoid accidentally ban yourself. Also do not forget to set “bantime” which rules how many seconds a banned user will still been locked out. Default value is 600 seconds or 10 minutes. You can adjust that value as you wish but you better raise the value because most of brute force bots will simply move on to the next target once banned by the server. Below “bantime” line is “maxretry”. This line defines how the amount of incorrect login attempts that a single IP may have before it gets banned for the length of the ban time you’ve defined. Default value is “3” but you can lower that value to “2” or “1”. The lower is better but make sure you white-listed your IP already in the “ignore ip” line above. The next line is “backend” which you can simply leave its value as “auto”. Now move to another line, “destemail”. In this line you can define to which email address all alerts will be sent. Simply change root@localhost to your own personal email address. But you have to make sure that your server has a working mail server already to be able to send outgoing email. Step 6 – Now move to the next section which is “Action”. Well, you can simply leave those lines as it is if you don’t really sure. All default value should be adequate for fail2ban to work correctly. Now you have to move a little bit down below and find the [ssh] section. You also don’t have to change that section. Its default values indicating that SSH protection is currently enabled / ON. You can change “enabled = true” to false if you want to turn OFF the protection. You can change the “port = ssh” line to the custom port number your SSH connection is designated. For instance, you’ve changed default SSH port from 22 to 2200, then change it to “port = 2200” Once done editing, hit Control+O to save then Control+X to exit Nano editor screen. Step 7 – That’s it. Now to make sure Fail2ban loads your newly defined config, simply do a restart. Issue this command: | service fail2ban restart Q: I rebooted the server, does it starts automatically? Yes, Fail2ban service will automatically start each time your server reboots. That’s it.
  8. Configuring IPv6 on your VPS

    All these examples assume an IPv6 subnet of 2001:DB8:1000::/64. You'll need to update them with the subnet that you have been assigned. We'll be using 2001:DB8:1000::100 as the main IP address to assign. We'll also be using 2001:19f0:4009:2001::1234 as a secondary IP address we're configuring. Adding a secondary IP is not necessary, but shows the process you'd use if you wanted multiple IPv6 addresses. Important Note: If you add an IPv6 subnet to an existing machine, you must restart the server via the control panel before IPv6 will work. Restarting via SSH or similar is not sufficient. IPv6 would not work at all until the server has been restarted. This does not apply if you've selected IPv6 during the initial server deployment. Windows: netsh interface ipv6 set global randomizeidentifiers=disabled netsh interface ipv6 add address interface="Local Area Connection" address="2001:DB8:1000::100/64" netsh interface ipv6 add address interface="Local Area Connection" address="2001:19f0:4009:2001::1234/64" CentOS: In /etc/sysconfig/network-scripts/ifcfg-eth0 add the following lines: IPV6INIT="yes" IPV6ADDR="2001:DB8:1000::100/64" IPV6_AUTOCONF="yes" IPV6ADDR_SECONDARIES="2001:19f0:4009:2001::1234/64" If you have IP forwarding enabled (if you're using your server as a VPN or similar), you'll need to add the following to /etc/sysctl.conf: net.ipv6.conf.all.accept_ra=2 net.ipv6.conf.eth0.accept_ra=2 The default settings here (which is 1), prevents IPv6 from working properly when IP forwarding is enabled. You can check if IP forwarding is enabled by running "sysctl net.ipv4.ip_forward". Debian/Ubuntu: In /etc/network/interfaces add the following lines: iface eth0 inet6 static address 2001:DB8:1000::100 netmask 64 up /sbin/ip -6 addr add dev eth0 2001:19f0:4009:2001::1234 If you have IP forwarding enabled (if you're using your server as a VPN or similar), you'll need to add the following to /etc/sysctl.conf: net.ipv6.conf.all.accept_ra=2 net.ipv6.conf.eth0.accept_ra=2 The default settings here (which is 1), prevents IPv6 from working properly when IP forwarding is enabled. You can check if IP forwarding is enabled by running "sysctl net.ipv4.ip_forward". FreeBSD: In /etc/rc.conf add the following lines: rtsold_enable="YES" ipv6_activate_all_interfaces="YES" rtsold_flags="-aF" ifconfig_vtnet0_ipv6="inet6 2001:DB8:1000::100 prefixlen 64 accept_rtadv" ifconfig_vtnet0_alias0="inet6 2001:19f0:4009:2001::1234 prefixlen 64"
  9. ZNC is an advanced IRC network bouncer that is left connected all the time so that an IRC client can disconnect or reconnect without losing the chat session. In this tutorial, we'll compile ZNC with the web admin module installed. Installation Packages First of all, and as always, we'll update the package cache. sudo apt-get update Next, we'll install some dependencies required to compile ZNC. sudo apt-get install libssl-dev libperl-dev pkg-config build-essential Compile and install ZNC Download the latest release of ZNC: cd /usr/local/src sudo wget http://znc.in/releases/znc-latest.tar.gz Extract ZNC from the tarball, and then enter the source directory: sudo tar xf znc-latest.tar.gz cd znc-*/ At this step, you can set ZNC's installation directory by adding the --prefix=<yourdir> option. But for now, we'll install it system wide: ./configure We'll compile ZNC and install it with the following commands. To speed up the process, you may add -j n to the first make command, where n is the number of cores / vCPUs on your server. sudo make sudo make install This may take a few minutes, depends on your machine's configuration. Configuration It is important not to run web-facing apps under root. So we'll create a new user for ZNC. adduser --disabled-password znc Now switch to znc. su znc - cd ~ Create ZNC's config file under znc: /usr/local/bin/znc --makeconf ZNC will ask us some questions in order to create the config file. The first one is important; note your input because you will connect to the ZNC daemon using that port. We'll enter 6697 now - that's the default port for IRC with SSL / TLS. [ ?? ] What port would you like ZNC to listen on? (1025 to 65535): 6697 It is strongly recommended to enable SSL listening instead of the plain-text (i.e. insecure) scheme. Would you like ZNC to listen using SSL? (yes/no) [no]: yes Next question is regarding IPv6. That actually depends on your needs. If your home network is IPv6 enabled, it's recommended to enable. We'll just leave the default option there. [ ?? ] Would you like ZNC to listen using both IPv4 and IPv6? (yes/no) [yes]: <press Enter> Now it'll prompt us about two global modules, partyline and webadmin. They're self-explanatory, and we'll need to enable them. [ ?? ] Load global module <partyline>? (yes/no) [no]: yes [ ?? ] Load global module <webadmin>? (yes/no) [no]: yes User creation. Enter your desired username and password for the user, then confirm it. Note that the password will not be echoed. [ ?? ] Username (AlphaNumeric): Doe [ ?? ] Enter Password: <password> [ ?? ] Confirm Password: <password> Grant the user admin permissions: [ ?? ] Would you like this user to be an admin? (yes/no) [yes]: yes Then, your IRC network options. Set it on your own. Here's an example: [ ?? ] Nick [Doe]: Doe [ ?? ] Alt Nick [Doe_]: Doe_ [ ?? ] Ident [Doe]: DoeIdent [ ?? ] Real Name [Got ZNC?]: Jane Doe [ ?? ] Bind Host (optional): server.hostname [ ?? ] Number of lines to buffer per channel [50]: 50 [ ?? ] Would you like to clear channel buffers after replay? (yes/no) [yes]: yes Enable these modules: [ ?? ] Load module <chansaver>? (yes/no) [no]: yes [ ?? ] Load module <controlpanel>? (yes/no) [no]: yes [ ?? ] Load module <perform>? (yes/no) [no]: yes [ ?? ] Load module <webadmin>? (yes/no) [no]: yes Now we may setup the IRC network that ZNC will connect to. [ ?? ] Would you like to set up a network? (yes/no) [no]: yes We'll use #ubuntu on Freenode for example. Network (e.g. 'freenode' or 'efnet'): freenode Information about these network modules prompted are here. [ ?? ] Load module <chansaver>? (yes/no) [no]: yes [ ?? ] Load module <keepnick>? (yes/no) [no]: yes [ ?? ] Load module <kickrejoin>? (yes/no) [no]: yes [ ?? ] Load module <kickrejoin>? (yes/no) [no]: yes [ ?? ] Load module <nickserv>? (yes/no) [no]: yes [ ?? ] Load module <perform>? (yes/no) [no]: yes [ ?? ] Load module <simple_away>? (yes/no) [no]: yes Set the server we'll connect to: [ ?? ] IRC server (host only): irc.freenode.net [ ?? ] [irc.freenode.net] Port (1 to 65535) [6667]: 6697 [ ?? ] [irc.freenode.net] Password (probably empty): [ ?? ] Does this server use SSL? (yes/no) [no]: yes [ ** ] [ ?? ] Would you like to add another server for this IRC network? (yes/no) [no]: no And the channel we'll join: [ ?? ] Would you like to add a channel for ZNC to automatically join? (yes/no) [yes]: yes [ ?? ] Channel name: #ubuntu [ ?? ] Would you like to add another channel? (yes/no) [no]: no Finish the configuration and launch ZNC: [ ?? ] Would you like to set up another user? (yes/no) [no]: no [ .. ] Writing config [/home/znc/.znc/configs/znc.conf]... [ >> ] ok ... ... [ ?? ] Launch ZNC now? (yes/no) [yes]: yes Yay. ZNC is up and running!
  10. In this tutorial, you will learn how to add a web interface to your Linux VPS. The instructions here were tested using Ubuntu 12.04. Ajenti is an open source, web-based, lightweight control panel for Linux servers. It offers a simple, yet powerful graphical interface to perform most of the actions that are required to configure and keep your server up-to-date. If you want a simple, yet stable control panel with some eye candy, then try Ajenti on your VPS. Setup repositories Connect to your server using SSH as the root user. Download the latest package files. apt-get update Import keys and add the Ajenti Repository. Pay attention, this is important to prevent installing infected packages. wget http://repo.ajenti.org/debian/key -O- | apt-key add - Add the APT repository to to your sources.list file. echo "deb http://repo.ajenti.org/ng/debian main main ubuntu" >> /etc/apt/sources.list Install Ajenti Update the package sources again, then install the Ajenti package. apt-get update apt-get install ajenti Start Ajenti with the following command. service ajenti restart Now you can access the Ajenti panel by navigating to the following URL in a web browser. Replace [SERVER_IP] with the IP address of your VPS. https://[SERVER_IP]:8000/ If you are unable to access this URL, try opening the TCP port with the following command. iptables -A INPUT -p tcp --dport 8000 -j ACCEPT You will be presented with an invalid SSL certificate error. It is safe to proceed. Next, you will see a login screen. You can login with any UNIX username, such as root. At this point, you are inside the Ajenti panel. Navigate around the panel to start using some of its primary features, such as processor usage, memory usage, SSH over the web browser, cron job setup, firewall configuration, file system load, and more!
  11. There are several ways of logging into a server over SSH. Methods include password login, key-based login, and two-factor authentication. Two-factor authentication is a much better type of protection. In the event that your computer gets compromised, the attacker would still need an access code to login. In this tutorial, you will learn how to set up two-factor authentication on an Ubuntu server using Google Authenticator and SSH. Step 1: Prerequisites An Ubuntu 14.04 server (or newer). A non-root user with sudo access. A smart phone (Android or iOS) with the Google Authenticator App installed. You can also use Authy or any other app supporting TOTP based logins. Step 2: Installing Google Authenticator Library We need to install the Google Authenticator Library module available for Ubuntu which will allow the server to read and validate codes. Run the following commands. sudo apt-get update sudo apt-get install libpam-google-authenticator Step 3: Configure Google Authenticator for each user To configure the module, just run the following command. google-authenticator Once you run the command, you will be asked certain questions. The first question would be: Do you want authentication tokens to be time-based (y/n) Press y and you will get a QR code, secret key, verification code, and emergency backup codes. Take out your phone and open the Google Authenticator app. You can either scan the QR code or add the secret key to add a new entry. Once you have done that, note down the backup codes and keep them safe somewhere. In case your phone gets misplaced or damaged, you can use those codes to login. For the remaining questions, press y when asked to update the .google_authenticator file, y for disallowing multiple uses of same token, n for increasing time-window, and y to enable rate-limiting. You will have to repeat Step 3 for all of the users on your machine, otherwise they won't be able to login once you are through with this tutorial. Step 4: Configure SSH to use Google Authenticator Now that all users on your machine have set up their Google authenticator app, its time to configure the SSH to use this authentication method over the current one. Enter the following command to edit the sshd file. sudo nano /etc/pam.d/sshd Find the line @include common-auth and comment it out like below. # Standard Un*x authentication. #@include common-auth Add the following line to the bottom of this file. auth required pam_google_authenticator.so Press Ctrl + X to save and exit. Next, enter the following command to edit the sshd_config file. sudo nano /etc/ssh/sshd_config Find the term ChallengeResponseAuthentication and set its value to yes. Also find the term PasswordAuthentication, uncomment it, and change its value to no. # Change to no to disable tunnelled clear text passwords PasswordAuthentication no Next step is to add the following line to the bottom of the file. AuthenticationMethods publickey,keyboard-interactive Save and close the file by pressing Ctrl + X. Now that we have configured the SSH server to use the Google Authenticator, its time to restart it. sudo service ssh restart Try logging back into the server. This time you will be asked for your Authenticator code. ssh user@serverip Authenticated with partial success. Verification code: Enter the code that your app generates and you will be logged in successfully. Note In case you lose your phone, use the backup codes from Step 2. If you lost your backup codes, you can always find them in the .google_authenticator file under the user home directory after you login via console. Conclusion Having multiple factor authentication greatly improves your server's security and allows you to help thwart common brute force attacks.
  12. Introduction Easy Hosting Control Panel (EHCP for short) is a free and open source hosting control panel that can be used to host websites, create emails, sub domains, and FTP accounts easily using a web browser. It is written in the PHP programming language and provides built-in support for Nginx and PHP-FPM. Some of the EHCP features include: Open source and easily customizable. Manage DNS, domains, sub domains, FTP, MySQL, Email. Password protect domains. Support SSL, disk quota, domain alias, domain redirect. Backup and restore functionality. Supports unlimited user accounts, email accounts, and FTP accounts. Prerequisites A newly deployed Ubuntu 16.04 server instance. A non-root user with sudo privileges setup on your server. A static IP address of configured on your system. As you're reading, replace this with the main IP of your server. Step 1: System update First, update your system to the latest stable version by running the following command: sudo apt-get update -y sudo apt-get upgrade -y sudo reboot Step 2: Install EHCP Download the latest version of the EHCP installation package. You can download EHCP from their official website. For example: wget http://ehcp.net/ehcp_yeni.tgz Once the download has completed, extract the downloaded file with the following command. tar -zxvf ehcp_yeni.tgz Next, change the directory to ehcp and run the install.sh script to install EHCP. cd ehcp sudo ./install.sh During the installation, read each step carefully and follow the instructions. The installer will install all of the required packages such as Apache, MySQL, Postfix and PHP. You will also need to provide some information to configure the different services and set the admin passwords. The installation can take up to 60 minutes depending on your internet speed. Upon a successful installation, you will see the following output: ehcp install finished up to now. we are continuing on simplifying the install process. sorry for any inconvenience. you can contact email/msn: info@ehcp.net you may join us in developing this control panel. You may visit http://www.ehcp.net You may support by donating cash, buying a pro license, doing php coding, html design, graphic design... You may support by donating free dedicated or virtual servers for this project... CURRENTLY WE NEED A DEDICATED SERVER WITH 8 CORE, 8GRAM, 500G hdd at least (or, you may consider to buy a pro license or donate..) ehcp : Finished all operations.. go to your panel at http://yourip/ now... Step 3: Access EHCP dashboard It's time to access the EHCP dashboard. Open your web browser and type the URL On the main page, click on the link that reads "Click here for the control panel on your server". Enter your login credentials. The default username is admin and the password is the one you setup during the installation. If you haven't set a password, use the default password of 1234. Congratulations! You have successfully installed EHCP on Ubuntu 16.04 server.
  13. Using a sudo user to access a server and execute commands at root level is a very common practice among Linux and Unix Systems Administrator. The use of a sudo user is often coupled by disabling direct root access to one's server in an effort to prevent unauthorized access. In this tutorial, we will be covering the basic steps for disabling direct root access, creating a sudo user, and setting up the sudo group on CentOS, Debian, and FreeBSD. Prerequisites A newly installed Linux server with your preferred distribution. A text editor installed on the server whether it's nano, vi, vim, emacs. Step 1: Installing sudo Debian apt-get install sudo -y CentOS yum install sudo -y FreeBSD cd /usr/ports/security/sudo/ && make install clean or pkg install sudo Step 2: Adding the sudo user A sudo user is a normal user account on a Linux or Unix machine. Debian adduser mynewusername CentOS adduser mynewusername FreeBSD adduser mynewusername Step 3: Adding the new user to the wheel group (optional) The wheel group is a user group which limits the number of people who are able to su to root. Adding your sudo user to the wheel group is entirely optional, but it is advisable. Note: In Debian, the sudo group is often found instead of wheel. You can however manually add the wheel group using the groupadd command. For the purpose of this tutorial, we will use the sudo group for Debian. The difference between wheel and sudo. In CentOS and Debian, a user belonging to the wheel group can execute su and directly ascend to root. Meanwhile, a sudo user would have use the sudo sufirst. Essentially, there is no real difference except for the syntax used to become root, and users belonging to both groups can use the sudo command. Debian usermod -aG sudo mynewusername CentOS usermod -aG wheel mynewusername FreeBSD pw group mod wheel -m mynewusername Step 4: Making sure your sudoers file is setup properly It is important to ensure that sudoers file located in /etc/sudoers is setup properly in order to allow sudo users to effectively use the sudo command. In order to accomplish that, we will view the contents of /etc/sudoers and edit them where applicable. Debian vim /etc/sudoers or visudo CentOS vim /etc/sudoers or visudo FreeBSD vim /etc/sudoers or visudo Note: The visudo command will open /etc/sudoers using the system's preferred text editor (usually vi or vim). Start reviewing and editing below this line: # Allow members of group sudo to execute any command This section of /etc/sudoers often looks like this: # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL In some systems, you may not find %wheel instead of %sudo; in which case, this would be the line under which you would start modifying. If the line starting with %sudo in Debian or %wheel in CentOS and FreeBSD is not commented out (prefixed by #), this means that sudo is already setup and is enabled. You can then move to the next step. Step 5: Allowing a user that belongs to neither the wheel nor the sudo group to execute the sudo command It is possible to allow a user that is in neither user groups to execute the sudo command by simply adding them to /etc/sudoers as follows: anotherusername ALL=(ALL) ALL Step 6: Restarting the SSHD Server In order to apply the changes you made to /etc/sudoers, you need to restart the SSHD server as follows: Debian /etc/init.d/sshd restart CentOS 6 /etc/init.d/sshd restart CentOS 7 systemctl restart sshd.service FreeBSD /etc/rc.d/sshd start Step 7: Testing After you have restarted the SSH server, log out and then log back in as your sudo user, then attempt to execute some testing commands as follows: sudo uptime sudo whoami Any of the below commands will allow the sudo user to become root. sudo su - sudo -i sudo -S Notes: The whoami command will return root when coupled with sudo. You will be prompted to enter your user's password when executing the sudo command unless you explicitly instruct the system to not prompt sudo users for their passwords. Please note that is not a recommended practice. Optional: allowing sudo without entering the user's password As previously explained, this is not a recommended practice and is included in this tutorial for demonstration purposes only. In order to allow your sudo user to execute the sudo command without being prompted for their password, suffix the access line in /etc/sudoers with NOPASSWD: ALL as follows: %sudo ALL=(ALL:ALL) ALL NOPASSWD: ALL Note: You need to restart your SSHD server in order to apply the changes. Step 8: Disable direct root access Now that you have confirmed that you can use your sudo user without issues, it is time for the eighth and final step, disabling direct root access. First, open /etc/ssh/sshd_config using your favorite text editor and find the line containing the following string. It may be prefixed with a # character. PermitRootLogin Regardless of the prefix or the value of the option in /etc/ssh/sshd_config, you need to change that line to the following: PermitRootLogin no Finally, restart your SSHD server. Note: Do not forget to test your changes by attempting to SSH into your server as root. If you are unable to do so, this means that you have successfully completed all the necessary steps. This concludes the tutorial.
  14. When setting up a new Linux server, updating the system's Kernel and other packages to the latest stable release is a recommended practice. In this article, we will learn how to update CentOS 7, Ubuntu 16.04 LTS or Debian 8. Prerequisites A fresh CentOS 7, Ubuntu 16.04, or Debian 8 server instance. A sudo user. On CentOS 7: Setup the EPEL YUM repo: sudo yum install epel-release -y Perform the system update and then apply system modifications by restarting the system: sudo yum update -y && sudo shutdown -r now On Ubuntu 16.04 or Debian 8: Update the list of packages which can be updated: sudo apt-get update -y Then install updates and then apply them by restarting the system: sudo apt-get upgrade -y && sudo shutdown -r now That's it. After the reboot, log in as the same sudo user to continue your work.
  15. Grue is a grey bluey “flat” style theme for Sentora Control Panel. You can see a demo of it in action over at sentora.ga. Login to the Sentora demo then go into the “Theme Selector” and choose “Grue”. Download Grue is available over on the GitHub page. To install 1. Download the zip from GitHub. 2. Extract it to your Sentora “styles” path. (Usually /etc/sentora/panel/etc/styles/) 3. Rename “Grue-master” folder to “Grue” (Notice the uppercase “G”) 4. In Sentora set the theme and away you go!