Translate

tmp secure directory is not empty | centos not boot with tmp secure error |tmp.secure :directory is not empty

tmp secure directory is not empty | centos not boot with tmp secure error |tmp.secure :directory is not empty


May VPS servers may have this problem..
If you have VPS machine with Centos and CPanel after use /scripts/securetmp your server does not boot and show this error in OS boot level.

tmp secure directory is not empty
The problem that you have when you see the boot screen:
Can not move /usr/tmp.secure to /ur/tmp.secure.cpback/tmp.secure :directory is not empty

This problem from cPanel secure tmp and we can solve it by disable /scripts/securetmp on boot on cPanel Server.

cPanel's /scripts/securetmp is a great and easy tool to secure your tmp part of your server and it used industry standard security measurements.

But sometimes will slow down your server startup time, because it's time consuming process, if your tmp size is bigger, specially on HDD then you must fix it by following command:


 To fix this issue disable it on boot just issue this command on your:

touch /var/cpanel/version/securetmp_disabled 

dubbed POODLE | Google discovers vulnerability in SSL 3.0 | POODLE

Dubbed POODLE | Google discovers vulnerability in SSL 3.0 | POODLE



When you access high profile sites and services such as your bank, Twitter  or Google  you typically access sites using https:// or a feature called SSL  (secure sockets layer) but a new security defect could break that open. SSL or TLS (Transport Layer Security) provides encryption to protect your information from being intercepted, spied upon or modified by attackers in between you and the service provider. This widely used technology is what prevents someone sat next you in Starbucks from watching your transactions as you access your Internet banking and is also frequently used when accessing your e-mail account to stop your username and password disappearing in to the hands of cyber criminals. Simply put SSL is a core component of security, privacy and trust on the Internet . Great though all that sounds unfortunately many sites still fail to adhere to best practice and many don’t implement these security features at all leaving information open to interception. Even those which do try to do the right thing can have significant setbacks due to implementation failures or security vulnerabilities. That is precisely what has happened with the new, cutely named, but very nasty POODLE vulnerability.

SSL has a number of different versions and which you support is important from a security standpoint. Backwards compatibility with older versions can get you in real trouble and you can see a wonderfully detailed breakout of the features of each version and timelines here. The POODLE vulnerability impacts SSL version 3 and under the right conditions would allow an attacker to gain access to information that would let them take over your account . For example, the flaw may enable an attacker to gain access to session tokens or credentials so they can hijack the identify of another user. The vulnerability, discovered by Google security researchers Thai Duong, Bodo Moller and Krzysztof Kotowiczis is fully outlined in this paper and makes interesting reading. Geeky bit: the attack is essentially an oracle padding attack in CBC (cipher block chaining which uses output of previous blocks as input to the next block processing to prevent duplicate blocks of data producing identical cipher text blocks) mode ciphers in SSLv3.

For the attack to work the attacker must be on the same wireless network (or in the path of your communications) and your client must be running Javascript (such as in a web browser) which makes the attack less all out serious than vulnerabilities like Heartbleed . This attack is effective against clients (as opposed to servers like with Heartbleed or Shellshocked) and so is of the greatest concern to users browsing on wireless hotspots where others may be listening but is sufficiently serious that Twitter has announced they have entirely disabled SSLv3 .

How To Install cPanel on a Server or VPS Running Centos 6

How To Install cPanel on a Server or VPS Running Centos 6


Before installing cPanel on our droplet, we need to take two additional steps.
First we need to make sure that Perl is installed on the server:

 yum install perl
 
After installing perl we need to take one more preliminary step. cPanel is very picky about making sure that server that it is installed on has a Fully Qualified Domain Name. To that effect, we need to provide it with a valid hostname. Skipping this step will inevitably get you the following, very common, error:

2014-10-01 16:00:54  461 (ERROR): Your hostname () is not set properly. Please
2014-10-01 16:00:54  462 (ERROR): change your hostname to a fully qualified domain name,
2014-10-01 16:00:54  463 (ERROR): and re-run this installer.
 
