How to Remove Hacked By Godzilla

Kaedah Membuang Menggunakan Registry.

1. Klik pada butang start dan tekan run . dalam kotak run taip regedit.

2. Satu Kotak editor akan muncul klik pada HKEY_LOCAL_MACHINE\SOFTWARE .klik dua kali

3. Kemudian car i software dan klik 2 kali HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft

4. Kemudian pilih interner explorer dan klik dua kali HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer

5. Dan cari perkataan main , kemudian klik perkataan tersebut dan lihat pada sebelah kanan dan cari perkataan window title , right klik dan pilih modify kemudian delete perkataan yang ada pada string tersebut.

Selepas buang perkataan tersebut dan restart pc.

Untuk maklumat yang lain boleh cari di sini http ://www.technixupdate.com/how-to-remove-hacked-by-godzilla-virus-in-5-minutes/

Bagaimana untuk berceramah?

Oleh mesrarakyat

Artikel daripada Tranungkite.com

Bagaimana untuk berceramah?


Artikel ini ditujukan kepada rakanku di JAKIM, JAWI, TH,guru-guru dan apa jua jenis profesion anda. Yang penting, tujuannya untuk berceramah terutama ceramah umum atau khas yang telah di tetapkan oleh penganjur. Yang pasti, kuliah dan ceramah adalah dua perkara berlainan.



Bagaimana ingin memulakan teks ceramah?


Yang pertama, pastikan kita dapatkan tajuk dari penganjur ataupun kita yang bebas memilih tajuk. Kita ambil contoh ‘Peranan Ilmu Kepada Manusia’. Nampak mudah tetapi bagi yang tidak pernah berceramah, tentulah ia perkara yang amat berat.



Penulisan Teks Ceramah


Bagaimana seseorang itu boleh bercakap 2 jam tanpa rasa letih ataupun tanpa menjemukan pendengar-pendengar? Mestilah ceramah tersebut penuh dengan isi ditambah pula dengan isi yang dapat menarik pendengar tersebut seperti isu-isu terbaru, perkara yang sudah menjadi budaya dan sebagainya. Ini terpulang kepada kebijaksanaan penceramah itu sendiri.


Mari kita tulis lakaran teks ceramah. Hanya memerlukan kertas A4 yang di lipat empat ataupun buku nota kecil (jangan guna buku 555, low class!)



TAJUK: Peranan Ilmu Kepada Manusia

MASA : 1 jam

PENDENGAR : Penduduk Kg Aman Sentosa



Kita perlu bahagikan kepada 3 perkara :



1-PENDAHULUAN (10 min)

2-ISI (40 min)

3-PENUTUP (10 min)


Oleh kerana sejam 60 minit maka 3 perkara di atas hanya memerlukan pembahagian minit untuk anda berceramah setiap perkara tersebut.



Contoh PENDAHULUAN :


Pembukaan dengan kalimah tauhid – spt Asyhadualla la ilaha illa Allah.. (3 min)

Takrif Ilmu – ringkas (3 min)

Pembahagian ilmu kepada baik dan buruk (4 min)


Jika dirujuk dari isi pendahuluan di atas maka anda sudah nampak apakah isi yang perlukan anda beri penekanan. Ini terpulang kepada bahasa anda, samada anda menggunakan audien untuk soal jawab seperti “Siapa boleh beritahu ustaz, ilmu itu terbahagi kepada berapa bahagian..??”


PERINGATAN : Anda Hendaklah Berdisiplin Mematuhi Masa Yang Anda Sendiri Tetapkan Supaya Tidak Terkurang. Jika Terlebih, Itu Bonus Buat Anda.



Mari kita lihat teks ISI pula :



Contoh ISI ‘Peranan Ilmu..’ :



1-kenal pencipta ( 10 min)

1.1 ilmu tauhid – kenal siapa tuhan (5 min) – beza dengan orang bukan islam

1.2 pelbagai ilmu ada manfaatnya (5 min) – ilmu perubatan ada faedah, ilmu falak ada faedah.



2-selamat dari kekufuran ( 10 min)
2.1 tahu membezakan yang mana iman atau kufur – cthnya ilmu sihir (5 min)

2.2 menjauhkan perkara yang boleh menjatuhkan akidah – cthnya dengan ilmu, kita tahu mana yang patut dijauhi seperti menghina Rasulullah (5 min)



3. Allah beri kemudahan penuntut ilmu (20 min)

3.1 penuntut ilmu di doakan oleh segenap makhluk Allah (5 min) – hadis

3.2 penuntut ilmu di mendapat darjat yang tertinggi (5 min) – alQuran

3.3 penuntut ilmu di kenang sepanjang zaman (5 min) –

3.4 penuntut ilmu yang mengajar (5 min) - amal jariah yang besar



Oleh itu, masa untuk ISI adalah 40 minit.



Akhirnya kita lihat PENUTUP :



Kesimpulan tajuk ilmu (5 min)

Doa – semoga menjadi orang yang berilmu (5 min)


Sudah selesai! Anda akan dapati masa di atas nampak sudah menjadi singkat. Dan, siapa yang telah biasa buat cara begini masanya sentiasa di penuhi dengan ceramah dan ditambah pula jika isi menarik.



Bagaimana pula memasukkan ayat alQuran dan hadith?


Biasanya, penceramah hendaklah terlebih dahulu menghafaz ayat atau matan hadith demi memudahkan dan melancarkan isi tersebut. Jika tidak pun, catatkan di hujung kertas tersebut agar ia semakin kuat di ingatan kita."

Fundamentals: Five ways to secure your Cisco routers and switches

Article taken from TechRepublic

• Date: April 3rd, 2008
• Author: David Davis

Recently, Cisco Subnet blogger Brad Reese wrote the article, “Expert warns of scam to blackmail companies for cash to get back access to their Cisco routers.” In that post, he wrote about hackers who manage to hijack a company’s routers and then extort money from them by threatening to take down the network. The hackers were able to obtain control of the network because of poorly written Cisco IOS ACLs, easily guessed passwords, and unencrypted SNMP community strings (or easily guessed community strings).
Don’t let this happen to you and your network. Here are my top five best practices to secure your routers, your network, and your company from malicious attacks.

1. Understand the basics of router security

You must understand the basics of router security. Here are the essentials:
Physically secure the routers
If your routers are not physically secured, anyone can walk up, perform a password reset, and gain full access to that router’s configuration. Even if this isn’t a core router, they could take down your network by poisoning the routing tables on all routers. For this reason, routers should be in a locked room and preferably have video surveillance. Additionally, reliable electrical power and cooling must be provided.
Lock down the router with passwords
Routers must be secured with passwords at both the login mode (to prevent initial access) and the privileged mode (to prevent configuration changes). For more information on these different levels in the Cisco IOS, please see my article, “Understand the levels of privilege in the Cisco IOS.”
Apply login mode passwords on Console, AUX, and VTY (telnet/ssh) interfaces
Password controlled access needs not only to be on the VTY lines to prevent network access, but also on the Console and AUX ports. If the Console port is locked but the AUX port doesn’t have a password, then locking the Console wasn’t of much use, was it?
Set the correct time and date
To ensure that logs are correct and have not been tampered with, you must ensure that the router has the correct time and date. For more information, please see “Synchronize a Cisco router’s clock with Network Time Protocol (NTP).”
Enable proper logging
Logging should be enabled, preferably, back to a central source like a syslog server. At minimum, you need to configure a buffered log on the router. However, if the power is lost to that router, that local buffered log is lost. For this reason, to really be secure, you need to configure a syslog server (see the article, “SolutionBase: Monitor your network with Kiwi Syslog“), and send all router logs to that server. You could also put in the open source or commercial version of Tripwire. Preferably, you should increase the level of logging and even log configuration changes to the router. For example, you can use the following command to enable SNMP traps for configuration changes:

snmp-server enable traps config

