Katalis Blog

My Blog Had been Moved to Techonia.com

2010-04-23T16:06:00.002+07:00

Just for your information that this blog had been moved to Techonia.Com. I moved this blog since June 2009, almost one year ago. Apologize for being late to make this announcement.

Thank you
Fuad NAHDI

To be remembered: Air Interface Framing

2009-05-31T11:44:00.003+07:00

Air interface framing is illustrated as in figure below. A super frame is made up of 4096 radio frames. Each radio frame is made up of 15 timeslots. A timeslot can be allocated to either UL (uplink) and DL (downlink) transmission.

Within each timeslot several Resource Units (RUs) (sometime termed "codes" or "bursts") can be supported. An RU is defined as a single code within a single timeslot. As defined in 3GPP TD-CDMA downlink supports two spreading factor, SF1 and SF16. IPWireless implements both SF1 and SF16 for the downlink. Thus, the maximum number of codes supported in the DL is 16xSF16 or 1xSF1 code per time slot. When using SF16, the minimum code granularity on the downlink is 4, meaning that each user gets assigned at least 4 codes. The upper bound on the number of multiples of 4 codes allocated per slot is determined by C/I conditions and traffic conditions. On the uplink, spreading factor 1, 2, 4, 8, and 16 are allowed.
In a public wide-area TDD system such as that of IPWireless the UL and DL transmissions are synchronized to eliminate the possibility of NodeB-to-NodeB and UE-to-UE interference.

Opensolaris 2008.11 screenshots (compiz included)

2009-05-02T10:28:00.003+07:00

Windows 7 in action

2009-03-30T16:05:00.008+07:00

Here are some screenshots of Windows 7 build 7057 (RC1) installed on my own Compaq Presario Laptop. Luckily all hardwares are detected out of the box so I did not need to install any hardware drivers one by one like in Windows XP or even Vista.

The appearances are like Vista actually but there are some improvements in the performance, much faster in loading applications, IE 8 Final Release browser by default, interesting new logon/shutdown background and many others. It also natively supports for Quicktime .mov, DivX and XVid movie files.

Lets take a look at the screenshots below. Thanks to the Windows 7 development team for making it damn cool :)

My Junior just born

2008-09-09T10:49:00.007+07:00

Alhamdulillah, praise be upon Him, my lovely baby just born on August 29, 2008.
I gave him a name 'Naveed Afzal Fazlani', Naveed means good news taken from Persian language, Afzal means better or superior taken from Arabic language and Fazlani means kindness. Hope he will be a good, smart boy as his name.

Mac OS X Leopard 10.5.2 has been successfully installed on my Desktop PC

2008-08-02T17:34:00.006+07:00

A hacker team called "Kalyway" released new Hackintosh Leopard 10.5.2 on March 2008. According to many "Mac Lover", this is the best hackintosh DVD on the planet because of the straight forward and successful installation.

I already tested it on my intel desktop PC and it works fine. Intel sound card and ATI Radeon 9200 work properly. Only editing photos in iPhoto application does not appear the edited photo. Also the Apple Realtek 8139 Ethernet driver has many Tx errors and make my internet connection damn slow and drop very often. To fix this, I need to replace the Apple Realtek ethernet driver with PCGen Realtek driver, the discussion about fixing this realtek driver is on insanelymac.com forum (http://forum.insanelymac.com/index.php?showtopic=69783).

You can also try by yourself to install it on your desktop pc and enjoying this damn pretty operating system.

Many thanks for Kalyway hacker team :)

Maksud hati mengurangi jumlah huruf/abjad dalam Bhs Indonesia

2007-09-27T13:21:00.000+07:00

(diambil dari milis sebelah)

Mengurangi jumlah huruf/abjad pada bahasa Indonesia.
(disadur dari sebuah tulisan yang sudah lama hilang - versi Inggris)

Huruf/Abjad yang digunakan di dalam bahasa Indonesia berjumlah 26.

Ke-26 abjad tersebut rasanya masih terlalu banyak, dan lagipula ada beberapa abjad yang jarang sekali digunakan.

Oleh karena itu mari kita sederhanakan abjad-abjad tersebut dan menyesuaikan dengan kata-kata yang kita gunakan.

Pertama-tama, huruf X, kita ganti dengan gabungan huruf K dan S.
Kebetulan hampir tidak ada kata dalam bahasa Indonesia asli yang menggunakan huruf ini, kebanyakan merupakan kata serapan dari bahasa asing. Misalnya taxi menjadi taksi, maximal menjadi maksimal, dst.

Selanjutnya, huruf Q kita ganti dengan KW. Serupa dengan X, kata2 yang mengunakan huruf ini juga sangat sedikit sekali.

Berikutnya, huruf Z. Huruf Z kita ganti menjadi C. Tidak ada alasan kuat tentang hal ini.

Huruf Y diganti dengan I.
Hal ini dilakukan sebab bunii huruf tersebut mirip dengan I.

Kemudian huruf F dan V keduania diganti menjadi P.

Pada lepel ini masih belum terjadi perubahan iang signipikan.

Hurup W kemudian diganti menjadi hurup U.

Berarti sampai saat ini kita sudah mengeliminasi 7 hurup.

Hurup iang bisa kita eliminasi lagi adalah R, mengingat baniak orang iang kesulitan meniebutkan hurup tersebut. R kita ganti dengan L.

Selanjutnia, gabungan hulup KH diganti menjadi H.

Iang paling belpengaluh adalah hulup S iang diganti menjadi C.

Hulup G juga diganti menjadi K.

Dan hulup J juga diganti menjadi C.

Caia laca cudah cukup untuk hulup-hulup konconannia.

Cekalank kita kanti hulup pokalnia.

Cuma ada lima hulup pokal, A, I , U, E, O.

Kita akan eliminaci dua hulup pokal.

Hulup I mencadi dua hulup E iaitu EE.

Cementala hulup U mencadee dua hulup O iaitoo OO.

Cadi, campe cekalank, keeta belhaceel menkulangee hooloop-hooloop keeta.

Kalaoo keeta tooleeckan lagee, hooloop-hooloop eeang telceeca adalah:

A, B, C, D, E, H, K, L, M, N, O, P, T.

Haneea ada 13 belac hooloop!! Looal beeaca bookan??

Padahal cebeloomneea keeta pooneea 26 hooloop.

Eenee adalah penemooan eeang cankat penteenk dan cikneepeekan! !
Co, ceelahkan keeleemkan tooleecan anda denkan menkkoonakan teeka belac hooloop telceboot.

3D Desktop Ubuntu Festy Fawn with Beryl

2007-09-10T22:29:00.000+07:00

Mac OS X Intel on my desktop PC

2007-01-13T12:42:00.000+07:00

Mac OSX, the world's most 'biutipul' operating system, was successfully installed on my Intel PC. The performances and its 'biuti' don't have any differences with the system installed in PowerPC chip. Any applications like Microsoft Office 2004, Adobe Acrobat Reader, Adobe Photoshop, Macromedia Flash and Dreamweaver, Yahoo Messenger and many more had installed and run greatly on the system without any crashes.

As we know, Apple Inc. has a target to change all the PowerPC chip to Intel-made chip and claimed that the speed is more than 4 times faster than using PowerPC. Good news from Apple.
Nothing I can say, Mac OS X is the cutiest operating system has ever seen before. Even if the base system is BSD Unix, Apple can make the Unix look so 'biuti' and can natively interactive with Windows operating system like mount automatically to Windows file system and even Windows File Sharing.

Interview: Theo de Raadt of OpenBSD

2006-03-29T18:08:00.000+07:00

Theo de Raadt is the project leader for OpenBSD, a Unix-like operating system. We spoke with Theo about the upcoming release of OpenBSD, 3.9, the financial state of the project, and about companies that profit from free software without contributing back.

NewsForge: Hello Theo. Could you tell us a few things about yourself and your involvement in the OpenBSD project?

Theo de Raadt: I have been the project leader for OpenBSD now for more than 10 years, and along the way I have had some good adventures with the developers in the group. We've developed some side projects as well, which are heavily used by everyone in the Unix world, such as OpenSSH.

NF: How many developers contribute to OpenBSD at the moment?

TdR: Inside the project, the count has slowly grown. It was 40 in the early years, and now it is about 80. Of course, that is just counting internal developers. There are many more people on the outside who send us bug reports, fixes, or new code contributions. We also are able to take pieces of code from other sources if they are sufficiently free. But since internal developers have more responsibility -- they have really maintained the areas they are in -- the people on the outside really have an easier job, and should not envy the people on the inside. Instead, they should find a bug, write a fix, and send it in. When someone on the outside sends us many (good) bug fixes, we invite them to become a developer.

NF: You regularly organize events called hackathons. What exactly is a hackathon?

TdR: This is something we started many years ago. A bunch of us would fly to one location (typically before or after a conference) and we would sit down and code. These events really are about getting tasks done; there is very little chatter, as we already know basically what needs to be done. They are not meetings, no one presents talks, nor are they so-called summits. They are for taking action in the source tree, knowing that the guy you need to ask a question of really quickly is sitting at a table a meter away.

NF: OpenBSD is considered one of the most secure operating systems currently available. What approaches do you take towards security?

TdR: We've had 10 years of nearly fanatical devotion to anything which can make OpenBSD more secure. A very important part of that is that we have not been afraid to completely overhaul anything even if it breaks backward compatibility. Secondly, when we have found a flaw in any part of the system we have assumed that the same mistake was made elsewhere, and gone on a hunt to fix them all. Thirdly, we have developed and incorporated a collection of methods that make software flaws very difficult to attack.

The important detail is that in all three of these areas we have not only been fanatical, but pretty much first. Other vendors are not treating their source code the way we treat ours -- with distrust, knowing that we should always actively churn it, so that it can slowly evolve into a better state.

Someone on wikipedia has gone through a lot of effort to identify some of our security efforts, and there is the Exploit Mitigation Techniques paper which I have presented at a number of conferences.

NF: Why should someone use OpenBSD instead of another operating system, besides security?

TdR: I don't really take any position of advocacy. People should use what they want to, and I am not the right person to say anyone "should" do anything. But hey, if someone is adventurous, check it out.

NF: A new stable version, 3.9, is about to be released on May 1. A complete changelog between 3.8 and 3.9 is available; would you comment on some of the new features of this release? Start with G5-based Mac support on macppc architecture. How well does it work at the moment?

TdR: It works on some of the models. For some of the machines we have a strange bug in the Serverworks SATA chipset that we have not been able to fix yet. There is no documentation for that chipset, of course.
NF:Hardware sensors support (ESM, IPMI, IIC) -- a useful feature, especially on servers.

TdR: This has been a significant effort this release. These are three major subsystems that provide temperature, voltage, and fan sensor data. We have a unified system above that, that takes all this and makes it available to a daemon that can alert you when things go wrong.

Regarding specifically the "i2c" subsystem: in the Linux world there is the lm-sensors package, which requires all sorts of hand-configuration for each specific machine. In OpenBSD, we carefully probe for the devices, and it should just work, on every single PC, without any configuration. Thus, pretty much every OpenBSD 3.9 machine will have some sort of sensor now.

We have more work to do now that 3.9 is released, since the sensor daemon is a bit weak for reporting events. We want to make it fantastic.
NF: The new ftp-proxy -- why write a new FTP proxy daemon when the previous one worked fine?

TdR: FTP is a nasty protocol to begin with, and trying to proxy it perfectly is a very difficult task. The new daemon just has a better design, and IPv6 works as well.
NF: NFE, the Nvidia nForce MCP Ethernet adapter. How did you manage to write this driver? Is it reverse-engineered?

TdR: Nvidia did not give anyone documentation. Instead, they expect people to load a gigantic blob of binary code into their kernel, and just be happy with that. Some Linux people in Germany reverse-engineered the driver years ago, but the rough story I heard is that Nvidia asked them to stop, and they did. This just astounds me! In any case, Jonathan Gray (who started this effort) asked for their help with a few problematic technical details, and they refused. I could not believe that, so I asked as well -- and they refused again. These are Linux developers, basically placing the community in a situation where they have to run a binary blob of unknown code from a vendor, instead of sticking to their guns about open source? I must admit, I just don't understand some people. They must have much more flexibility to their belief systems than I have.

Damien Bergamini joined Jonathan toward the end and got all the bugs out of the driver. We are happy to say that it appears to be working better than the Nvidia binary blob. It is also significantly smaller, and it is very clean source code.

NF: In the past there was a movement in the OpenBSD community to press hardware vendors to release documentation about their products (Ethernet and wireless network adapters, RAID controllers, etc.) so that drivers could be written for OpenBSD or other open source projects. Some vendors did release documentation, but others didn't. Why do you think vendors do that? They don't want their products to be supported on OpenBSD?

TdR: There are always at least a few efforts in the project to get more documentation out of vendors. But some vendors are still incredibly resistant. We often run into vendors who have signed NDA agreements with Linux developers, who will then happily write a Linux driver filled with magic numbers, which only one developer in the world understands. Having signed the NDA ensured that Linux got a working driver, sure, but the internals are indistinguishable from magic. It cannot be fixed by anyone else, because it is full of secrets. It is a source code version of a blob.

There are many reasons why vendors will not give information out. I believe that all their reasons are a lie to the customer. I can get nearly complete data books for the parts that are in my car, and I should be able to get them for the parts in my computer.

Once in a while we hear from vendors out of the blue, and they offer us hardware and software without us having to ask. It is happening more -- mostly from Asian hardware manufacturers eager to have their hardware supported by all systems. On the other hand, American companies in particular are becoming increasingly insular, and sometimes we think twice before wasting our time trying to contact them. As a result, our support for a few high-end or very new American products is lagging, because there just isn't documentation available. That is a problem, but it should not be overstated, because 99% of the world is buying these Asian products. For instance, Asian 802.11 vendors accounted for perhaps 1% of the market five years ago, but within a year or two the market is likely to be split between Intel (because of how they tie their wireless chipset into their laptop Centrino brand) and the Asian vendors, such as RAlink and Zydas.

NF: Now that OpenBSD's user base seems to have increased a bit, do you have more success convincing vendors to release documentation for hardware?

TdR: We are having more success getting documentation, but I am not sure if it is due in any way to our user base size. Part of it might be that many more products are coming from Asia (where business sense still applies -- the customer gets the documentation he wants). I think that the Asian businesses are just being smarter about this. When it comes to documentation requests, an Asian company that says no is rare. An American company that says yes is rare.

NF: I understand that OpenBSD is financed from CD sales and donations. Does this money pay for all the projects needs?

TdR: Our income varies year to year. Donations rise and fall, and so do the sales of our products. Meanwhile, our FTP servers just keep getting busier.

We have built up some savings to deal with a rainy day, but our basic operation is perhaps falling behind slowly, or at least slowing our growth. We want to hold more hackathons, since that is where many amazing developments come from. If we had more money, we would also want to pay the travel expenses of some of the poorer developers, since we have some smart developers who are students or live in poorer countries. But with the finances we have, it is difficult to justify these things now. I want us to do much more, but we are constrained.

Donations make the most difference, since our project does not get taxed on them. We have investigated becoming a non-profit organization, but the margins and savings really do not make sense for our project, especially since most of our donations do not come from the country where we operate. Also, there are numerous other constraints and rules. So for now we are sticking to clear cash donations, without tax receipts.

NF: Lots of hardware vendors use OpenSSH. Have you got anything back from them?

TdR: If I add up everything we have ever gotten in exchange for our efforts with OpenSSH, it might amount to $1,000. This all came from individuals. For our work on OpenSSH, companies using OpenSSH have never given us a cent. What about companies that incorporate OpenSSH directly into their products, saving themselves millions of dollars? Companies such as Cisco, Sun, SGI, HP, IBM, Siemens, a raft of medium-sized firewall companies -- we have not received a cent. Or from Linux vendors? Not a cent.

Of course we did not set out to create OpenSSH for the money -- we purposely made it completely free so that the "telnet infrastructure" of the 1980s would die. But it sure is sad that none of these companies return even a fraction of value in kind.

If you want to judge any entity particularly harshly, judge Sun. Yearly they hold interoperability events, for NFS and other protocols, and they include SSH implementation tests as well. Twice we asked them to cover the travel and accommodation costs for a developer to come to their event, and they refused. Considering that their SunSSH is directly based on our code, that is just flat out insulting. Shame on you Sun, shame, shame, shame.

I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already.

Wawancara khusus dengan Bang Rhoma Irama

2006-03-29T14:03:00.000+07:00

"Masya Allah, pornoaksi itu haram!" Winny, seorang wartawati dari Majalah GIRLS ONLY! ditugasi pemimpin redaksinya untuk mewawancarai biang dangdut Rhoma Irama yang sudah gaek. Winny yang lulusan sebuah perguruan tinggi di Kota Gudeg sendiri baru dua bulan kerja di majalah hiburan tersebut. Alhamdulillah, baru sekali nelpon asistennya, Rhoma Irama langsung kasih waktu untuk wawancara khusus. Padahal ia lagi sibuk mempersiapkan shooting sinetron dangdut buat TPI.

Berikut wawancara Winny (W), perempuan muda berpenampilan atraktif yang belum menginjak usia 25 dengan Bang Haji Rhoma Irama (R) di kantornya, kawasan Pejaten, Jaksel:
W: "Assalamu'alaikum Pak Rhoma..."
R: "Waalaikum salaaaaaaam. Antum yang bernama Winny?"
W: "Betul Pak.....saya Winny dari majalah GIRLS ONLY. Maaf Bang, antum itu apa ya artinya?"
R: "Wah, Winny bukan muslimah ya, kok kagak tahu antum. Antum itu artinya kamu."
W: "Oh gitu ya Pak. Maaf saya baru dengar istilah itu..."
R: "Antum muslimah bukan?"
W: "Iya pak....."
R: "Husss, jangan panggil pak ke ana. Panggil saja Bang, kalau antum dipanggil Pak nanti antum cepet tua.."
("Emang udah tua sihhhhhhh", batin Winny)
W: "Ana itu apa artinya bang?"
R: "Ana itu artinya saya..."
W: "Oh gitu.."
R: "Kalau antum muslimah, kok nggak pakai jilbab?"
W: "Belum pengen eh belum siap pak, eh bang..."
R: "Ingat ya, antum harus segera pakai jilbab. Itu kewajiban sebagai muslimah. Pokoknya kudu! Perempuan yang pakai kaos ketat atau you-can-see itu temannya setan. Tidak pantas dilihat dan terlihat seperti perempuan murahan. Kalau antum ke Tangerang pakai pakaian seperti itu bisa ditangkap! Ada itu Perda-nya! Antum ingat-ingat ya
pesan ana."
W: "Iya bang, nanti kalau Winny udah siap lahir batin. Tapi ngomong-ngomong, kok abang naksir sama Angel Lelga yang nggak pakai jilbab?"
R: Masya Allah, itu kecelakaan. Waktu itu ana pas tergoda setan. Sudah, sudah. Jangan ungkit masa lalu, itu tidak baik."
W: "Oh begitu.."
R: "Ada pertanyaan lain? Ana lagi banyak tamu niih.."
W: "Menurut bang Rhoma, apa sih definisi pornoaksi itu?"
R: "Masya Allah, pornoaksi itu haram hukumnya. Pornoaksi adalah suatu tindakan atau perilaku porno yang membuat kita jadi berpikiran kotor. Yang berbuat pornoaksi jelas masuk neraka jahanam!"
W: "Apa konkretnya pikiran kotor itu, Bang?"
R: "Ya..itu pikiran yang ngeres karena pengaruh setan jahanam, yang membuat kita jadi 'terangsang' karena melihat hal-hal seperti itu.."
W: "Maksudnya, apanya yang terangsang, Bang..?"
R: (sambil mesam-mesem) "Ya..itulah...ana jadi malu nih ngomongnya. Antum tahulah itu......."
W: "Ooh...I see. Bisa kasih komentar kenapa Bang Rhoma mengatakan kalau gaya panggung dangdut Inul itu juga pornoaksi?"
R: "Ya..karena Inul itu gerakan 'bokong-nya' memang membuat ana dan akhwan-akhwan semua yang lihat jadi berpikir porno.."
W: "Lho, masak sih Bang?"
R: "Ya..dong..coba antum tanya semua penonton terutama yang cowok-cowok deh.."
W: "Bang, mengapa kalau Bang Rhoma beraksi selalu dengan kemeja bagian atas terbuka..dan keliatan bulu dada Bang Rhoma? Menurut Bang Rhoma, apa itu juga pornoaksi?"
R: "Hmm..ya jelas bukan dong! Itu bukan pornoaksi. Itu sekadar buat gaya saja."
W: "Bagaimana kalau saya bilang sama Bang Rhoma karena liat bulu-bulu dada Bang Rhoma...saya jadi merinding? Maksud saya...lalu saya jadi berpikiran..hmmm..yang gimana gitu sama abang?"
R: (muka merah menahan marah) "Ya kalo gitu..antum gak usah liatbulu dada ana dong!"
W: "Ya kalo gitu..Bang Rhoma juga NGGAK USAH LIAT BOKONG INUL!"
R: @#%&^$8@!&$##******

Rhoma pun mengusir Wina....
he...he...namanya aja wawancara Imajiner!
PeAcE Bro...........

Dahsyatnya sujud bikin otak cerdas!

2006-03-17T19:54:00.000+07:00

Sujud Bikin Cerdas
Salat adalah amalan ibadah yang paling proporsional bagi anatomi tubuh manusia. Gerakan-gerakannya sudah sangat melekat dengan gestur (gerakan khas tubuh) seorang muslim. Namun, perna! hkah terpikirkan manfaat masing-masing gerakan? Sudut pandang ilmiah menjadikan salat gudang obat bagi berbagai jenis penyakit!

Saat seorang hamba telah cukup syarat untuk mendirikan salat, sejak itulah ia mulai menelisik makna dan manfaatnya. Sebab salat diturunkan untuk menyempurnakan fasilitasNya bagi kehidupan manusia. Setelah sekian tahun menjalankan salat, sampai di mana pemahaman kita mengenainya?

TAKBIRATUL IHRAM
Postur: berdiri tegak, mengangkat kedua tangan sejajar telinga, lalu melipatnya di depan perut atau dada bagian bawah.
Manfaat: Gerakan ini melancarkan aliran darah, getah bening (limfe) dan kekuatan otot lengan. Posisi jantung di bawah otak memungkinkan darah mengalir lancar ke s! eluruh tubuh. Saat mengangkat kedua tangan, otot bahu meregang sehingga aliran darah kaya oksigen menjadi lancar. Kemudian kedua
tangan didekapkan di depan perut atau dada bagian bawah. Sikap ini menghindarkan dari berbagai gangguan persendian, khususnya pada tubuh bagian atas.

RUKUK
Postur: Rukuk yang sempurna ditandai tulang belakang yang lurus sehingga bila diletakkan segelas air di atas punggung tersebut tak akan tumpah.
Posisi kepala lurus dengan tulang belakang.

Manfaat: Postur ini menjaga kesempurnaan posisi dan fungsi tulang belakang (corpus vertebrae) sebagai penyangga tubuh dan pusat syaraf. Posisi jantung sejajar dengan otak, maka aliran darah maksimal pada tubuh bagian tengah.
Tangan yang bertumpu di lutut berfungsi relaksasi bagi otot-otot bahu hingga ke bawah. Selain itu, rukuk adalah latihan kemih untuk mencegah gangguan prostat.

I'TIDAL
Postur: Bangun dari rukuk, tubuh kembali tegak setelah, mengangkat kedua tangan setinggi telinga.
Manfaat: Ftidal adalah variasi postur setelah rukuk dan sebelum sujud.
Gerak berdiri bungkuk berdiri sujud merupakan latihan pencernaan yang baik.
Organ organ pencernaan di dalam perut mengalami ! pemijatan dan pelonggaran secara bergantian. Efeknya, pencernaan menjadi lebih lancar.

SUJUD
Postur: Menungging dengan meletakkan kedua tangan, lutut, ujung kaki, dan dahi pada lantai.
Manfaat: Aliran getah bening dipompa ke bagian leher dan ketiak. Posisi jantung di atas otak menyebabkan darah kaya oksigen bisa mengalir maksimal ke otak. Aliran ini berpengaruh pada daya pikir seseorang. Karena itu, lakukan sujud dengan tuma'ninah, jangan tergesa gesa agar darah mencukupi
kapasitasnya di otak. Postur ini juga menghindarkan gangguan wasir.
Khusus
bagi wanita, baik rukuk maupun sujud memiliki manfaat luar biasa bagi kesuburan dan kesehatan organ kewanitaan.

DUDUK
Postur: Duduk ada dua macam! , yaitu iftirosy (tahiyyat awal) dan tawarruk (tahiyyat akhir). Perbedaan terletak pada posisi telapak kaki.
Manfaat: Saat iftirosy, kita bertumpu pada pangkal paha yang terhubung dengan syaraf nervus Ischiadius. Posisi ini menghindarkan nyeri pada pangkal paha yang sering menyebabkan penderitanya tak mampu berjalan.
Duduk tawarruk sangat baik bagi pria sebab tumit menekan aliran kandung kemih (urethra), kelenjar kelamin pria (prostata) dan saluran vas deferens.
Jika dilakukan. dengan benar, postur irfi mencegah impotensi. Variasi posisi telapak kaki pada iftirosy dan tawarruk menyebabkan seluruh otot tungkai turut meregang dan kemudian relaks kembali. Gerak dan tekanan harmonis inilah yang menjaga. kelenturan dan kekuatan organ-organ gerak kita.

SALAM
Gerakan: Memutar kepala ke kanan dan ke kiri secara maksimal.
Manfaat: Relaksasi otot sekitar leher dan kepala menyempurnakan aliran darah di kepala. Gerakan ini mencegah sakit kepala dan menjaga kekencangan kulit wajah.

BERIBADAH secara, kontinyu bukan saja menyuburkan iman, tetapi
mempercantik diri wanita luar dalam.

PACU KECERDASAN
Gerakan sujud dalam salat tergolong unik. Falsafahnya adalah manusia menundukkan diri serendah?rendahnya, bahkan lebih rendah dari pantatnya sendiri. Dari sudut pandang ilmu psikoneuroimunologi (ilmu mengenai kekebalan tubuh dari sudut pandang psikologis) yang didalami Prof Sholeh,
gerakan ini mengantar manusia pada derajat setinggi?tingginya. Mengapa?
Dengan melakukan gerakan sujud secara rutin, pembuluh darah di otak terlatih untuk menerima banyak pasokan darah. Pada saat sujud, posisi jantung berada di atas kepala yang memungkinkan darah mengalir maksimal ke otak. Itu artinya, otak mendapatkan pasokan darah kaya oksigen yang memacu kerja sel-selnya. Dengan kata lain, sujud yang tumakninah dan kontinyu
dapat memacu kecerdasan.

Risetnya telah mendapat pengakua! n dari Harvard Universitry, AS. Bahkan seorang dokter berkebangsaan Amerika yang tak dikenalnya menyatakan masuk Islam setelah diam?diam melakukan riset pengembangan khusus mengenai gerakan sujud.

PERINDAH POSTUR
Gerakan?gerakan dalam salat mirip yoga atau peregangan (stretching).
Intinya untuk melenturkan tubuh dan melancarkan peredaran darah.
Keunggulan salat dibandingkan gerakan lainnya adalah salat menggerakan anggota tubuh lebih banyak, termasuk jari kaki dan tangan.
Sujud adalah latihan kekuatan untuk otot tertentu, termasuk otot dada.
Saat sujud, beban tubuh bagian atas ditumpukan pada lengan hingga telapak tangan. Saat inilah kontraksi terjadi pada otot dada, bagian tubuh yang menjadi kebanggaan wanita. Payudara tak hanya menjadi lebih indah bentuknya tetapi juga memperbaiki fungsi kelenjar air susu di dalamnya.

MUDAHKAN PERSALINAN
Masih dalam pose sujud, manfaat lain bisa dinikmati kaum hawa. Saat pinggul dan pinggang terangkat melampaui kepala dan dada, otot?otot perut (rectus abdominis dan obliquus abdominis externuus) berkontraksi penuh. Kondisi ini melatih organ di sekitar perut untuk mengejan lebih dalam dan lama.
Ini menguntungkan wanita karena dalam persalinan dibutuhkan pernapasan yang baik dan kemampuan mengejan yang mencukupi. Bila, otot perut telah berkembang menjadi lebih besar dan kuat, maka secara alami ia justru lebih elastis. Kebiasaan sujud menyebabkan tubuh dapat mengembalikan serta , mempertahankan organ?organ perut pada tempatnya kembali (fiksasi).

PERBAIKI KESUBURAN
Setelah sujud adalah gerakan duduk. Dalam salat ada dua macam sikap duduk, yaitu duduk iftirosy (tahiyyat awal) dan duduk tawarruk (tahiyyat akhir).
Yang terpenting adalah turut berkontraksinya otot?otot daerah perineum.
Bagi wanita, inilah daerah paling terlindung karena terdapat tiga lubang, yaitu liang persenggamaan, dubur untuk melepas kotoran, dan saluran kemih.

Saat duduk tawarruk, tumit kaki kiri harus menekan daerah perineum.
Punggung kaki harus diletakkan di atas telapak kaki kiri dan tumit kaki kanan harus menekan pangkal paha kanan. Pada posisi! ini tumit kaki kiri akan memijit dan menekan daerah perineum. Tekanan lembut inilah yang memperbaiki organ reproduksi di daerah perineum.

AWET MUDA
Pada dasarnya, seluruh gerakan salat bertujuan meremajakan tubuh. Jika tubuh lentur, kerusakan sel dan kulit sedikit terjadi. Apalagi jika dilakukan secara rutin, maka sel?sel yang rusak dapat segera tergantikan.
Regenerasi pun berlangsung lancar. Alhasil, tubuh senantiasa bugar.

Gerakan terakhir, yaitu salam dan menengok ke kiri dan kanan punya pengaruh besar pada kekencangan. kulit wajah. Gerakan ini tak ubahnya relaksasi wajah dan leher. Yang tak kalah pentingnya, gerakan ini menghindarkan wanita dari serangan migrain dan sakit kepala lainnya.

hidup ini hanya sekali, maka janganlah disia-siakan.
Mari kita kembali kepada niat yang baik.
Insya Alloh akan mendapatkan yang baik pula.....Amien

Critical browsing flaw found in Mac OS X

2006-02-22T18:12:00.000+07:00

A researcher published details and proof of concept code on Tuesday for a critical security flaw in Mac OS X that could allow a malicious Web site to automatically install code on Apple's flagship computers running in their default configuration.

The flaw, found by German researcher Michael Lehn, occurs in how the Mac OS X processes file-association meta data for ZIP files. A malicious Web site could use the flaw to run a program automatically on a visitor's Mac with the context of the user.

Apple's Mac OS X has become the focus of flaw finders and worm writers over the past month. In the last week, virus writers cobbled together two worms that attack Mac OS X and attempt to spread, one through the iChat instant messaging application and the other through Bluetooth connections. Both worms had programming issues and did not spread very successfully.

The latest exploit has not yet been confirmed in the wild, but it is trivial to reproduce, according to several analyses. An attack could be stopped by disabling the "Open safe files after downloading" option in Safari, according to the analyses. (SecurityFocus.com)

Hari minggu yang menyenangkan

2006-02-20T22:41:00.000+07:00

hari minggu kemaren adalah hari minggu pertama kami di korea, rencana kami di korea sampe tgl 3 maret 2006. seperti di jakarta, hari sabtu dan minggu merupakan hari libur di korea. perkantoran dan restoran di sekitar hotel kami menginap pada tutup. hanya beberapa restoran lokal aja yang buka.

waktu pagi sampe siang kami habiskan di kamar hotel untuk sekedar chatting dengan teman di indonesia (kebetulan ada temen ku yang mo berangkat ke perth, aussie, utk acara APRICOT 2006 - Asia Pacific Regional Internet Conferences on Operational Technologies, agung, jgn lupa oleh2nya yah :D ) dan membaca manual handbook training for native language internet address..

setelah makan siang, kami jalan kaki menuju ke gedung parlemen korea, jaraknya hanya 300 meter dari hotel tempat kami menginap. so enakan jalan kaki sambil menikmati udara dingin di jalanan kota seoul. hmm ternyata hari minggu itu ada demonstrasi buruh. gak tau demonstrasi menuntut apa. mungkin salah satu tuntutannya agar menurunkan harga bbm atau tdl kalii ya. wah kalo itu mah demo di jakarta donk...
hehehe ternyata di seoul ada demonstrasi buruh juga loh.

Banyak banget polisi yang berjaga-jaga di sekitar area demonstrasi, yang ternyata di depan gedung parlemen korea. ada sekitar 20-an bis digunakan untuk mengangkut polisi bantuan keamanan tersebut. mereka pada baris di trotoar sampe kami kesulitan juga untuk jalan kaki di trotoar. mereka keliatan masih muda dan ramah loh. mungkin karena mereka belom terhadapan langsung dengan demonstran, coba kalo dah berhadapan langsung dan pegang pentungan. dijamin seratus persen jadi ganas hehhee :)
Sebenernya lama kami tunggu di area demonstrasi, sapa tau akan terjadi tragedi spt tragedi tiananmen di china atau tragedi semanggi di jakarta. tapi setelah sekitar 30 menit ditunggu dan keliatannya para demonstran anteng-anteng aja, kami tinggalin deh tuh para demonstran hehe :)

Kami pilih untuk melanjutkan jalan-jalan ke Hang River, sekitar 300 meter sebelah utara hotel tempat kami menginap. sungai ini cukup lebar, mungkin lebarnya ada 1 km. dan ada banyak jalan yang melintang di atas sungai Hang River ini. kadang juga terliat kapal ferri yang melintas di tengah sungai. sedangkan di seberang sana, pegunungan dan lautan gedung pencakar langit tampak kokoh berdiri menambah pesona kota seoul yang sejuk dan dingin.

Ada banyak pengunjung di Hang River ini. kebanyakan mereka adalah anak2 muda yang bermain sepatu roda dan bersepeda ria. banyak juga yang berfoto-foto ria di sini. hmm ternyata nggak hanya kami yg dari indonesia yg suka pemandangan di tepi Hang River ini, orang lokal sendiri juga pada foto-foto tuh.

Setelah puas berfoto-foto di tepian Hang River, kami menuju ke tempat olah raga ice skating. nah ini yang dicari di korea. bermain skating di atas salju yang putih. lumayan lah, yang penting dah pernah liat salju sebenernya. seumur-umur baru kali ini liat salju. es, putih, dan dingin. banyak anak2 bersama orang tuanya bermain di sini juga. dan mereka sangat gembira menikmati olah raga ini.

Yang paling menarik, dari area ini kami dapat melihat dengan jelas bangunan LG Twin Tower atau menara kembar LG. itu loh perusahaan elektronik dan telekomunikasi korea yang bikin kulkas, AC, tv, komputer, handphone de el el. Sangat jelas dan bener2 menawan deh.

Hayoo sapa yang mo nyusul berkunjung ke korea. gak bakalan nyesel loh hehhe :)

Understanding Unicode

2006-02-20T20:37:00.000+07:00

Some Background on Characters

Before we see what Unicode is, it makes sense to step back slightly to think about just what it means to store "characters" in digital files. Anyone who uses a tool like a text editor usually just thinks of what they are doing as entering some characters—numbers, letters, punctuation, and so on. But behind the scene a little bit more is going on. "Characters" that are stored on digital media must be stored as sequences of ones and zeros, and some encoding and decoding must happen to make these ones and zeros into characters we see on a screen or type in with a keyboard.

Sometime around the 1960s, a few decisions were made about just what ones and zeros (bits) would represent characters. One important choice that most modern computer users give no thought to was the decision to use 8-bit bytes on nearly all computer platforms. In other words, bytes have 256 possible values. Within these 8-bit bytes, a consensus was reached to represent one character in each byte. So at that point, computers needed a particular encoding of characters into byte values; there were 256 "slots" available, but just which character would go in each slot? The most popular encoding developed was Bob Bemers' American Standard Code for Information Interchange (ASCII), which is now specified in exciting standards like ISO-14962-1997 and ANSI-X3.4-1986(R1997). But other options, like IBM's mainframe EBCDIC, linger on, even now.

ASCII itself is of somewhat limited extent. Only the values of the lower-order 7-bits of each byte might contain ASCII-encoded characters. The top 7-bits worth of positions (128 of them) are "reserved" for other uses (back to this). So, for example, a byte that contains "01000001" might be an ASCII encoding of the letter "A", but a byte containing "11000001" cannot be an ASCII encoding of anything. Of course, a given byte may or may not actually represent a character; if it is part of a text file, it probably does, but if it is part of object code, a compressed archive, or other binary data, ASCII decoding is misleading. It depends on context.

The reserved top 7-bits in common 8-bit bytes have been used for a number of things in a character-encoding context. On traditional textual terminals (and printers, etc.) it has been common to allow switching between codepages on terminals to allow display of a variety of national-language characters (and special characters like box-drawing borders), depending on the needs of a user. In the world of Internet communications, something very similar to the codepage system exists with the various ISO-8859-* encodings. What all these systems do is assign a set of characters to the 128 slots that ASCII reserves for other uses. These might be accented Roman characters (used in many Western European languages) or they might be non-Roman character sets like Greek, Cyrillic, Hebrew, or Arabic (or in the future, Thai and Hindi). By using the right codepage, 8-bit bytes can be made quite suitable for encoding reasonable sized (phonetic) alphabets.

Codepages and ISO-8859-* encodings, however, have some definite limitations. For one thing, a terminal can only display one codepage at a given time, and a document with an ISO-8859-* encoding can only contain one character set. Documents that need to contain text in multiple languages are not possible to represent by these encodings. A second issue is equally important: Many ideographic and pictographic character sets have far more than 128 or 256 characters in them (the former is all we would have in the codepage system, the latter if we used the whole byte and discarded the ASCII part). It is simply not possible to encode languages like Chinese, Japanese, and Korean in 8-bit bytes. Systems like ISO-2022-JP-1 and codepage 943 allow larger character sets to be represented using two or more bytes for each character. But even when using these language-specific multibyte encodings, the problem of mixing languages is still present.

What Is Unicode?

Unicode solves the problems of previous character-encoding schemes by providing a unique code number for every character needed, worldwide and across languages. Over time, more characters are being added, but the allocation of available ranges for future uses has already been planned out, so room exists for new characters. In Unicode-encoded documents, no ambiguity exists about how a given character should display (for example, should byte value 0x89 appear as e-umlaut, as in codepage 850, or as the per-mil mark, as in codepage 1004?). Furthermore, by giving each character its own code, there is no problem or ambiguity in creating multilingual documents that utilize multiple character sets at the same time. Or rather, these documents actually utilize the single (very large) character set of Unicode itself.

Unicode is managed by the Unicode Consortium (see Resources), a nonprofit group with corporate, institutional, and individual members. Originally, Unicode was planned as a 16-bit specification. However, this original plan failed to leave enough room for national variations on related (but distinct) ideographs across East Asian languages (Chinese, Japanese, and Korean), nor for specialized alphabets used in mathematics and the scholarship of historical languages.

As a result, the code space of Unicode is currently 32-bits (and anticipated to remain fairly sparsely populated, given the 4 billion allowed characters).

Encodings

A full 32-bits of encoding space leaves plenty of room for every character we might want to represent, but it has its own problems. If we need to use 4 bytes for every character we want to encode, that makes for rather verbose files (or strings, or streams). Furthermore, these verbose files are likely to cause a variety of problems for legacy tools. As a solution to this, Unicode is itself often encoded using "Unicode Transformation Formats" (abbreviated as UTF-*). The encodings UTF-8 and UTF-16 use rather clever techniques to encode characters in a variable number of bytes, but with the most common situation being the use of just the number of bits indicated in the encoding name. In addition, the use of specific byte value ranges in multibyte characters is designed in such a way as to be friendly to existing tools. UTF-32 is also an available encoding, one that simply uses all four bytes in a fixed-width encoding.

The design of UTF-8 is such that US-ASCII characters are simply encoded as themselves. For example, the English letter "e" is encoded as the single byte 0x65 in both ASCII and in UTF-8. However, the non-English "e-umlaut" diacritic, which is Unicode character OxOOEB, is encoded with the two bytes OxC3 OxAB. In contrast, the UTF-16 representation of every character is always at least 2 bytes (and sometimes 4 bytes). UTF-16 has the rather straightforward representations of the letters "e" and "e-umlaut" as 0x65 0x00 and 0xEB 0x00, respectively. So where does the odd value for the e-umlaut in UTF-8 come from? Here is the trick: No multibyte encoded UTF-8 character is allowed to be in the 7-bit range used by ASCII, to avoid confusion. So the UTF-8 scheme uses some bit shifting and encodes every Unicode character using up to 6 bytes. But the byte values allowed in each position are arranged in such a manner as not to allow confusion of byte positions (for example, if you read a file nonsequentially).

Let's look at another example, just to see it laid out. Here is a simple text string encoded in several ways. The view presented is similar to what you would see in a hex-mode file viewer. This way, it is easy to see both a likely on-screen character representation (on a legacy, non-Unicode terminal) and a representation of the underlying hexadecimal values each byte contains:

Hex view of several character string encodings
------------------- Encoding = us-ascii ------------------------
55 6E 69 63 6F 64 65 20 20 20 20 20 20 20 20 20 | Unicode
------------------- Encoding = utf-8 -------------------
55 6E 69 63 6F 64 65 20 20 20 20 20 20 20 20 20 | Unicode
------------------- Encoding = utf-16 ----------------------
FF FE 55 00 6E 00 69 00 63 00 6F 00 64 00 65 00 | U n i c o d e

Declarations

We have seen how Unicode characters are actually encoded, at least briefly, but how do applications know to use a particular decoding procedure when Unicode is encountered? How applications are alerted to a Unicode encoding depends upon the type of data stream in question.

Normal text files do not have any special header information attached to them to explicitly specify type. However, some operating systems (like MacOS, OS/2, and BeOS—Windows and Linux only in a more limited sense) have mechanisms to attach extended attributes to files; increasingly, MIME header information is stored in such extended attributes. If this happens to be the case, it is possible to store MIME header information such as:

Content-Type: text/plain; charset=UTF-8

Nonetheless, having MIME headers attached to files is not a safe, generic assumption. Fortunately, the actual byte sequences in Unicode files provide a tip to applications. A Unicode-aware application, absent contrary indication, is supposed to assume that a given file is encoded with UTF-8. A non-Unicode-aware application reading the same file will find a file that contains a mixture of ASCII characters and high-bit characters (for multibyte UTF-8 encodings). All the ASCII-range bytes will have the same values as if they were ASCII encoded. If any multibyte UTF-8 sequences were used, those will appear as non-ASCII bytes and should be treated as noncharacter data by the legacy application. This may result in nonprocessing of those extended characters, but that is pretty much the best we could expect from a legacy application (that, by definition, does not know how to deal with the extended characters).

For UTF-16 encoded files, a special convention is followed for the first two bytes of the file. One of the sequences 0xFF 0xFE or 0xFE 0xFF acts as small headers to the file. The choice of which header specifies the endianness of a platform's bytes (most common platforms are little-endian and will use 0xFF 0xFE). It was decided that the collision risk of a legacy file beginning with these bytes was small and therefore these could be used as a reliable indicator for UTF-16 encoding. Within a UTF-16 encoded text file, plain ASCII characters will appear every other byte, interspersed with 0x00 (null) bytes. Of course, extended characters will produce non-null bytes and in some cases double-word (4 byte) representations. But a legacy tool that ignores embedded nulls will wind up doing the right thing with UTF-16 encoded files, even without knowing about Unicode.

Many communications protocols—and more recent document specifications—allow for explicit encoding specification. For example, an HTTP daemon application (a Web server) can return a header such as the following to provide explicit instructions to a client:

HTTP/1.1 200 OK
Content-Type: text/html; charset:UTF-8;

Similarly, an NNTP, SMTP/POP3 message can carry a similar Content-Type: header field that makes explicit the encoding to follow (most likely as text/plain rather than text/html, however; or at least we can hope).

HTML and XML documents can contain tags and declarations to make Unicode encoding explicit. An HTML document can provide a hint in a META tag, like:

META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"

However, a META tag should properly take lower precedence than an HTTP header, in a situation where both are part of the communication (but for a local HTML file, such an HTTP header does not exist).

In XML, the actual document declaration should indicate the Unicode encoding, as in:

Other formats and protocols may provide explicit encoding specification by similar means.

Tim Peters, "The Zen of Python"

2006-02-20T20:23:00.000+07:00

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.

Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.

In the face of ambiguity, refuse the temptation to guess.
There should be one—and preferably only one—obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.

Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea—let's do more of those!

Second OS X worm appears

2006-02-19T20:04:00.000+07:00

Just one day after a new OS X Trojan/worm appears, a second worm has appeared that exploits old vulnerabilities in Apple's Bluetooth implementation.

The OSX.Inqtana.A worm is a proof-of-concept worm. Symantec has a description of the worm, which uses a BlueTooth Directory Traversal Vulnerability in OS X that was published on Bugtraq and patched by Apple in June 2005 (Note: SecurityFocus is owned by Symantec Corporation). F-Secure reports that the worm is written in Java. The worm has not been seen in the wild, and additionally is set to stop functioning after February 24th. It is not considered a threat to Mac users.

In other Mac security news, the OSx86 cracking forum has been shutdown, after receiving legal notice from Apple that they had violated the Digital Millennium Copyright Act (DMCA). The project had recently cracked Apple's Intel-based 10.4.4 operating system, which is specifically tied to Apple hardware, to enable it to run on ordinary beige PC clones. Other parts of the project's website remain up. In the process of cracking OS X, hackers discovered polite messages from Apple which included a file named, "Don't Steal Mac OS X.kext" and even a poem asking hackers to be more responsible in their actions:

"Your karma check for today:
There once was a user that whined
his existing OS was so blind,
he’d do better to pirate
an OS that ran great
but found his hardware declined.
Please don’t steal Mac OS!
Really, that’s way uncool.
(C) Apple Computer, Inc."

As Apple transitions its entire line of computers over to faster Intel-based technology, the platform continues to rapidly grow in popularity among hackers and the general population at large. Perhaps not understanding the culture of the Mac and its dedicated followers who purchase the US$129 operating system legitimately, hackers continue to work on getting OS X to run on PC clones for free. (SecurityFocus.com)

Taman Youngdeoungpo Park di Seoul

2006-02-19T08:30:00.000+07:00

Hari Sabtu tanggal 18 Febr 2006 bangun kesiangan, jam 09.34 waktu korea baru terbangun. padahal jadwal breakfast hanya sampe jam 09.00 waktu setempat. so gak kebagian sarapan pagi :(. Tapi gak apa-apa deh. masih ada beberapa bungkus indomie yang emang aku bawa dari indonesia. yah cukup untuk sekedar mengisi perut kosong di pagi hari.

Setelah sarapan mie dan mandi, kami keluar untuk jalan-jalan ke sebelah utara hotel benhur tempat kami menginap. kebetulan di sana ada sebuah gereja yang cukup besar dan luas halamannya. letaknya persis di sisi simpang lima jalan Youngdeoungpo-Gu. gerejanya besar seukuran gedung tujuh lantai. kebetulan pas hari sabtu tersebut, di gereja ada acara pernikahan sebuah keluarga di korea. jadi cukup ramai dan semarak. pikirku pasti seru untuk foto-foto di halaman gereja :). tapi apes, baru dua kali shoot, baterai kamera minta ganti deh. strom abis hehehe.

Kami pun bermaksud untuk mencari toko yang menjual baterai kamera ukuran double A (AA). Sebelumnya emang kami udah diberitahu oleh rekan kami di korea kalo untuk beli berbagai keperluan bisa mencari di toko '7 Eleven'. Nama tokonya emang 7 Eleven. nah pas lagi jalan ke toko tersebut, kami disapa oleh Jay dan Lee Hong (rekan kami di Netpia Korea). Jay adalah instruktur dan trainer kami yang selama kami di korea sangat membantu banget. Nama aslinya Jongsoon An. tapi dia meminta kami memanggilnya Jay. Mungkin biar lebih mudah kami memanggilnya. maklum lidah orang indonesia kan susah banget ngucapin nama dan bahasa korea. apalagi yang gak tau sama sekali bahasa korea :(.
Sedangkan Lee Hong udah pernah ketemu sebelumnya di indonesia. Dia yang bersama Stan Shin (yang menjemput kami di bandara Incheon) dah satu orang pengacara (lupa namanya) yang datang ke indonesia pada pertengahan bulan januari kemaren. Hong Lee ini orangnya tinggi dah gemuk banget. Dia bilang kalo beratnya mencapai 130 kg. cukup berat kan untuk ukuran kita? :).

Akhirnya kamipun ditemani belanja mencari baterai kamera AA di toko 7 Eleven. kami beli 5 biji baterai AA tersebut seharga 3.850 won korea. murah apa mahal yah ?
Karena waktu udah siang dan waktunya makan siang, kami pun diajak makan siang oleh Jay dan Hong. Perlu diketahui pada hari Sabtu dan minggu, banyak restoran, di sekitar hotel kami menginap, yang tutup. Karena emang kawasan hotel tempat kami menginap merupakan kawasan bisnis, jadi aktifitas akan sangat terasa pada hari-hari kerja (senin - jumat). Pada hari-hari kerja tersebut, semua restoran pasti buka dan pada jam makan siang pasti penuh dengan pelanggan.

Setelah beberapa saat mencari, akhirnya kami temukan juga sebuah restoran yang emang selalu buka di hari sabtu dan minggu. letaknya di sebuah gedung lantai dua, tepat di depan KOAMI building tempat Netpia berkantor. Kami berdua memesan menu makan siang daging sapi dan semangkuk nasi. Ada juga beberapa makanan tambahan yang dihidangkan sebagai pelengkap menu makan siang seperti rujak ketimun, irisan ikan laut yang pedas, kubis godok yang dikasih sambal serta telor rebus yang sudah diiris-iris.
Kami makan sambil lesehan yaitu sambil duduk di lantai dan semua menu dihidangkan di meja kecil yang memanjang. di setiap meja sudah disediakan kompor gas yang dibuat untuk memasak menu makan siang kami. jadi emang kami memasak sendiri. bumbu dan porsi daging sapi sudah ditaruh di semacam wajan yang disediakan. kami tinggal memasaknya sampai mendidih. hmmm luar biasa enaknya.
emang orang korea sangat suka makan makanan yang masih mendidih. harus hati-hati makannya. musti ditiup dulu biar panasnya berkurang. kalo gak hati-hati bisa kepanasan deh lidahnya :).
Satu porsi makan siang tersebut harganya 5000 won. karena kami berdua so jadi 10.000 won. pas kami bermaksud membayarnya, ternyata udah dibayarin dulu sama si Hong. Wah makasih banget om Hong. bisa buat ngirit hehe :)

Setelah selesai makan siang, Jay kembali ke kantor Netpia sedangkan Hong mengajak kami jalan-jalan dan menunjukkan kami ke Youngdeoungpo Park. sebuah taman umum di sekitar kantor netpia dan cukup luas juga. mungkin seluas kawasan lembah UGM deh. di sana ada lapangan basket juga. bedanya dengan taman di lembah UGM, kalo di lembah UGM dikelilingi oleh perkampungan penduduk dan beberapa gedung fakultas di UGM, kalo di taman Youngdeoungpo Park ini dikelilingi oleh gedung-gedung pencakar langit yang tinggi dan menawan. dan juga di sini sangat bersih dan tertata rapi. disediakan jalur untuk jalan kaki dan jalur untuk bersepeda. dan ternyata disediakan juga sewa sepeda, jadi yang mau bersepeda berkeliling taman bisa menyewa sepeda tersebut. kami gak sempet menjajal untuk berkeliling dengan sepeda. dah asyik sambil jalan kaki ajah sih :).

Di tengah-tengah taman ada sebuah kolam yang bersih. tapi sayang banget, karena suhunya yang sangat dingin, airnya membeku seperti es. ada ikannya gak yah di bawah air kolam tersebut. hehhe kayanya gak ada deh.

Setelah merasa puas menikmati suasana di taman Youngdeoungpo Park, jam 14.45 kamipun kembali ke kamar hotel. Sampe di kamar hotel, ternyata kamar kami sedang dibersihin oleh dua petugas kebersihan hotel. keduanya perempuan. satu orang asli korea dan satunya lagi badannya tinggi, putih dan hidungnya mancung. pikirku, ini pasti bukan orang korea. Bule. Bule amerika, eropa, atau australia? Tapi masa dia di sini jadi petugas kebersihan?
Pas lagi termangu oleh pikiran tersebut, tiba-tiba dia menyapaku,
"Are you from Indonesia?", sapa dia.
"Yes, I am from Indonesia", jawabku.
Dia balik tanya ke aku, "So you are muslim?"
Langsung aja aku jawab, "Yes, I am muslim"
Dia bilang lagi, "I am also muslim. Assalamu'alaikum"
Wah ternyata dia muslim juga :). Aku jawab salam dia. trus aku tanya dari negara mana dia berasal. Hmm ternyata dia berasal dari Kazakhstan, sebuah negara di kawasan Asia Tengah yang emang mayoritas penduduknya muslim.
Tapi pas aku tanya nama dia, dia kok keliatan kebingungan dan nggak menjawab pertanyaanku. padahal aku cuman tanya "what's your name" :).
Dia malah mengambil satu pack Jahe Wangi made in solo yang aku bawa dari jakarta. dan dia memintanya dariku. ya dengan senang hati aku kasih aja ke dia.

Wah ternyata ada tenaga kerja wanita dari kazakhtan juga yah di korea.
TKW indonesia blom nongol nih :)

Suasana di Kota Seoul ( bukan Suasana di Kota Santri loh )

2006-02-18T01:41:00.000+07:00

Banyak temen loh yang minta oleh-oleh dari Korea. Ada yang pesennya via email dan banyak juga yang pesen via YM. Oleh-olehnya pun macem-macem, dari yang pesen dibeliin notebook second yang murah, handphone noki-a sampe noki-z, bahkan ada yang iseng minta oleh-oleh getuk lindri khas korea hehhe. aneh-aneh kan permintaannya :) Hmm mungkin enaknya kalo pulang bawa rujak ginseng campur sambel petai kalee :)

Lagi musim dingin nih di korea, suhunya masih gak jauh-jauh dari nol derajat celcius. Minggu besok malah katanya bisa sampe minus 8 derajat celcius (kagak kebayang kaya apa dinginnya yah), lebih dingin dari es lah yaw. moga aja bisa liat salju turun dari langit. abis nya bosen di indonesia liat ujan aer mulu. sekali2 boleh kan liat ujan salju he hehehe :).

Benernya sih selama dua hari di korea, suasananya selalu cerah. matahari tanpa malu-malu memancarkan sinarnya dengan terang. langit juga cukup bersih dari awan. hanya beberapa awan saja yang terlihat di atas perbukitan atau gunung di sebelah utara kota seoul yang indah ini.
Namun walopun suasananya cerah, angin yang berhembus cukup kencang juga loh. dan rasa dingin itulah yang sebenernya dateng dari hembusan angin kencang tersebut. hmzzzz dinginnya sampe menusuk tulang dan membuat dada rasanya jadi sesak untuk bernafas, dan tentu saja menggigil kedinginan hemzzzzzz. kulit tangan, muka dan telinga jadi memerah karena menahan rasa dingin yang kuat.

oh iya, tadi malem abis jalan2 looking around the city, kotanya bersih rapi dan tata kotanya bagus. Nggak ada motor, asap kendaraan bermotor, bau got yg menyengat spt di jakarta apalagi sampe liat tikus got :). kagak nemuin. kalo tikus kantor lain lagi ceritanya. banyak juga kali di sini ya...
Penginnya sih jalan2 sampe larut malem, tapi baru sampe jam 22.30 waktu korea dah gak kuat dinginnya. akhirnya balik lagi ke kamar hotel. Oh iya aku menginap di Hotel Benhur (awas jangan salah, bukan Benhill loh :p ). Kalo Benhill mah loe-loe pada dah sering lewat sono di jakarta :)

Di hotel serba electronic dan automatic. Lampu akan nyala dan padam dengan sendiri ketika ada orang masuk atau orang keluar. Pas pertama kali masuk, kaget liat lampu nyala sendiri, kirain ada penunggunya lagi baik hati nyalain lampu utk tamu yg dateng. ternyata nyala otomatis... norak deh gue :))

Yang lebih penting lagi adalah layanan internet gratis dengan unlimited speed di kamar hotel. kenceng boo speednya. kalo donlot file bisa nyampe 400 KB/s loh, padahal itu donlot ke internasional link loh :)
Makanya mumpung lagi dapet koneksi internet cepet, aku pake buat donlot Solaris 10 ( 4 CD, pengin nyoba solaris 10 terbaru katanya Sun sih "it just got better than linux") masing-masing sekitar 400 MB dalam waktu 1 jam dah kedonlot semua. cepet kan?
Kalo di indonesia jgn harap dapet speed segitu, paling banter speednya 10 KB/s jadi bisa seminggu tuh donlot 4 CD nya :). kadang malah donlotnya dah hampir selesai malah koneksinya terputus, kudu ngulang dari awal. nasib deh nasib :p.

Kapan yah Indonesia kita bisa spt Korea? PR lagi deh :)

Perjalanan ke Korea dan Hari Pertama di Korea

2006-02-16T23:53:00.000+07:00

Tanggal 14 Februari 2006 adalah tanggal keberangkatan kami ke korea. Deg-degan juga rasanya mo berangkat ke negeri orang, apalagi ke negeri nun jauh di sana, yang lagi musim dingin lagi. apalagi suhunya sangat ekstrim bagi kita orang indonesia yang notabene masuk kawasan negara2 tropis. Suhunya antara -4 derajat Celcius sampe 1 derajat Celcius. Gak kebayang dinginnya kaya apa yah. Kaya es lah hehhe.

Perlu untuk diketahui, pada bulan februari, korea sedang dilanda musim dingin, karena pengaruh revolusi bumi terhadap matahari dan gerak semu tahunan matahari dari belahan bumi selatan ke belahan bumi utara, korea termasuk negara yang mempunyai empat musim. Musim panas, musim gugur, musim semi dan musim dingin. Yang jelas gak ada musim rambutan di korea apalagi musim jambu monyet :p.
Berdasarkan ilmu geografi yang pernah kita pelajari di bangku SMP, pada bulan februari posisi matahari masih berada di belahan bumi selatan (periode tgl 22 Sept - 23 Maret matahari berada di atas belahan bumi selatan, sebaliknya 23 Maret - 22 Sept matahari berada di atas belahan bumi utara, kalo gak salah loh :)) )
Jadi untuk antisipasi dan biar nggak kedinginan di Korea nantinya, udah disiapkan 3 helai jaket hangat untuk berhangat-hangat ria di suasana yang dingin :p.

Jam 18.15 kami berdua berangkat dari kantor di gedung cyber menuju ke bandara internasional soekarno-hatta, sampe di bandara sekitar jam 18.55 wib, bukan pake ojek tapi pake taksi hehhe.
Karena udah terasa laper, kami sempet makan fried chicken juga di luar bandara, lumayan buat ngisi perut dan makan malam sekalian. apalagi udah kebayang susahnya nyari makanan indonesia di korea. Setelah check-in dengan membayar masing2 rp. 100.000,- dan biaya fiskal masing2 rp. 1.000.000, kami bisa masuk ke bandara dan nunggu pesawat Korean Air dateng.
Menurut jadwal keberangkatan, pesawat akan take off pada pukul 22.15 wib. Jam 21.00 pesawat tiba dari korea dan pada jam 21.45 untuk boardingnya. tepat pada pukul 22.30 15 pesawat molai ambil ancang-ancang untuk take-off menuju seoul, korea selatan. Pesawatnya lumayan gede, mungkin pesawat boeing tipe 757 kalee. Soalnya lebih gede dari garuda indonesia atau adam air yang pernah aku tumpangi pas perjalanan dari jogja - jakarta.
Pesawat take off dengan baik dan mencapai ketinggian stabil pada 10.000 meter di atas laut dengan kecepatan 960 km/jam. Kok aku tau ya? Wong ada tampilan monitor yang menggambarkan posisi kecepatan dan ketinggian pesawat kok. Canggih kan?
Di kursi pesawat juga ternyata tersedia radio penerima untuk mendengarkan siaran radio korea. Itu juga aku tau setelah kami dapat ear phone dari pramugari. Kirain semacam souvenir gratis dari pesawat yang mo bagi2 ear phone gitu, eh pas diperhatiin di bungkusnya ada tulisan "must be returned to ..... (lupa deh)". Setelah di perhatiin ternyata di sisi kiri dan kanan kursi tuh ada output untuk earphone tersebut. Wah baru tau kalo ada radio penerimanya di situ. Norak deh gue :))
Menu makan malem di pesawat lumayan juga, chicken rebus serta nasi khas korea. enak juga loh rasanya hehhe.

Akhirnya setelah menempuh perjalanan selama 6 jam 20 menit, sampe juga kami di korea. Kami mendarat di Incheon International Airport, sekitar 1 jam perjalanan dari Seoul. Lokasi Incheon Airport ini terletak di sebuah pulau kecil, jadi musti nyeberang laut untuk bisa mencapai Seoul.
Karena proses di keimigrasian yang lama, kami kebagian yang terakhir dalam proses pengurusan imigrasi di bandara incheon ini.

Setelah proses keimigrasian beres, terus menuju ke claim baggage untuk nyari tas bawaan kita yang isinya pakaian dan beberapa makanan ringan dari indonesia (spt indomie, jahe wangi, dan stmj :)). Mungkin karena terlalu lama terhenti di proses pengurusan keimigrasian tadi, kami kesulitan mencari tas bawaannya. ditunggu lama kok gak nongol2 tuh tas. kepikir juga jangan2 tas ilang deh digondol orang yg naksir ma tas kita dari indonesia hehe. Sempet dilaporin ke bagian "lost and found" loh. Nah pas lagi ngelaporin itu, tas keliatan di tumpukan di sebelah sisi kanan meja "lost and found". akhirnya gak jadi kehilangan tas deh hehhe.

Setelah itu kami mencari public telepon untuk mencoba menelepon kontak person yang ada di korea. emang katanya sih kita mau dijemput ma orang yang di korea. tapi untuk lebih yakin aja, kita berusaha untuk menelponnya dulu. Ada banyak sih publik telpon cuman pake koin uang korea dan kita gak ada koin. adanya uang won dalam bentuk uang kertas. nah pas lagi mau nukerin uang kertas ke uang koin itulah, mr. stan yang menjemput kami dateng dan menyapa kami. alhamdulillah ..... plong deh rasanya udah ketemu ma orang yang mau jemput kita.

Abis itu kita dibawa oleh stan ke mobilnya, bayar parkir mobilnya 2.400 won dan serba elektronik proses pembayarannya. jadi ada semacam mesin pembayarannya gitu. tinggal pencet tombol sana pencet tombol sini gitu deh :).
Pas pertama kali meliat jalanan dari bandara incheon ke seoul, decak kagum rasanya gak ilang-ilang. jalanan bersih dan tertata rapi serta teratur banget.
Jalan tol mulus dan lebar, mungkin karena masih pagi jadi masih sedikit kendaraan yang berlalu lalang di jalanan. kami melaju dengan kecepatan 140 km/jam, lumayan cepet yah dan melalui jalan tol yang membelah lautan :). mantap boo.

Setelah kurang lebih 30 menit melaju dari bandara incheon akhirnya kami sampe juga di kota seoul, ibu kota korea selatan, sekitar jam 09.55 waktu korea. kami langsung diantar ke hotel tempat kami tinggal selama di korea. Benhur Hotel. Lokasinya deket sama tempat training kami yang juga adalah head office of netpia korea, koami building lantai 11. Setelah mandi dan istirahat sebentar, kami dijemput oleh stan, lee, dan jay untuk diajak makan siang.
Sempet ditanya lebih dulu apa punya pantangan dalam hal makanan. saya bilang asal gak daging babi, anjing, ular, tikus dan daging orang :p serta bukan minuman beralkohol, it's OK. mereka pun mafhum.

akhirnya kami diajak untuk mencoba chicken soup ala korea. 1 ayam utuh untuk 1 orang euy. banyak banget kalo menurut gue. dihidangin sekalian sama tempat ngerebusnya dan masih mendidih lagi. itu emang tradisi orang korea begitu. makan makanan yang masih panas. sampe-sampe lidah ku kepanasan karena saking panasnya hehhehe. makan soupnya pake sendok dan sumpit. sumpitnya pake sumpit besi lagi, gak pake kayu atau bambu :p. itu mah di indonesia kalo pake kayu atau bambu hehhe. di dalem checken soup itu ada nasi koreanya dan ginseng. hampir semua makanan di korea pasti ada ginsengnya.
bagi mereka itu bagus buat nambah kekuatan tubuh. emang betul kan? :)
Abis makan kami diajak ke kantor netpia dan dikenalkan dengan beberapa staf edp dan system development-nya. setelah itu diberikan overview dan skedule utk proses training native language ini.
jadi di hari pertama hanya diberikan pendahuluan dan apa aja materi yang akan diberikan selama training.

karena dah capek nulisnya. cukup dulu sampe di sini deh. apalagi dah larut malem nih, dini hari. jam 03.9 menit waktu korea. musti kudu istirahat dulu biar besok fresh lagi. :)

Permohonan Visa Masuk Korea

2006-02-16T23:20:00.000+07:00

Untuk bisa masuk ke Korea (atau negara lain), yang pasti harus minta visa untuk tinggal sementara di Korea (atau di negara yang bersangkutan). Kalo pasport? Otomatis donk. Untuk ngurus visa harus udah punya pasport lebih dulu kan?

Ngurus visa ternyata nggak semudah yang dibayangkan, apalagi untuk orang Indonesia yang pertama kali ke luar negeri, ke negara yang bukan anggota ASEAN lagi :). Dalam bayangan sih paling lama dua atau tiga hari untuk ngurus permohonan visa-nya. eh ternyata sampe empat hari. Itu saja sempat ditolak empat kali ketika dateng ke kedubes korea untuk minta dibuatkan visa, ada aja dokumen yang kurang lengkap. Asal tau aja, jam buka untuk masukin aplikasi permohonan visa di kedubes korea hanya sampe jam 12.00 wib. Kalo ada dokumen yang kurang lengkap, musti balik dulu ke kantor untuk melengkapinya dan pasti waktunya nggak keburu untuk balik lagi ke kedubes, dipastikan udah lebih dari jam 12.00 wib sih kalo balik lagi. so, pihak kedubes dah nggak mau terima aplikasi permohonan visa. ini berulang sampe 4 kali, bete deh :)
Kasian banget deh gue sampe ditolak sebanyak itu. Padahal hari keberangkatan ke korea dah mepet, sempet putus asa juga loh. Bahkan kepikiran pengin pake jalan pintas, manfaatin orang dalem. Hehe ...ternyata kalo dah mentok begitu, kita masih butuh calo juga yah :p. Tapi setelah menjalani proses permohonan dan memenuhi semua kelengkapan dokumen yang dibutuhkan pihak konsular/kedutaan, akhirnya visa bisa keluar juga / di-approve pada tanggal 13 Februari 2006 kemaren, tanpa pake calo loh (jangan salah yah) hehhe. Kita berangkat pada tanggal 14 Februari-nya loh, soalnya tgl 15 Feb dah kudu di Korea untuk molai trainingnya.

Oh iya, perlu untuk diketahui, di Korea kita training untuk system baru dalam hal internet addressing, yaitu Native Language Internet Address (NLIA). Di buku dokumentasi-nya, orang Korea menyebut sistem baru ini dengan istilah "3rd generation internet domain name". Mirip teknologi selular aja ya pake 3G segala :p.

Solaris 10 Just Got Better

2006-01-26T11:43:00.000+07:00

25.January.2006 -- The Solaris 10 Operating System (Solaris OS) just got better. The newest release of the software includes a host of new features, such as:

* GRUB-based (GRand Unified Bootloader) boot loader for simplification of installation and boot of the Solaris 10 OS on x64/x86 platforms
* Sun Update Connection, which provides immediate access to the latest patches and fixes, or software updates
* Solaris Containers improvements to enable customers to install and update patches dynamically within a Container
* Improved network performance
* Improved memory management
* Updated peripheral support including iSCSI support
* Integrated bug fixes

Simplified Installation and Updating

The Solaris 10 Operating System 1/06 integrates two applications that simplify installing and updating. The popular GRUB boot loader, traditionally used on Linux, simplifies and accelerates the boot process for alternate operating systems from a Solaris system or USB device.
Sun Connection software enables immediate access to Sun Connection Services, so you can get the latest software updates (including security patches and fixes), as they become available.

Market Momentum

Nearly four million people have chosen the Solaris 10 OS since it became available just over a year ago. The list of supporting independent software vendors grows longer each day.

Customers are seeing remarkable performance improvements after deploying the Solaris 10 OS in their environments, due to networking enhancements, a radically improved kernel, special optimizations for memory allocation, and chip multithreading (CMT). The Solaris 10 software's unique Solaris Dynamic Tracing feature (DTrace) yields additional application performance gains by tuning applications.

"We favor Solaris because we've seen it's faster than Linux for the same applications with no changes, especially large memory footprint applications, including simulations and large database cache applications," says Neal Tisdale, vice president of Software Development at NewEnergy Associates, a Siemens Company.

"We also like the features of DTrace and the Sun compilers. These are pulling my development teams over into Solaris."

“We favor Solaris because we've seen it's faster than Linux for the same applications with no changes, especially large memory footprint applications.”
---------------
Neal Tisdale
Vice President of Software Development
NewEnergy Associates, a Siemens Company

A Thriving Ecosystem

Sun continues to support a community of participation in the software space. In addition to making the Sun Java Enterprise System and all of our developer tools available free of charge, we have also committed to opening the source all of our infrastructure software. All of this software is available--at no cost--through the Solaris Enterprise System.

The Solaris Enterprise System includes popular developer tools such as the NetBeans software, the Sun Studio 11 software, and the Sun Java Studio Enterprise software, giving developers powerful choices for creating applications optimized for the Solaris 10 OS. Sun also makes it easier for customers to deploy open source software by supporting popular open source applications such as the Postgres database.

Access the Solaris source code, including the recently released features, the Solaris ZFS (zettabyte file system) and the Solaris Containers for Linux Applications, through OpenSolaris.org.

Get the Solaris OS Today

Download the Solaris 10 OS 1/06 today, free of charge, or order a media kit containing the Solaris Enterprise System software. Because at Sun, we're all about delivering value.

DOA UNTUK KEKASIH HATI

2006-01-26T11:29:00.000+07:00

Allah Yang Maha Pemurah, terima kasih Engkau telah menciptakan dia dan mempertemukan saya dengannya.

Terimakasih untuk saat-saat indah yang boleh kami nikmati bersama.
Terimakasih untuk setiap pertemuan yang boleh kami lalui bersama.
Terimakasih untuk setiap saat-saat yang lalu.
Saya datang bersujud dihadapan-Mu,
Sucikan hati saya yaa Allah, sehingga dapat melaksanakan kehendak dan rencana-Mu dalam hidup saya.

Yaa Allah, jika saya bukan pemilik tulang rusuknya,
janganlah biarkan saya merindukan kehadirannya.
Janganlah biarkan saya melabuhkan hati saya di hatinya.
Kikislah pesonanya dari pelupuk mata saya
dan usirlah dia dari relung hati saya.
Gantilah damba kerinduan dan cinta yang bersemayam di dada ini dengan kasih dari dan pada-Mu yang tulus dan murni.
Tolonglahsaya agar dapat mengasihinya sebagai sahabat.

Tetapi jika Kau ciptakan dia untuk saya, yaa Allah,
tolong satukan hati kami.
Bantulah saya untuk mencintai, mengerti dan menerima dia seutuhnya.
Berikan saya kesabaran, ketekunan, dan kesungguhan untuk memenangkan hatinya.
Urapilah dia agar dia juga mencintai, mengerti dan mau menerima saya
dengan segala kelebihan dan kekurangan saya sebagaimana saya telah Kau ciptakan.
Yakinkanlah dia bahwa saya sungguh-sungguh mencintai dan rela membagi suka dan duka saya dengan dia.

Yaa Allah Maha Pengasih, dengarlah doa saya ini.
Lepaskanlah saya dari keraguan ini menurut kasih dan kehendak-Mu.

Allah Yang Maha Kekal, saya tahu Engkau senantiasa memberikan yang terbaik buat saya.
Luka dan keraguan yang saya alami pasti ada hikmahnya.
Pergumulan ini mengajar saya untuk hidup makin dekat pada-Mu, untuk lebih peka terhadap suara-Mu
yang membimbing saya menuju terang-Mu.
Ajarlah saya untuk tetapsetia dan sabar menanti tibanya waktu yang telah Engkau tentukan.

Jadilah kehendak-Mu dan bukan kehendak saya yang jadi dalam setiap bagian hidup saya, yaa Allah.

Amin....

Alasan orang jawa memberi nama..

2006-01-26T11:15:00.000+07:00

Pandai menanam bunga, diberi nama Rosman.
Pandai memperbaiki mobil, diberi nama Karman.
Pandai main golf, Parman.
Pandai dalam korespondensi, Suratman.
Gagah perkasa, Suparman.
Kuat dalam berjalan, Wakiman.
Berani bertanya, Asman.
Ahli membuat kue, Paiman.
Pandai berdagang, Saliman.
Pandai melukis, Saniman.
Agar jadi orang kaya, Sugiman.
Agar jadi orang yg berbudi luhur, Budiman
Agar besar nanti pandai cari muka, Yasman
Suka begituan, Pakman
Suka makan toge goreng, Togiman
Selalu ketagihan, Tuman
Suka telanjang, Nudiman
Selalu sibuk terus, Bisiman
Biar selalu beruntung .... Lukman
Biar pinter main game .... Giman
Biar bisa sering cuti .... Sutiman
Biar jadi juragan sate .... Satiman
Biar jadi juragan trasi .... Tarsiman
Biar pinter memecahkan problem .... Sukarman
Biar kalau ujian ndak usah mengulang .... Herman
Biar pinter bikin jus .... Yusman
Biar jadi orang yang berwibawa .... Jaiman
Biar jadi pemain musik .... Basman
Biar awet muda .... Boiman
Biar pinter berperang .... Warman
Biar jadi orang Bali .... Nyoman
Biar jadi orang Sunda .... Maman
Biar lincah seperti monyet .... Hanoman
Biar jadi orang Belanda .... Kuman
Biar tetep tinggal di Jogja .... Sleman
Biar jadi tukang sepatu handal .... Soleman
Biar tetep bisa jalan walau ndak pake mesin .... Delman

Debunking the WMF backdoor

2006-01-25T18:08:00.000+07:00

by Thomas C. Greene (SecurityFocus.com)

Claims that the WMF vulnerability was an intentional backdoor into Windows systems makes for an interesting conspiracy theory, but doesn't fit with the facts.
Contrary to a recent rumor circulating on the internet, Microsoft did not intentionally back-door the majority of Windows systems by means of the WMF vulnerability. Although it is a serious issue that should be patched straight away, the idea that it's a secret back door is quite preposterous.

The rumor began when popinjay expert Steve Gibson examined an unofficial patch issued by Ilfak Guilfanov, and, due to his lack of security experience, observed behavior that he could not explain by means other than a Microsoft conspiracy. He then went on to speculate publicly about this via a "This Week in Tech" podcast, and on his own web site. Slashdot grabbed the story, and the result is a fair number of Netizens who now mistakenly believe that the WMF flaw was created with malicious intent.

What it is

We think it's time that this irrational fear is put to rest. First, let's look at how the flaw works: A WMF (Windows Metafile) image can trigger the execution of arbitrary code because the rendering engine, shimgvw.dll, supports the SetAbortProc API, which was originally intended as a means to cancel a print task, say when the printer is busy with a very large job, or the queue is very long, or there is a mechanical problem, and so on. Unfortunately, due to a bit of careless coding, it is possible to cause shimgvw.dll (i.e., the Windows Picture and Fax Viewer) to execute code when SetAbortProc is invoked.

A metafile is essentially a script to play back graphical device interface (GDI) calls when a rendering task is initiated. Unfortunately, and due entirely to Microsoft's carelessness whenever security competes with functionality, it is possible to point the abort procedure to arbitrary code embedded in a metafile.

Gibson could not imagine why WMF rendering should need the SetAbortProc API, since, as he mistakenly believed, WMF outputs to a screen, not a printer. In fact, it can output to a printer as well. But following Gibson's erroneous assumption, the question arose: what would be the point of polling the process and allowing the user, or application, to cancel it?

Having exhausted his imagination on that score, he concluded that there's no good reason for SetAbortProc to be involved in handling metafiles. The more logical explanation, Gibson reckoned, was that someone at Microsoft had deliberately back-doored Windows with this peculiar little stuff-up. And besides, the idea of compromising a computer with an image file seemed quite cloak-and-dagger, adding to the supposed "mystery."

Nothing new here

To anyone well acquainted with Windows security, hence Microsoft's insistence on ease of use whatever the cost, the idea of intentional mischief along these lines is immediately suspect. Microsoft still encourages users to run Windows as administrators, because it believes that logging in is too much trouble for the average point-and-drool civilian. It enables scores of potentially dangerous networking services by default, lest anyone struggle to enable them as needed; and its security scheme for IE - which, instead of distrusting Web content by default, forces the user to decide whose content to trust and whose not to - is essentially a means of skirting responsibility by blaming the victim for the crushing burden of malware they are carrying.

Microsoft has made a pudding of security from its earliest days, and no amount of malicious intent can possibly account for this. The company's obsession with ease of use is more than adequate to account for this and thousands of other security snafus like it.

Furthermore, the WMF flaw doesn't make for a good backdoor, assuming that one would like to target a user, or class of users. For example, IE is not in itself vulnerable; the problem comes when the system renders online WMF files with shimgvw.dll. So luring a Windows user to a malicious web site is no guarantee that they will be affected, while many others, who are not targets, might well be affected. Similarly, when sending a malicious WMF file via e-mail or IM, there is no guarantee that the intended target or targets will be vulnerable. And there are plenty of other types of malicious file that can be sent or placed on line in a similar manner, so there is no distinct advantage to using WMF. It is not a powerful back door.

Finally, Microsoft doesn't need this as a back door; it already has one: Windows Automatic Update. It's got Windows boxes phoning home without user interaction, identifying themselves, and downloading and installing code in the background. Technically speaking, it would not be difficult for the company to pervert this process subtly, and effectively, to target certain machines for malware. But naturally, there is no possibility that it ever will: its actually doing so would be detected, and proved, and the company would end up with the PR debacle of the century. So, yes, there is a back door in Windows, and no, it is not news.

Here Gibson takes his preferred route to getting the ink that he craves: technobabble and innuendo. He can't prove anything (technically, he hasn't got the chops), so he lurks in the gray area between fact and fiction, and generates torrents of fear, uncertainty, and doubt.

The FUD Olympics

Gibson has a bad track record: a history of latching onto arcane issues that he doesn't fully understand and can never prove, and converting his limited understanding into fodder for the next internet melt-down. In mid-2001, when he discovered the SOCK_RAW protocol (which had been implemented in UNIX and Linux for ages) and Microsoft's intent to implement it in Windows XP, he predicted an "XP Christmas of Death" for 2001-2002, which has yet to materialize. Nevertheless, he made such a riot over the issue for so long that Windows XP service Pack 2 disables the function. Naturally, the installed user base of XP machines in botnets remains the same, because the problem was, and is, the ease with which even the most inept script kiddie can own a Windows box. Default configurations are very loose, so there are scores of routes into most Windows systems that require very little knowledge or talent to exploit. Microsoft needs to tighten up thirty or so glaring design and configuration flaws, all right, but raw sockets is not among them.

In 2002, when he discovered SYN floods, he developed a broken gimmick that he called "GENESIS" (Gibson's ENcryption-Enhanced Spoofing Immunity System). He said it was "beautiful and perfect." In fact, it was nothing more than an inept implementation of SYNcookies, which had been developed (in a properly working form) for Linux by Dan Bernstein and Eric Schenk years earlier. Gibson denied that he had ever heard of SYNcookies, and insisted had thought up his own, broken version independently, but this is highly unlikely. Of course, that can't be proved or disproved, keeping the issue in the vague territory that Gibson so comfortably inhabits.

The WMF backdoor very much in keeping with Gibson's history of getting security matters a bit wrong, filling the gaps in his understanding with technobabble, and hyping the actual matter out of all reasonable proportion in his neverending quest of ink.

And here, much as we regret it, we've given him even more ink. We can only hope that it dispels the ridiculous rumor that Gibson has propagated, and thus will do more good than harm.

Blocking sshd throlling

2005-09-30T14:05:00.000+07:00

Dari milisnya OpenBSD-MISC, dijelaskan bagaimana caranya memblock sshd throlling.
Berikut kutipannya:

---------------------------------
List: openbsd-misc
Subject: Re: is there a way to block sshd trolling?
From: Rico
Date: 2005-09-29 19:11:53
Message-ID: 433C3C79.80001 () it ! dk
[Download message RAW]

Hi Nick

I managed to get it working like this..

I am mainly writing this also if other users might benefit from it :-)

In /etc/pf.conf I added only the following line:
block quick on $ext_if inet proto { tcp udp } from to $ext_if

I then placed the following in /root/swatchrc:
watchfor /Invalid user/
mail=root@mydomain.dk, --subject=Hacking alert! We have an illegal
login attempt!
exec pfctl -t sshdhackers -T add $10

This means that I will get an email notification plus pfctl will add the
illegal IP to the sshdhackers tabel.

In my case I only want to block illegal users since I am using
AllowUsers with SSHD, and because I don't want to risk blocking someone
who might have forgotten his/hers password. This could be extended to
block the user if he or she fails at X attempts. Swatch then needs to be
looking for "Failed password for USER" where user is the right username.
This actually is a good idea to block in case some script kid gets hes
hands on the right username.

In /etc/rc.local I have placed the following line:
/usr/local/bin/swatch -c /root/swatchrc -t /var/log/authlog

If one wants to see the IP in sshdhackers it can be done with:
pfctl -t sshdhackers -T show
And if one needs to delete an IP:
pfctl -t sshdhackers -T delete xxx.xxx.xxx.xxx
Where xxx.xxx.xxx.xxx is the IP.

To get swatch to add the illegal entry to it's own logging file say
/root/swatchlog (as Nick used) I add this entry in /root/swatchrc after
the "exec pfctl" line:
exec echo $0 >> /root/swatchlog

And if you only want the IP to be logged:
exec echo $10 >> /root/swatchlog

In case someone don't know: $10 means the tenth word in the line (which
in authlog is the IP).

Hope others might benefit.

Cheers.
Rico.

--------------------------

Thanks Rico