Luckily this error has a very easy solution. If you have a FQDN, you can type it in with the command:

hostname your FQDN
 
Otherwise, if you want to proceed with the cPanel installation but do still lack the hostname, you can input a temporary one. Once cPanel is installed, you will be able to change the hostname to the correct one on one of the first setup pages.

hostname  host.example.com

Install cPanel

Although the cPanel installation only has several steps, the installation does take a long time.
 
you can proceed to install cPanel with WHM or a DNS only version of cPanel.
  • Use this this command to install cPanel with WHM: 
    cd /home 
    wget -N http://httpupdate.cPanel.net/latest
    sh latest 
  • Use this command to install the DNS only version of cPanel:
    cd /home 
    wget -N http://httpupdate.cPanel.net/latest-dnsonly
Once cPanel finally installs, you can access the login by going to your ip address:2087 (eg. 12.34.45.678:2087l) or domain (example.com:2087)
Your login will be:
username: your_server_user
password: your_password
From there, you can create your cpanel user and finally login in at ipaddress/cpanel or domain/cpanel

Install NginxCp, Install NginxAdmin, Install Nginx Admin, Install Nginx Cpanel

Install NginxCp, Install NginxAdmin, Install Nginx Admin, , Install Nginx Cpanel

Ngnix admin or Nginx cp or Nginx cpanel.

 

Installation Instruction

Nginx Admin Install instruction:
cd /usr/local/src
wget http://nginxcp.com/latest/nginxadmin.tar 
tar xf nginxadmin.tar
cd publicnginx
./nginxinstaller install 





Nginx Admin Uninstall instruction:


cd /usr/local/src 
wget http://nginxcp.com/latest/nginxadmin.tar 
tar xf nginxadmin.tar 
cd publicnginx
./nginxinstaller uninstall 


Install NginxCp, Install NginxAdmin, Install Nginx Admin, , Install Nginx Cpanel



Clear Memory cache Linux, Free Memory cache Linux, Release cached memory Linux,Flush Memory Cache on Linux Server

 Clear Memory cache Linux, Free Memory cache Linux, Release cached memory Linux,Flush Memory Cache on Linux Server


 Clear Memory cache Linux, Free Memory cache Linux, Release cached memory Linux,Flush Memory Cache on Linux Server



Many times administrator of Linux servers having a low memory of Linux servers, as Linux uses too much memory for disk caching then the RAM will be used.
I will explain in this article how you will flush memory cache in Linux servers.

Clear Memory Cache in Linux Server's:

    1. Connect via shell using a program such as Putty
    2. At the shell prompt type crontab -e <enter> as this will allow you to edit cron jobs for the root user.
      • If you are not familiar with vi (linux editor) you press “i” to insert text and once done hit “esc” and type “:wq” to save the file.
    3. Scroll to the bottom of the cron file using the arrows key and enter the following line:
                 0 * * * * /root/clearcache.sh
              4. Create a file in ‘/root’ called ‘clearcache.sh’ with the following content:

                #!/bin/sh
                sync; echo 3 > /proc/sys/vm/drop_caches

            5. Once you have saved this file, the job is complete!

Hope you are now know how to solve this problem clear cache memory in Linux Servers.
If you need any help don't hesitate to contact us.


 


Enable IPtables modules in OpenVZ VPS

Enable IPtables modules in OpenVZ VPS



Many of servers administrator not know how to Enable IPtables modules in OpenVZ VPS .
This will be done as following scenario.
Adding Rules manually inside node server for any VPS that you want to Enable IPtables modules inside it.
Open the VPS configuration file which exists at the follwoing path:
 /etc/vz/conf/veid.conf .... example: nano /etc/vz/conf/101.conf
veid: is the id of the vps server.
 Add the following in the last line of the file:
IPTABLES="iptable_filter iptable_mangle ipt_limit ipt_multiport ipt_tos ipt_TOS ipt_REJECT ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_LOG ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_conntrack ipt_state ipt_helper iptable_nat ip_nat_ftp ip_nat_irc"