For more information on Cisco router logging, please see, “Get to know your logging options in the Cisco IOS.”
Back up router configurations to a central source
Let’s say that someone does take control of your router or wipes out your router configurations. To replace that router quickly or replace the configuration, you need to have a backup of that configuration. To do this, ensure that your routers are backed up whenever configuration changes are made or each week or day. I have enjoyed using Kiwi CatTools to do this. For more information, see “Automate changes to your Cisco router with Kiwi CatTools.”
Secure other network devices such as switches and wireless access
Most of the items listed here also apply to Cisco switches and wireless access points. Here are a couple of articles on those topics that you should check out:

• 10 things you should know about securing wireless connections
• Lock Down Switch Port Security

Two more areas that I consider to be at the basic level of router security are locking down network access to the router with a stateful firewall or ACL and encrypting sensitive network traffic, but I will cover these points in more detail below (sections three and five, respectively).

2. Know your network: Diagram, audit, and document

If you are responsible for the security of a network you should know that network like you know the vulnerable doors and windows (think entry points) of your house.
You should diagram your network so that you have a map to help you and others visualize the entire network.
You should have the router configurations backed up (see Kiwi CatTools above). Finally, you should periodically audit your network security, both internally and externally (via a third party). There are tons of network scanning and auditing tools available. Here is a recent article of mine that covered one of them: “Audit your Cisco router’s security with Nipper.”

3. Protect your router with a firewall and ACLs

In Reese’s post about the hackers, he mentioned the fact that the company had poor access control lists (ACLs) in place on their routers. ACLs are typically what protect routers from attack. However, due to their complexity, many of them end up being misconfigured or ineffective. Make sure that your ACLs allow only traffic to the router and through the router that should be there. For internal routers this will only be internal traffic.
Make sure you understand that whatever isn’t permitted will be denied (the implicit deny), that ACLs are processed from the top down, that there should never be a permit any in the ACL, and that the ACL must be applied to an interface in the proper direction to be enabled. For more information on ACLs, please see some of my articles and video on this topic:

• Secure your router with Cisco’s SDM Firewall Policy Wizard
• Cisco IOS access lists: 10 things you should know
• Use advanced parameters on your Cisco IOS ACLs
• VIDEO: Harden your Cisco Router with IOS ACLs

Keep in mind that ACLs aren’t just used to prevent traffic from going through the router. They are also used to control SSH traffic, routing update, and to throttle traffic. For more information, see:

• Learn additional uses for Cisco IOS access control lists
• Control unwanted traffic on your Cisco router with CAR

Besides ACLs, the Cisco IOS offers a real stateful firewall if you use the Security/Firewall version of the IOS. A stateful firewall will be much better than just using ACLs. I recommend checking out my article, “Protect your network with the Cisco IOS Firewall,” and consider implementing one on your routers.

4. Change your passwords and make them complex

Another method that hackers use to take control of networks is password guessing or password sniffing. To prevent this, you should CHANGE YOUR PASSWORDS TO COMPLEX PASSWORDS TODAY. Don’t wait another day! An example of a complex password is MySuper!S3cr3tPa$$.
Make sure you always use type 5 password encryption on your routers (see “Be aware of how easily someone can crack a Cisco IOS password“). Make sure this command is on your router to encrypt most (but not all) passwords with type 5 encryption:

service password-encryption

Also, keep in mind that we aren’t just talking about login passwords. This includes all SNMP community strings and routing protocol update passwords. All of those should be complex and changed periodically.
For more information on this topic, please see, “How to Configure Passwords to Secure your Cisco Router.”

5. Always encrypt sensitive network traffic

Finally, hackers can obtain passwords to your routers by sniffing network traffic when you log in to your router with telnet, perform a “show run” via telnet, or use unencrypted SNMP strings.
You should always encrypt sensitive network traffic by using SSH and SNMP encryption. Start by enabling SSH and disable telnet to all network devices that support it (see “Configure SSH on your Cisco Router“).
If you are using SNMP, enable SNMP v3 with encryption and use it exclusively (for more information, see AES and 3-DES Encryption Support for SNMP Version 3).

