Thursday, October 29, 2009

Install BlankOn5 dari Flashdisk 1GB ke 4GB

Setelah lama utak-atik slax, akhirnya kepengen juga mencicipi BlankOn5:Nanggar yang belum lama keluar.
Cek di site-nya mugos eh ternyata udah ada mirrornya, langsung download pake FDM3 (und3r-w1nd0w5)... lewat hotspot UMS bisa dapet 16Mbps ataw 2MBps (karena lokal, nggak lewat ISP), nunggu sekitar 5 menitan selesai deh. Tapi ada kendala nih, harddisk dah hampir penuh dan juga dvd-rw rusak, wew!!!... akhirnya kepikiran untuk menginstallnya ke flashdisk.

Berbekal file iso blankon-5.0-cdlive-i386.iso, 2 Flashdisk, 1GB dan 4GB, serta 2 Program, Grub4Dos dan UltraISO, akhirnya berhasil juga. Disini Flashdisk 1GB-nya aku jadiin pengganti CD Installnya, dan yang 4GB sebagai target disk BlankOn5-nya nanti akan diinstall.

Jika pingin nyobain, 2 program diatas bisa didownload lewat link dibawah ini:
Grub4Dos : http://www.indowebster.com/grub4dos_for_blankon_5_instzip.html
UltraISO : http://www.indowebster.com/UltraISO_8.html
File blankon-5.0-cdlive-i386.iso bisa diunduh di:
http://cdimage.blankonlinux.or.id/rilis/nanggar/
http://mugos.ums.ac.id/pub/iso/Blankon/5.0/
ftp://kambing.ui.ac.id/iso/blankon/rilis/nanggar/
ftp://dl2.foss-id.web.id/iso/blankon/rilis/nanggar/
ftp://mirror.unej.ac.id/blankon-cd/rilis/nanggar/
dan mirror2 lainnya

[under-w1nd0ws-thox]
Pertama kita download file diatas dulu, jika dah punya langsung saja.
1. Format dulu Flashdisk 1GB-nya dengan format FAT.
2. Ekstrak grub4dos_for_blankon_5_inst.zip dan jalankan grubinst_gui.exe.
3 .Klik pada disk dan pilih flashdisk kamu [jangan pilih hd0, hd0 adalah harddisk kamu]
4. klik install dan tutup.
5. Salin file menu.lst dan grldr ke Flashdisk kamu.
6. Buka blankon-5.0-cdlive-i386.iso dengan UltraISO.
7. Ekstrak semuanya ke FlashDisk..
8. Selesai.

[installing]
Prinsip kerja install dari Flashdisk itu sama kalo pake CD,
cuma media setupnya yang beda. Yang perlu diperhatikan:
1. pastikan booting melalui usb-hdd / flashdisk (setting dibios)
2. jangan salah memilih target install harddisk-nya.
3. jangan salah memilih target install boot-loader-nya.
4. isi menu.lst perlu diubah untuk menginstall blankon 5, pastikan menggunakan file menu.lst dari file zip diatas.

Wednesday, October 28, 2009

Using .htaccess files to block exploit attempts

Alright, so there are a lot of noticeable trends in how people exploit Joomla websites and I have seen a lot of simple mod_rewrite configurations that attempt to address this issue but in my opinion they were often to vague and could easily cause problems with the sites normal functions. Hence, I have tried to hash out a set of mod_rewrite conditions that you can tag onto the end of your .htaccess files that will hopefully block out a good number of the common exploit attempts while interferring as little as possible with legitimate usage.

Keep in mind, this is just a trial script I have not had a whole lot of time to test it. You will know it is working correctly/incorrectly if you get forwarded to your home page and receive a 403 Forbidden error.

Append to .htaccess in the same directory as your index.php file.


* Edited last line as the F option is compatible with more versions of Apache than R=403 *
* Edited to include conditions to match recent com_simpleboard and com_extcalendar exploits *
* Edited to remove the conditions that matched com_simpleboard and com_extcalendar specifically *
* Last updated on August 2, 2006 1:35 AM PDT (UTC -8:00) *

I am of course open to comments and suggestions. Your site should still be very usable with this code in place because of how specific I have tried to make the conditions. For example, it will not block out a search string that includes GLOBALS, only one that includes something to the effect of GLOBALS=... or GLOBALS[... or GLOBALS = (URL encoded space, etc)..

It attempts to deal with exploit attempts that try and set _REQUEST variables or GLOBAL variables as well as those that use XSS vulnerabilities and include javascripts with in the URL. It also attempts to block any script trying to assign a value to a mosConfig value and scripts that try and base64_encode information to pass it through the URL. 

If this breaks some feature of your site, just comment out the rules by placing a # in front of them and everything should go back to normal. Let me know what you were doing and copy the URL and save it and I will try and work through it and figure out a way to allow the legitimate requests.

Hope it helps some of you guys worried about your sites security.