Then Restart the container as follow:
# vzctl restart 101

Then open VPS and try to surely that you Enable IPtables modules in OpenVZ VPS .

If you need any help try to contact us.



openssl 1.0.1g heartbleed updates for Centos,Redhat and Fedora



Openssl 1.0.1g heartbleed updates for Centos,Redhat and Fedora.

From below steps you can install last version of openssl 101g that will protect you from  heartbleed:

cd /usr/src
wget https://www.openssl.org/source/openssl-1.0.1g.tar.gz
tar -zxf openssl-1.0.1g.tar.gz
cd openssl-1.0.1g
./config
make
make test
make install
openssl version
*************

If it shows old version do the steps below:
mv /usr/bin/openssl /root/
ln -s /usr/local/ssl/bin/openssl /usr/bin/openssl

Any help you can contact us please.
 

The Heartbleed Bug

The Heartbleed Bug

The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.



What leaks in practice?

We have tested some of our own services from attacker's perspective. We attacked ourselves from outside, without leaving a trace. Without using any privileged information or credentials we were able steal from ourselves the secret keys used for our X.509 certificates, user names and passwords, instant messages, emails and business critical documents and communication.
 
 

What versions of the OpenSSL are affected?

Status of different versions:
  • OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
  • OpenSSL 1.0.1g is NOT vulnerable
  • OpenSSL 1.0.0 branch is NOT vulnerable
  • OpenSSL 0.9.8 branch is NOT vulnerable
Bug was introduced to OpenSSL in December 2011 and has been out in the wild since OpenSSL release 1.0.1 on 14th of March 2012. OpenSSL 1.0.1g released on 7th of April 2014 fixes the bug.

How common are the vulnerable OpenSSL versions?

The vulnerable versions have been out there for over two years now and they have been rapidly adopted by modern operating systems. A major contributing factor has been that TLS versions 1.1 and 1.2 came available with the first vulnerable OpenSSL version (1.0.1) and security community has been pushing the TLS 1.2 due to earlier attacks against TLS (such as the BEAST).

How about operating systems?

Some operating system distributions that have shipped with potentially vulnerable OpenSSL version:
  • Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4
  • Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11
  • CentOS 6.5, OpenSSL 1.0.1e-15
  • Fedora 18, OpenSSL 1.0.1e-4
  • OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012)
  • FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013
  • NetBSD 5.0.2 (OpenSSL 1.0.1e)
  • OpenSUSE 12.2 (OpenSSL 1.0.1c)
Operating system distribution with versions that are not vulnerable:
  • Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14
  • SUSE Linux Enterprise Server
  • FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013
  • FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013
  • FreeBSD 10.0p1 - OpenSSL 1.0.1g (At 8 Apr 18:27:46 2014 UTC)
  • FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)

How can OpenSSL be fixed?

Even though the actual code fix may appear trivial, OpenSSL team is the expert in fixing it properly so fixed version 1.0.1g or newer should be used. If this is not possible software developers can recompile OpenSSL with the handshake removed from the code by compile time option -DOPENSSL_NO_HEARTBEATS.


 

samsung galaxy s5,samsung galaxy s5 specification, samsung galaxy s5 specs,samsung galaxy s5 review

samsung galaxy s5,samsung galaxy s5 specification, samsung galaxy s5 specs,samsung galaxy s5 review

samsung galaxy s5,samsung galaxy s5 specification


The Samsung Galaxy S5 is an upcoming Android smartphone produced by Samsung Electronics, which serves as the immediate successor to 2013's Galaxy S4. Unveiled on February 24, 2014 at Mobile World Congress in Barcelona, Spain, it is expected to be generally released on April 11, 2014. As with the S4, the S5 is an evolution of the prior year's model, placing a particular emphasis on an improved build quality, dust and water resistance, a more refined user experience, new security features such as a fingerprint reader, and an updated camera.








Samsung GALAXY S5 - Official Introduction Video: