Username dan Password Speedy Groovia Huawei HG532e

Mau sedikit sharing tentang speedy dengan paket tv groovia dengan menggunakan router huawei HG532e. Jadi ketika saya sudah dipasangkan oleh petugas dari telkom, saya penasaran untuk memasuki router huawei tersebut. Tapi anehnya kok saya cuman dapat menu 'admin' yang minimize banget. Terpikir dibenak saya jika sistem router huawei HG532e ini telah dimodifikasi firmware nya oleh pihak telkom. Kemudian saya mencoba googling dan menemukan beberapa tulisan bagus di kaskus dan josh.rootbrain.com.

Memang ternyata pihak telkom mengunci hak akses user dengan nama "support". Berikut ini daftar user2 di router tersebut :

username : admin

password : admin

username : support

password : theworldinyourhand

Kemudian segera saya rubah untuk kedua hak akses user2 tersebut agar tidak dimasuki oleh pihak yang tidak bertanggung jawab. Selanjutnya saya mengikuti saran dari kaskus dan Pak Josua agar menonaktifkan ssid wifi yang diaktifkan oleh settingan default telkom. Untuk menonaktifkannya, teman2 harus menggunakan akun 'support'.

Jika sudah masuk menu support, maka pilih "Basic ---> WLAN"

Saran saya yang diaktifkan hanya SSID Index : SSID1 saja dan SSID 2-4 dinonaktifkan dengan cara mencentang kotak enabled ssid seperti gambar diatas.

Untuk SSID1, mohon agar lebih aman wifi kita gunakan security WPA-PSK/WPA2-PSK di menu tersebut dan isikan key yang terdiri dari angka,huruf dan spesial karakter untuk best practice nya saja (usahakan berwarna hijau jangan merah saat menginputnya). Berikut ini contohnya :

WPA pre-shared key : run994%man

WPA encryption : TKIP+AES

Selanjutnya ke settingan Basic --> WAN

Seperti gambar diatas, saya melakukan penonaktifan dua koneksi WAN bawaan default ini router dikarenakan saya tidak mengetahui kegunaan profile yang pertama dan keempat. Jika temen2 menggunakanTV groovia, maka wajib dan kudu menggunakan port LAN nomor 3 dan 4 karena di firmware huaweinya sudah di setting seperti itu dan jika kita memindahkan LAN groovia ke port 1 dan 2, maka akan muncul tulisan seperti ini :

Error EPG dan silahkan kontak 147

Jadi ketika saya mencoba memindahkan ke port2 lain tidak bisa dan disimpulkan bahwa port LAN 1 dan 2 adalah untuk koneksi internet dan port LAN 4 itu untuk TV Groovia. Mungkin jika mau lebih dalam lagi, temen2 bisa mengoprek source code dengan menggunakan plugin di firefox seperti "firebug" atau yg lainnya. Sebenarnya kita bisa meng-custom port lan yang kita mau gunakan tinggal mencentang2 port lan tersebut pada menu router huawei tersebut. Intinya untuk settingan internet menggunakan connection type "PPPoE" sedangkan TV Groovia menggunakan "Bridge". Jika anda mau melihat username PPPoE roter anda, tinggal search di source code untuk penggunaan username dan password (jika saya username ada di line 278 col 1400), berikut contoh punya saya (sedikit sensor):

var WANPPP = new Array(new WanPPPConstruction

"InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.

WANPPPConnection.1","1","Connected","IP_Routed",

"INTERNET_TR069_R_0_35","300","1","1221xxxxxxxx@telkom.net",

"0","AUTO","1xx.xx1.xx4.xx","1xx.xx1.xx4.xx",

"1xx.xx1.xx4.xx,2xx.xx3.xx4.xx",

"AlwaysOn","InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.1,

InternetGatewayDevice.LANDevice.1.WLANConfiguration.1,InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.2",

"INTERNET_TR069","0","1492","1492","0","A4:99:47:EE:00:18","0","1","0","PendingDisconnect","SLAAC","","0","","","",""),new WanPPPConstruction

("InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANPPPConnection.1","1","Connected","PPPoE_Bridged","OTHER_B_8_88","0","0","","1","AUTO","","","","AlwaysOn",

"InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.3,InternetGatewayDevice.LANDevice.1.LANEthernetInterfaceConfig.4","OTHER","1","1492","1492","0",

"A4:99:47:EE:00:19","0","1","0","PendingDisconnect","SLAAC","","0","","","",""),new WanPPPConstruction("InternetGatewayDevice.WANDevice.1.WANConnectionDevice.3.WANPPPConnection.1",

"0","PendingDisconnect","PPPoE_Bridged","INTERNET_B_7_77","0","0","","1","AUTO","","","","AlwaysOn","InternetGatewayDevice.LANDevice.1.WLANConfiguration.2","INTERNET",

"1","1492","1492","0","A4:99:47:EE:00:1A","0","1","0","PendingDisconnect","SLAAC","","0","","","",""),null);

Selanjutnya untuk menghindari di flood atau dDos Attack router anda, maka aktifkan fitur "Advance -- Firewall -- Dos Attack", centang ketiga pilihan tersebut: CMP flooding, SYN flooding dan ARP attack.

Terakhir adalah settingan yang ane rasa aneh adalah di menu "Advance -- CWMP -- TR069 dan TR111". Jika tidak salah itu adalah fasilitas remote management via WAN. Nah jika kita mau ekstrim, kita matikan saja ke dua menu tersebut di router kita karena jujur secara pribadi saya kurang suka dengan adanya hak akses ini karena kita sebagai user awam tidak diberitahukan oleh pihak telkom untuk apa kedua menu tersebut. Mungkin alasan mereka ingin melakukan upgrade firmware nantinya jika ada update patch. Xixiiixii itu sih pendapat saya loh.

Jika settingan seperti diatas sudah dilakukan, segera lakukan backup configuration tersebut di menu "Maintenance > Device > Configuration File > Download". Jangan lupa disimpan ditempat yang aman yah brother.

Intinya dari semua itu adalah, kita harus berani mengoprek setiap peralatan yang diberikan oleh pihak ketiga dan jangan malu bertanya ke mbah google atau langsung telfon si pihak ketiga tersebut tapi kayanya klo kita telfon pasti mereka akan ga mau membeberkan semuanya deh, xixixii peace. Jika dari saya sendiri, saya menonaktifkan fungsi WLAN / Wifi di router huawei HG532e tersebut dan hanya mengaktifkan port TV groovia saja. Untuk share wifi nya saya lebih mempercayakan WRT54GL dengan firmware tomato karena saya lebih familiar dan lebih asik konfigurasinya.

Jika terdapat kesalahan atau menyinggung dari pihak2 tertentu, saya sebelumnya mohon maaf karena disini saya cuman sharing saja dan tidak mau menjelekkan pihak manapun. Mencerdaskan anak bangsa adalah sebuah tugas mulia bagi hidup saya.

Sumber Tulisan :
http://www.kaskus.co.id/thread/523d8cb7f8ca173d2800000e/panduan-menghilangkan-wifiid-multiuser-remote-cwmp-modem-speedy/1

http://josh.rootbrain.com/blog/2013/01/16/modem-adsl-wireless-bisa-menjadi-ancaman-keamanan-internetintranet/

http://en.wikipedia.org/wiki/TR-069

http://www.broadband-forum.org/technical/download/TR-111.pdf

Program Doktor (S3) Universitas Gunadarma

Berdasarkan surat Nomor 3716/D/T/2002 tertanggal 27 Desember 2002 dan bekerjasama dengan Universite De Bourgogne, Perancis, Universitas Gunadarma membuka program studi Teknologi Informasi untuk jenjang Program Doktor (S3). Program ini memberikan kesempatan bagi mahasiswa untuk bekerja bersama para ahli yang berpengalaman melakukan penelitian di bidang Teknologi Informasi terkini seperti Sistem Basis Data, Image Processing (Pengolah Citra), dan Pemodelan Simulasi.

Secara ringkas dapat dikatakan bahwa visi yang mendasari penyelenggaraan Program Doktor Teknologi Informasi Universitas Gunadarma ini adalah suatu tekad untuk mengembangkan ilmu pengetahuan bidang Teknologi Informasi/Ilmu Komputer dengan memberikan kemampuan penelitian yang tinggi kepada para mahasiswa serta memberikan wawasan yang mendalam mengenai suatu bidang disiplin ilmu.

Sebagai langkah awal, pendidikan Program Doktor yang diselenggarakan dirancang dengan cara menempatkan pengetahuan sebagai ujung tombak. 

Berdasarkan itu, diharapkan terbuka kesempatan bagi mahasiswa untuk mengembangkan kemampuan profesionalnya dalam berbagai kekhususan bidang Teknologi Informasi.

CALON MAHASISWA
 

Para calon mahasiswa yang akan mengikuti Program pendidikan Doktor ini, pada tahap awal adalah para lulusan Program Magister bidang Ilmu Teknologi Informasi/Ilmu Komputer atau yang berdekatan, diantaranya Magister Komputer, Magister Sistem Informasi atau yang berdekatan, Magister Teknik Elektro, Magister Matematika/Statistika.

Dengan perkembangan teknologi informasi pada berbagai bidang, maka calon mahasiswa dimungkinkan dari bidang lain dengan pertimbangan khusus. Untuk menampung aspirasi calon, penerimaan mahasiswa dengan beban penuh diatur dua angkatan untuk setiap tahun akademik, yaitu bulan Agustus dan Februari.

PENERIMAAN MAHASISWA BARU
 

Persyaratan penerimaan mahasiswa Program Doktor Teknologi Informasi Universitas Gunadarma adalah sebagai berikut :
A. Syarat Akademik :

1. Memiliki ijazah S2 perguruan tinggi dalam Negeri ataupun Luar negeri yang ijazahnya telah diakui oleh Direktur Jenderal Pendidikan Tinggi Depdiknas.

2. Memiliki Indeks Prestasi Kumulatif S2 minimum 3,00.

B. Syarat Penerimaan :

1. Mendaftarkan diri dengan mengisi formulir pendaftaran yang disediakan di Sekretariat Program Doktor Teknologi Informasi Universitas Gunadarma.

2. Lulus seleksi yang ditetapkan oleh panitia penerimaan mahasiswa Program Doktor Teknologi Informasi Universitas Gunadarma yang meliputi :
a. Tes Potensial Akademik
b. Tes Bahasa Inggris (setara TOEFL dengan nilai minimum 500)
c. Tes Wawancara

3. Memperoleh rekomendasi dari Guru Besar atau pakar bidang Teknologi Informasi/Ilmu Komputer.

4. Melengkapi/memenuhi semua persyaratan yang ditetapkan oleh panitia penerimaan mahasiswa program Doktor.

BIAYA PENDIDIKAN
 

Biaya pendidikan S3 Gunadarma, terdiri dari beberapa komponen, sebagai berikut :
a. Biaya Pendaftaraan dan seleksi masuk sebesar Rp. 300.000,-
b. Biaya Pendidikan/Uang Kuliah per semester :
- Untuk 6 semester pertama sebesar Rp. 30.000.000,- per semester
- Untuk semester-semester berikutnya sebesar Rp. 10.000.000,- per semester
c. Biaya Ijazah dan wisuda sebesar Rp. 500.000,-

Download file lengkapnya :

https://mega.co.nz/#!EpRhkAqY!UfmNynJgzEaswbQaiUKKKh8bmXwh_TcRhe5EkL6dwyQ

Slowloris HTTP DoS

CCCCCCCCCCOOCCOOOOO888@8@8888OOOOCCOOO888888888@@@@@@@@@8@8@@@@888OOCooocccc::::
CCCCCCCCCCCCCCCOO888@888888OOOCCCOOOO888888888888@88888@@@@@@@888@8OOCCoococc:::
CCCCCCCCCCCCCCOO88@@888888OOOOOOOOOO8888888O88888888O8O8OOO8888@88@@8OOCOOOCoc::
CCCCooooooCCCO88@@8@88@888OOOOOOO88888888888OOOOOOOOOOCCCCCOOOO888@8888OOOCc::::
CooCoCoooCCCO8@88@8888888OOO888888888888888888OOOOCCCooooooooCCOOO8888888Cocooc:
ooooooCoCCC88@88888@888OO8888888888888888O8O8888OOCCCooooccccccCOOOO88@888OCoccc
ooooCCOO8O888888888@88O8OO88888OO888O8888OOOO88888OCocoococ::ccooCOO8O888888Cooo
oCCCCCCO8OOOCCCOO88@88OOOOOO8888O888OOOOOCOO88888O8OOOCooCocc:::coCOOO888888OOCC
oCCCCCOOO88OCooCO88@8OOOOOO88O888888OOCCCCoCOOO8888OOOOOOOCoc::::coCOOOO888O88OC
oCCCCOO88OOCCCCOO8@@8OOCOOOOO8888888OoocccccoCO8O8OO88OOOOOCc.:ccooCCOOOO88888OO
CCCOOOO88OOCCOOO8@888OOCCoooCOO8888Ooc::...::coOO88888O888OOo:cocooCCCCOOOOOO88O
CCCOO88888OOCOO8@@888OCcc:::cCOO888Oc..... ....cCOOOOOOOOOOOc.:cooooCCCOOOOOOOOO
OOOOOO88888OOOO8@8@8Ooc:.:...cOO8O88c.      .  .coOOO888OOOOCoooooccoCOOOOOCOOOO
OOOOO888@8@88888888Oo:. .  ...cO888Oc..          :oOOOOOOOOOCCoocooCoCoCOOOOOOOO
COOO888@88888888888Oo:.       .O8888C:  .oCOo.  ...cCCCOOOoooooocccooooooooCCCOO
CCCCOO888888O888888Oo. .o8Oo. .cO88Oo:       :. .:..ccoCCCooCooccooccccoooooCCCC
coooCCO8@88OO8O888Oo:::... ..  :cO8Oc. . .....  :.  .:ccCoooooccoooocccccooooCCC
:ccooooCO888OOOO8OOc..:...::. .co8@8Coc::..  ....  ..:cooCooooccccc::::ccooCCooC
.:::coocccoO8OOOOOOC:..::....coCO8@8OOCCOc:...  ....:ccoooocccc:::::::::cooooooC
....::::ccccoCCOOOOOCc......:oCO8@8@88OCCCoccccc::c::.:oCcc:::cccc:..::::coooooo
.......::::::::cCCCCCCoocc:cO888@8888OOOOCOOOCoocc::.:cocc::cc:::...:::coocccccc
...........:::..:coCCCCCCCO88OOOO8OOOCCooCCCooccc::::ccc::::::.......:ccocccc:co
.............::....:oCCoooooCOOCCOCCCoccococc:::::coc::::....... ...:::cccc:cooo
 ..... ............. .coocoooCCoco:::ccccccc:::ccc::..........  ....:::cc::::coC
   .  . ...    .... ..  .:cccoCooc:..  ::cccc:::c:.. ......... ......::::c:cccco
  .  .. ... ..    .. ..   ..:...:cooc::cccccc:.....  .........  .....:::::ccoocc
       .   .         .. ..::cccc:.::ccoocc:. ........... ..  . ..:::.:::::::ccco

Welcome to Slowloris - the low bandwidth, yet greedy and poisonous HTTP client!

Written by RSnake with help from John Kinsella, IPv6 version by Hugo Gonzalez and a dash of inspiration from Robert E Lee.

UPDATE 3: IPv6 version provided by Hugo Gonzalez.

UPDATE 2: Video presentation of Slowloris at DefCon (the middle section of the presentation) can be seen here: Hijacking Web 2.0 Sites with SSLstrip and SlowLoris -- Sam Bowne and RSnake at Defcon 17.

UPDATE: Amit Klein pointed me to a post written by Adrian Ilarion Ciobanu written in early 2007 that perfectly describes this denial of service attack. It was also described in 2005 in the "Programming Model Attacks" section of Apache Security. So although there was no tool released at that time these two still technically deserves all the credit for this. I apologize for having missed these.

In considering the ramifications of a slow denial of service attack against particular services, rather than flooding networks, a concept emerged that would allow a single machine to take down another machine's web server with minimal bandwidth and side effects on unrelated services and ports. The ideal situation for many denial of service attacks is where all other services remain intact but the webserver itself is completely inaccessible. Slowloris was born from this concept, and is therefore relatively very stealthy compared to most flooding tools.

Slowloris holds connections open by sending partial HTTP requests. It continues to send subsequent headers at regular intervals to keep the sockets from closing. In this way webservers can be quickly tied up. In particular, servers that have threading will tend to be vulnerable, by virtue of the fact that they attempt to limit the amount of threading they'll allow. Slowloris must wait for all the sockets to become available before it's successful at consuming them, so if it's a high traffic website, it may take a while for the site to free up it's sockets. So while you may be unable to see the website from your vantage point, others may still be able to see it until all sockets are freed by them and consumed by Slowloris. This is because other users of the system must finish their requests before the sockets become available for Slowloris to consume. If others re-initiate their connections in that brief time-period they'll still be able to see the site. So it's a bit of a race condition, but one that Slowloris will eventually always win - and sooner than later.

Slowloris also has a few stealth features built into it. Firstly, it can be changed to send different host headers, if your target is a virtual host and logs are stored seperately per virtual host. But most importantly, while the attack is underway, the log file won't be written until the request is completed. So you can keep a server down for minutes at a time without a single log file entry showing up to warn someone who might watching in that instant. Of course once your attack stops or once the session gets shut down there will be several hundred 400 errors in the web server logs. That's unavoidable as Slowloris sits today, although it may be possible to turn them into 200 OK messages instead by completing a valid request, but Slowloris doesn't yet do that.

HTTPReady quickly came up as a possible solution to a Slowloris attack, because it won't cause the HTTP server to launch until a full request is recieved. This is true only for GET and HEAD requests. As long as you give Slowloris the switch to modify it's method to POST, HTTPReady turns out to be a worthless defense against this type of attack.

This is NOT a TCP DoS, because it is actually making a full TCP connection, not a partial one, however it is making partial HTTP requests. It's the equivalent of a SYN flood but over HTTP. One example of the difference is that if there are two web-servers running on the same machine one server can be DoSed without affecting the other webserver instance. Slowloris would also theoretically work over other protocols like UDP, if the program was modified slightly and the webserver supported it. Slowloris is also NOT a GET request flooder. Slowloris requires only a few hundred requests at long term and regular intervals, as opposed to tens of thousands on an ongoing basis.

Interestingly enough, in testing this has been shown in at least one instance to lock up database connections and force other strange issues and errors to arise that can allow for fingerprinting and other odd things to become obvious once the DoS is complete and the server attempts to clean itself up. I would guess that this issue arises when the webserver is allowed to open more connections than the database is, causing the database to fail first and for longer than the webserver.

Slowloris lets the webserver return to normal almost instantly (usually within 5 seconds or so). That makes it ideal for certain attacks that may just require a brief down-time. As described in this blog post, DoS is actually very useful for certain types of attacks where timing is key, or as a diversionary tactic, etc....

This affects a number of webservers that use threaded processes and ironically attempt to limit that to prevent memory exhaustion - fixing one problem created another. This includes but is not necessarily limited to the following:

• Apache 1.x
• Apache 2.x
• dhttpd
• GoAhead WebServer
• WebSense "block pages" (unconfirmed)
• Trapeze Wireless Web Portal (unconfirmed)
• Verizon's MI424-WR FIOS Cable modem (unconfirmed)
• Verizon's Motorola Set-Top Box (port 8082 and requires auth - unconfirmed)
• BeeWare WAF (unconfirmed)
• Deny All WAF (unconfirmed)

There are a number of webservers that this doesn't affect as well, in my testing:

• IIS6.0
• IIS7.0
• lighttpd
• Squid
• nginx
• Cherokee (verified by user community)
• Netscaler
• Cisco CSS (verified by user community)

This is obviously not a complete list, and there may be a number of variations on these web-servers that are or are not vulnerable. I didn't test every configuration or variant, so your mileage may vary. This also may not work if there is an upstream device that somehow limits/buffers/proxies HTTP requests. Please note though that Slowloris only represents one variant of this attack and other variants may have different impacts on other webservers and upstream devices. This command should work on most systems, but please be sure to check the options as well:

perl slowloris.pl -dns example.com

Requirements: This is a Perl program requiring the Perl interpreter with the modules IO::Socket::INET, IO::Socket::SSL, and GetOpt::Long. Slowloris works MUCH better and faster if you have threading, so I highly encourage you to also install threads and threads::shared if you don't have those modules already. You can install modules using CPAN:

perl -MCPAN -e 'install IO::Socket::INET'
perl -MCPAN -e 'install IO::Socket::SSL'

The IPv6 version needs:

perl -MCPAN -e 'install IO::Socket::INET6'
perl -MCPAN -e 'install IO::Socket::SSL'

Windows users: You probably will not be able to successfuly execute a Slowloris denial of service from Windows even if you use Cygwin. I have not had any luck getting Slowloris to successfuly deny service from within Windows, because Slowloris requires more than a few hundred sockets to work (sometimes a thousand or more), and Windows limits sockets to around 130, from what I've seen. I highly suggest you use a *NIX operating system to execute Slowloris from for the best results, and not from within a virtual machine, as that could have unexpected results based on the parent operating system.

Version: Slowloris is currently at version 0.7 - 06/17/2009 and 0.7.1 (IPv6 version) - 04/02/2013

Download: slowloris.pl or slowloris6.pl (IPv6 version)

Getting started: perldoc slowloris.pl or perldoc slowloris6.pl

Issues: For a complete list of issues look at the Perl documentation, which explains all of the things to think about when running this denial of service attack.

Thanks: Thank you to John Kinsella for the help with threading and id and greyhat for help with testing. Big thanks to Hugo Gonzalez for IPv6 too!

SOURCE:
http://ha.ckers.org/slowloris/