Like my promise yesterday which was stated in the article part 1 "Learning to be a hacker"
Before moving on to the next chapters, you need to know that the hacking process is not always negative, we will learn how to infiltrate other people's systems, but not damage or make changes. The person doing the hacking is what we know as the HACKER.
Conversely, people who damage other people's systems are called CRACKERS and their work is called CRACKING.
Based on RFC 1392, regarding the internet users glossary. Definition Hacker is an individual who is interested in specifically exploring the workings of an internal system, computer, laptop and network. Meanwhile, CRACKER is an individual who "forces" into a system intentionally without "permission" with "bad" purposes. The two terms are sometimes interpreted the same but are very different.
Before going any further, I will invite you to get to know and memorize numbered internet standards called RFCs. RFC stands for Request for Comment which is used in networks, the internet and some network operating systems such as windows. RFCs are under the direction of ISOC (Internet Society) and technical standards setting bodies such as the IETF (Internet Engineering Task Force) or IRTF (Internet Research Task Force)
This is a list of commonly used RFCs
- RFC 768 = User Datagram Protocol
- RFC 791 = Internet Protocol
- RFC 792 = Control Message Protocol
- RFC 793 = Transmission Control Protocol
- RFC 821 = Simple Mail Transfer Protocol Change to RFC 2821
- RFC 822 = Format e-mail Change to RFC 2822
- RFC 826 = Address Resolution Protocol
- RFC 894 = IP via ethernet
- RFC 951 = Bootstrap Protocol
- RFC 959 = File Transfer Protocol
- RFC 1034 = Domain Name System - Konsep
- RFC 1035 = DNS - implementasi
- RFC 1122 = Terms Host 1
- RFC 1123 = Terms Host 2
- RFC 1191 = Path MTU
- RFC 1256 = Founder Router
- RFC 1323 = TCP high performance
- RFC 1350 = Trivial File Transfer Protocol
- RFC 1403 = Interactions BGP OSPF
- RFC 1459 = Protocol Internet Relay Chat
- RFC 1498 = Architectural Discussion
- RFC 1518 = CIDR alocation
- RFC 1519 = CIDR
- RFC 1591 = Domain Name Structure / DNS
- RFC 1661 = Point to point Protocol
- RFC 1738 = Uniform Resource Locator
- RFC 1771 = A border Gateway Protocol 4
- RFC 1772 = Aplication BGP
- RFC 1789 = Internet Phone / VoIP
- RFC 1812 = Router IPv4
- RFC 1889 = Real time Transport
- RFC 1905 = Simple Network Management Protocol
- RFC 1907 = MIB
- RFC 1918 = Network 10
- RFC 1939 = Post Office Protocol Version 3 (POP3)
- RFC 2001 = TCP Performance
- RFC 2026 = Internet Standar Process
- RFC 2045 = MIME
- RFC 2046 = MIME
- RFC 2047 = MIME
- RFC 2048 = MIME
- RFC 2049 = MIME
- RFC 2060 = Internet Message Access Protocol versi 4 (IMAP4) change to RFC 3501
- RFC 2131 = DHCP
- RFC 2223 = Intructions for RFC author
- RFC 2231 = Set aksara
- RFC 2328 = OSPF
- RFC 2401 = Security Architecture
- RFC 2453 = Routing Informations Protocol
- RFC 2525 = TCP problem
- RFC 2535 = DNS Security
- RFC 2581 = TCP Jam Control
- RFC 2616 = HTTP
- RFC 2663 = Network address Translation
- RFC 2766 = NAT-PT
- RFC 2821 = Simple Mail Transfer Protocol
- RFC 2822 = Format e-mail
- RFC 2960 = SCTP
- RFC 3010 = Network File System
- RFC 3031 = Arsitektur MPLS
- RFC 3066 = Tag language
- RFC 3092 = Etimologi "Foo"
- RFC 3098 = Email advertising
- RFC 3160 = Tao IETF
- RFC 3168 = ECN
- RFC 3501 = IMAP4rev1
This is our world now...the world of the electron and the switch,the beauty of the baud. We make use of a service already axisting without paying for what could be dirt-cheap if it wasn't run by profiteering gluttons,and you call us criminals. We explore...and you call us criminals. We seek after knowledge...and you call us criminals. We exist without skin color,without nationality,without religius bias...and you call us criminals.You build atomic bombs,you wage wars, you murder,cheat and lie to us and try to make us believe it's for our own good,yet we're the criminals. Yes, I am a criminal. My crime is that of curiosity. My crime is that of judging people by what they say and think,not what they look like. My crime is that of outsmarting you,something that you will never forgive me for
The principles and code of ethics of a hacker
- Don't damage any system on purpose. Such as: Causing a crash, overflow, changing the index file of a website. Although there is also the argument that changing the index file is fine as long as the original file is stored on the same system and can be accessed by the administrator
- Do not change system files other than those needed to secure your identity as the hackers
- Do not leave your own (or anyone else's) real name, real phone number on any system that you access illegally. They can and will track you.
- Be careful about sharing sensitive information. The government will get smarter. In general, if you don't know who the other person is, be careful with the person you're talking to.
- Don't start off by targeting government-owned computers. Yes, there are many government owned systems that are safe enough to hack, but the risks outweigh the benefits. Remember, the government has unlimited funds compared to ISPs / companies whose objective is to seek profit.
No comments:
Post a comment