Allow user to edit and add files to /var/www

The user should then be able to edit /var/www/ files without hassle.

The first line adds the user to the www-data group, the second line clears up any files with messed up ownership, and the third makes it so that all users who are members of the www-data group can read and write all files in /var/www.

If you are logged in as <username> you need to log out and log back in for the group membership to take effect.

Source : http://askubuntu.com/questions/19898/whats-the-simplest-way-to-edit-and-add-files-to-var-www

Cara Reset the MySQL root password on Ubuntu Linux

Ada kalanya mungkin kita lupa password root mysql di vps kita 😀 Nah ini dia caranya buat reset password root mysql kita 😉 Check it out yachhh…..

Stop the MySQL Server.

Start the mysqld configuration.

Login to MySQL as root.

Replace YOURNEWPASSWORD with your new password!

 

Done !!

Menangkal Serangan DDOS Di VPS Dengan Block IP Melalui IP Tables

Masih seperti sebelumnya, artikel ini adalah copas mentah2 dari http://forum.tuban-cyber.web.id/Thread-Tutorial-Menangkal-Serangan-DDoS-Di-VPS

Menangkal Serangan DDoS Di VPS

Cara ini sangat sederhana tapi juga ampuh untuk melihat serangan ddos yang menyerang server atau vps anda Big_smile2 ,1. login ke vps menggunakan putty masuk sebagai user root
2. Jalankan Perintah Berikut ini

Kode:

Perintah di atas akan menampilkan daftar / list IP pengujung dan jumlah koneksi yg di buat tiap IP tsb.

Akan tampil seperti ini misalnya:

Kode:

Pada tampilan di atas sebelah kiri menujukan Jumlah koneksi dan sebelah kanan IP yg mengakses

3.Perhatikan tampilan tsb dan koneksi standar pada server web biasanya maksimal 20 konneksi per ip per detik, anda bisa melihat apa ada yg melebihi 30 koneksi, misal anda menemukan ada IP yng koneksinya mewlebihi 20, coba anda jalankan perintah tadi minimal 5 kali dalam tempo minimal 5 detik

Kode:

Jika anda msh melihat IP tsb dengan koneksi yg tidak menurun bahkan bertambah, sudah di pastikan IP tsb bermasalah.

4. Tapi tunggu dulu jangan berpikir negatif Big_smile2 catat IP tsb cek dulu punya siapa IP tsb anda bisa mengecek IP melalui http://whatismyipaddress.com/ip-lookup, jika hasilnya ip tsb milik google kemungkinan itu google yg sedang melakukan bot crawling / mengindex server/website anda jika tidak brarti itu IP bahaya , di sini kami hanya merekomendasikan IP google Big Grin

5. Lakukan Block IP agar tidak bisa mengakses server anda dengan cara:

Kode:

x.x.x.x di ganti IP yg ingin anda block

6. Jika sudah coba anda cek koneksi lagi :

Kode:

di pastikan juika IP tadi sudah tidak akan tampil karena sudak di block

7. Untuk melihat Status IP yg sudah di block td anda bisa dengan cara :

Kode:

Maka akan tampil seperti ini misalnya:

Kode:

Terlihat bahwa IP yg tadi anda block, dan IP tsb terus berusaha mengirim paket lihat bagian Chain INPUT jumlah pkts akan terus bertambah dan nilai byte juga pasti bertambah.

Membuat Firewall di VPS Ubuntu 12.04

Dicopas mentah2 dari https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-using-ip-tables-on-ubuntu-12-04 😉

Creating the IP Table:

If you type in the following, you can see the current rules in the virtual server’s IP Table:

They should look like this:

If you have another set of rules in place or want to start fresh, you can always set the rules back to the default by flushing and deleting all of them:

Additionally, if you want speed up your work with IP Table, you can include -n in the command. This option disables DNS lookups and prevents the command from trying to find the reverse of each IP in the ruleset. You could use this to list rules, as an example:

A Basic Firewall

As it stands the current rules allow all connections, both incoming and outgoing. There are no security measures in place whatsoever. As we build up the table, keep in mind that as soon as a packet is ACCEPTED, REJECTED, or DROPPED, no further rules are processed. Therefore the rules that come first take priority over later ones.

While creating the rules, we have to be sure to prevent ourselves from accidentally blocking SSH (the method through which we connected to the server).

To start off, let’s be sure to allow all current connections, all of the connections at the time of making the rule, will stay online:

We can go ahead and break this down:

  1. -A tells the IP table to append a rule to the table.
  2. INPUT designates this rule as part of the Input chain.
  3. m conntrack followed by the –cstate ESTABLISHED,RELATED guarantees that the result of this rule will only apply to current connections and those related to them are allowed
  4. -j ACCEPT tells the packet to JUMP to accept and the connections are still in place.

After we are assured that all the current connections to the virtual private server can stay up uninterrupted, we can proceed to start blocking off other insecure connections.

Let’s assume that we want to block all incoming traffic, except for those coming in on 2 common ports: 22 for SSH and 80 for web traffic. We proceed by allowing all traffic on the designated ports with the following commands:

In both of these commands, the -p option stands for the protocol with which the connection is being made, in this case tcp, while the –dport specifies the port through which the packet is being transmitted.

After we have guaranteed that the desirable traffic will make it through the firewall, we can finish up by blocking all remaing traffic from accessing our virtual server. Because this is the last rule in the list, all traffic that matches any of the previous rules in the IP Table will not be affected, and will be treated as we set up previously.

Let’s make a rule to block all of the remaining traffic:

With that, we can see what our updated rules look like:

We are almost finished. However, we are missing one more rule. We need to provide our VPS with loopback access. If we were to add the rule now without further qualifiers, it would go to the end of the list and, since it would follow the rule to block all traffic, would never be put into effect.

In order to counter this issue, we need to make this rule first in the list, using the INPUT option :

  1. -I INPUT 1 places this rule at the beginning of the table
  2. lo refers to the loopback interface
  3. -j ACCEPT then guarantees that the loopback traffic will be accepted

Now we have finished creating a basic firewall. Your rules should look like this (we can see the details of the iptable by typing -v):

However, as soon as the virtual server reboots, the IP tables will be wiped. The next step will go over saving and restoring the IP tables.

Saving IP Tables

Although the IP tables are effective, they will automatically be deleted if the server reboots. To make sure that they remain in effect, we can use a package called IP-Tables persistent.

We can install it using apt-get:

During the installation, you will be asked if you want to save the iptable rules to both the IPv4 rules and the IPv6 rules. Say yes to both.

Your rules will then be saved in /etc/iptables/rules.v4 and /etc/iptables/rules.v6.

Once the installation is complete, start iptables-persistent running:

After any server reboot, you will see that the rules remain in place.

Linux Screen – Solusi agar proses tetap berjalan saat koneksi SSH terputus

Artikel ini saya copy sepenuhnya dari http://hostuner.com/linux-screen/

 

Linux Screen

 

Ketika anda sedang meremote sebuah server melalui ssh dan sedang menjalankan proses yang tidak bisa ditinggal dan membutuhkan waktu lama, lalu tiba-tiba koneksi anda putus, tentunya itu akan sangat menjengkelkan, dan ketika kita kembali terhubung ke server melalui ssh, proses yang kita jalankan tadi tidak bisa kita lihat lagi. Untuk itu kita perlu menggunakan bantuan “linux screen”, utilitas ini berguna untuk melanjutkan kembali sesi terminal sebelumnya, sehingga anda bisa melanjutkan pekerjaan anda walaupun koneksi terputus. Berikut tutorial singkat penggunaan linux screen.

Instalasi Linux Screen

Debian/Ubuntu

CentOS

 

Cara menggunakan screen

Untuk menjalan screen, cukup ketikkan perintah “screen”

 

ketika anda mengetikan perintah tersebut, tidak akan terlihat perubahan yang berarti, hanya akan terjadi perubahan di title terminal anda.

 

linux screen tutorial

 

Sekarang beberapa perintah dasar menggunakan screen, perintah screen dimulai dengan menekan tombol ctrl bersamaan dengan tombol yang diperlukan,

 

  • ctrl+a+c : membuat sebuah sesi screen baru, sehingga anda dapat menggunakan beberapa sesi screen.
  • ctrl+a+n : beralih ke sesi screen selanjutnya (tentunya jika anda membuat beberapa sesi)
  • ctrl+a+p : beralih ke sesi screen sebelumnya
  • ctrl+a+d : melepaskan sebuah sesi screen (tanpa menghentikan proses yang berjalan di dalam screen)
  • exit : untuk mengakhiri sebuah sesi screen

 

Sekarang kita akan sedikit mencoba mempraktekan teori tersebut, pertama tentunya remote server anda, kemudian ketik perintah “screen”, lalu jalankan perintah yang bisa kita lihat, dalam contoh ini saya menggunakan perintah “mtr” (my trace route).

 

 

kemudian buat sesi screen baru lagi dengan menggunakan perintah “ctrl+a+c“, lalu jalankan perintah “ping” misalnya.

 

 

sekarang cobalah berganti sesi screen sebelumnya menggunakan perintah “ctrl+a+p“, dan coba ke screen selanjutnya dengan perintah “ctrl+a+n“.

 

Selanjutnya adalah coba kembali ke sesi SSH biasa atau dengan kata lain deattach (bukan menghentikan screen) dengan perintah “ctrl+a+d“.

 

Untuk melihat daftar screen yang ada, gunakan perintah

 

 

 

Untuk menghubungkan kembali ke salah satu screen, gunakan perintah “screen -r nomor_screen“, contoh

 

Untuk menghapus session screen

Lalu bagaimana jika koneksi saya terputus? Tinggal koneksi saja via ssh, lalu lihat screen yang ada, kemudian hubungkan seperti langkah diatas.

 

Semoga bermanfaat

 

Regards,

 

Install Elasticsearch in Ubuntu 12.04 LTS

Easy install Elasticsearch in Ubuntu 12.04

Source : https://gist.github.com/wingdspur/2026107