Be careful

The point of this article is to (1) encourage you to take action to secure your network before malicious attackers take control of it and (2) to show you exactly which actions you need to take. You shouldn’t assume that your network isn’t a target because your company isn’t high profile or your data wouldn’t be valuable to an attacker. Take every reasonable step to protect your network; as you can see from this post, these steps aren’t necessarily difficult or costly.
Want to learn more about router and switch management? Automatically sign up for our free Cisco Routers and Switches newsletter, delivered each Friday!

How to reset Product Key - Microsoft Office

Today i got problem with ms office, cannot activate because it said already reach the limit for the product key. Actually i don't know which installation cd have been used.

I must install new ms office to get new product key but anyway i don't know which cd already used and validate. After searching in the internet , i got solution and i tried , successful.

This is the step :

1. Close all Microsoft Office programs.
2. Click on Start button, then click on Run.
3. Type “regedit” (without quotes) in the Run text box, and click OK or press Enter.
4. Locate and then click the following subkey: HKEY_LOCAL_MACHINE \Software\Microsoft\Office\12.0\Registration
   Inside, you will find another subkey that resembles the following subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Registration\{30120000-00
5. After you find the GUID subkey that contains your Office product or program which you want to remove the existing product license key or registration details, delete the following registry entries by right clicking on the registry entry in the GUID subkey, click Delete, and then click Yes: • DigitalProductID
   • ProductID
   
6. Exit Registry Editor.
7. Run or open an Office application program, such as Microsoft Word or Excel or Outlook. Office will prompt you to enter a new 25-character product key.

NTLDR Missing

NTLDR Missing

http://tinyempire.com/notes/ntldrismissing.htm
http://pcsupport.about.com/od/fixtheproblem/ht/ntldrntdetect.htm
http://pcsupport.about.com/od/fixtheproblem/ss/rconsole_4.htm

10 security tips for all general-purpose OSes

• Date: October 19th, 2007
• Author: Chad Perrin
• Category: Security, Passwords, Authentication, Intrusion Detection, Encryption, Malware, networking, patching

There are key considerations for system security that apply no matter which general-purpose operating system platform you happen to be using. You should always consider the following precautions when securing your systems against unauthorized access and unfortunate disasters:

1. Use strong passwords. One of the simplest ways to improve security is to use a password that isn’t easily guessed by brute force attacks. A brute force attack is one where the attacker uses an automated system to guess passwords as quickly as possible, hopefully finding the right password before long. Passwords that include special characters and spaces, use both capital and lowercase letters, avoid words in the dictionary, as well as numbers, are much more difficult to crack than your mother’s name or your anniversary date. Remember as well that increasing the length of your password by one single character multiplies the total number of possibilities by the number of valid characters that can be used. In general, anything less than eight characters is considered far too easy to crack. Ten, 12, or even 16 is better. Just don’t make it too long to remember or too difficult to type.
2. Invest in good perimeter defense. Not all security occurs on the desktop. It’s a good idea to use an external firewall/router to help protect your computer, even if you only have one computer. At the low end, you can purchase a retail router device, such as the commercial Linksys, D-Link, and Netgear routers that are available in stores such as Best Buy, Circuit City, and CompUSA. Higher up the scale, you can get managed switches, routers, and firewalls from “Enterprise” class vendors such as Cisco, Vyatta, and Foundry Networks. Starting somewhere in the middle and moving all the way up to direct competition with the major “Enterprise” class vendors, you can put together your own firewalls either “from scratch” or using prepackaged firewall/router installers such as m0n0wall and IPCop. Proxy servers, antivirus gateways, and spam filtering gateways can all contribute to stronger perimeter security as well. Remember that in general switches are better for security than hubs, routers with NAT are better than switches, and firewalls are a definite necessity.
3. Update your software. While concerns such as patch testing before deployment to production systems may be of critical importance in many circumstances, ultimately security patches must be rolled out to your systems. Ignoring security updates for too long can result in the computers you use becoming easy targets for unscrupulous security crackers. Don’t let the software installed on your computers fall too far behind the security update schedule. The same applies to any signature-based malware protection software such as antivirus applications (if your system needs them), which cannot be any more effective than the degree to which they are kept up to date with current malware signature definitions.
4. Shut down services you don’t use. Often, computer users don’t even know which network accessible services are running on their systems. Telnet and FTP are common offenders that should be shut down on computers where they are not needed. Make sure you’re aware of every single service running on your computer, and have a reason for it to be running. In some cases, this may require reading up on the importance of that service to your particular needs so that you don’t make a mistake like shutting off the RPC service on a Microsoft Windows machine and disallow logging in, but it’s always a good idea to have nothing running that you don’t actually use.
5. Employ data encryption. Varying levels of data encryption coverage are available to the security-conscious computer user or sysadmin, and choosing the right level of encryption for your needs is something that must be decided based on circumstances. Data encryption can range from use of cryptographic tools on a file-by-file basis, through filesystem encryption, up to full disk encryption. Typically, this doesn’t cover the boot partition, as that would require decryption assistance from specialized hardware, but if your need for privacy is great enough to justify the expense, it’s possible to get such whole-system encryption. For anything short of boot partition encryption, there are a number of solutions available for each level of encryption desired, including both commercial proprietary systems and open source systems for full disk encryption on every major desktop operating system.
6. Protect your data with backups. One of the most important ways you can protect yourself from disaster is to back up your data. Strategies for data redundancy can range from something as simple and rudimentary as periodically saving copies to CD to complex, staggered, periodic automated backups to a server. On systems that must maintain constant uptime without loss of service, RAID can provide automatic failover redundancy in case of a disk failure. Free backup tools such as rsync and Bacula are available for putting together automated backup schemes of arbitrary complexity. Version control systems such as Subversion can provide flexible data management so that you can not only have backups on another computer, but you can keep more than one desktop or laptop system up to date with the same data without a great deal of difficulty. Using subversion in this manner saved my bacon in 2004 when my working laptop suffered a catastrophic drive failure, emphasizing the importance of regular backups of critical data.
7. Encrypt sensitive communications. Cryptographic systems for protecting communications from eavesdroppers are surprisingly common. Software supporting OpenPGP for e-mail, the Off The Record plug-ins for IM clients, encrypted tunnel software for sustained communication using secure protocols such as SSH and SSL, and numerous other tools can be had easily to ensure that data is not compromised in transit. In person-to-person communications, of course, it can sometimes be difficult to convince the other participant to use encryption software to protect communications, but sometimes that protection is of critical importance.
8. Don’t trust foreign networks. This is especially important on open wireless networks such as at your local coffee shop. If you’re careful and smart about security, there’s no reason you cannot use a wireless network at a coffee shop or some other untrusted foreign network, but the key is that you have to ensure security through your own system, and not trust the foreign network to be safe from malicious security crackers. For instance, it is much more critical that you protect sensitive communications with encryption on an open wireless network, including when connecting to Web sites where you use a login session cookie to automate authentication or enter a username and password. Less obviously, make sure you don’t have any network services running that are not strictly necessary, as they can be exploited if there is an unpatched vulnerability. This applies to network filesystem software such as NFS or Microsoft CIFS, SSH servers, Active Directory services, and any of a number of other possibilities. Check your systems both from the inside and the outside to determine what opportunities malicious security crackers may have to attempt to compromise your computer, and make sure those points of entry are as locked down as reasonably possible. In some respects, this is just an extension of the points about shutting down unneeded services and encrypting sensitive communications, except that in dealing with foreign networks you must be especially stingy with the services you allow to run on your system and what communications you consider “sensitive.” Protecting yourself on a foreign, untrusted network may in fact require a complete reworking of your system’s security profile.
9. Get an uninterruptible power supply. You don’t just want a UPS so you won’t lose files if the power goes out. There are other, ultimately more important reasons, such as power conditioning and avoiding filesystem corruption. For this reason, make sure you get something that works with your operating system to notify it when it needs to shut itself down, in case you aren’t home when the power goes out, and make sure you get a UPS that provides power conditioning as well as battery back-up. A surge protector simply isn’t enough to protect your system against damage from “dirty” power. Remember, a UPS is key to protecting both your hardware and your data.
10. Monitor systems for security threats and breaches. Never assume that just because you’ve gone through a checklist of security preparations your systems are necessarily safe from security crackers. You should always institute some kind of monitoring routine to ensure that suspicious events come to your attention quickly and allow you to follow up on what may be security breaches or threats to security. This sort of attention should not only be spent on network monitoring but also integrity auditing and/or other local system security monitoring techniques.

Other security precautions may apply depending on the specific OS you use. Some operating systems provide additional challenges to security because of design characteristics that produce a less-than-optimal security profile, and some operating systems grant the knowledgeable sysadmin capabilities for increased security that may not exist elsewhere. All of this should be kept in mind when securing your system, whether using proprietary systems such as Microsoft Windows and Apple Mac OS X or open source systems such as your favorite Linux distribution, FreeBSD, NetBSD, or even the very security-conscious OpenBSD.
Only in the very rarest of circumstances is a default install of your OS of choice, with no further thought to securing the system, truly sufficient. Start with the above enumerated security concerns regardless of your operating system, then consider the specific security needs and opportunities of your platform. Don’t leave the integrity of your system’s security up to luck.

& Techniques for Managing ICT Staff

This info i taken from http://techrepublic.com.com/ with original title 7 techniques for manging your technical staff.

• Date: October 16th, 2007
• Author: Tom Mochal
• Category: Project Management, Personnel, Management

In my last blog, I talked about some of the general characteristics of an IT project team. For example:

• They tend to be introverts
• They tend to think more logically than emotionally
• They tend to be problem solvers
• They tend to be technically creative

Knowing some of the characteristics of your technical staff allows you to better understand how to manage them effectively. Applying some or all of the following techniques will help you create a more conducive work environment where people can excel.
Give them the tools that need to do their jobs.
Establish an environment where people feel they have what they need in order to do their jobs. This includes having appropriate hardware and software. It doesn’t necessarily need to be state of the art, but it should be of acceptable quality. Because they’re in the IT field, IT people get frustrated when they don’t have the right hardware and software to do their jobs effectively.
Make sure they have the right skills and provide opportunities to learn.
IT people love to learn new things. Managers should make sure their people have the skills needed to do their jobs and that they receive opportunities to grow into new technical areas. This doesn’t have to be third-party training classes. It can include computer-based training, seminars, webinars, books, magazines, etc. Also, once someone has mastered a certain skill and they start to become bored, look for ways they can cross-train and learn new areas of the group.
Create a viable work environment.
Technical people like to understand the work processes in the group, and then they like to be creative in working within that structure. So, set the high-level rules, but don’t micromanage the details.
Give people as much information as they need to do their jobs.
Managers should strive to be proactive communicators. Remember, many IT people are introverts who like to process information internally. They may or may not come up to you and ask you what’s going on all of the time. Managers should make sure that they communicate as much as they can about what’s going on in the company, their organization, and their group.
Shield the team from office politics
Don’t let your team get bogged down in the organization muck. This means removing organizational roadblocks and shielding the team from organizational politics. IT people will tend to get cynical fast if they feel like a political environment is affecting their work or in decisions that affect them.
Make sure each person remembers he’s part of a team.
Even though IT people tend to be introverts, it doesn’t mean they prefer to work alone. IT staff may prefer to work independently, but they also like being a part of the team. Managers should nurture this need. For instance, they should have regular team meetings. Managers should also make sure they have opportunities to do fun stuff as a group - even if it’s just going to lunch together once in a while.
Be there when needed and respond to problems and concerns.
Not all problems can be fixed, but many times the simple act of listening and trying is enough. People will give you credit for trying, even if the ultimate resolution to a problem isn’t available.
You might note that many of these management techniques are not unique to technical staff in general or IT staff in particular, but they’re particularly applicable to the IT staff.