regret

Members
  • Content count

    472
  • Joined

  • Last visited

Community Reputation

0 Neutral

About regret

  • Rank
    SUPR3M3 31337 Mack Daddy P1MP
  • Birthday 07/02/1982

Profile Information

  • Interests
    Everything...world student. Computers, phones, hardware, programming, telecomm, languages (love phreaking ppl out in the south by speaking something other than spanish), physics, math, everything...
  • Location
    Are any of us ever in one place at any give time?

Contact Methods

  • Website URL
    http://
  • ICQ
    0
  • Yahoo
    di3m0nd6ack
  1. you can mount the BT3 partition within slackware and use the applications from within the slackware system. The only problems you may run into (from personal experience) is you may get missing library errors. To correct those, simply use slocate to find the file and make a soft-link to the /lib and-or /usr/lib folders on your slackware install. updatedb && slocate [i]missingfilename[/i] then, say your missing libgtk.so.0 and it finds it on /media/bt3/lib/libgtk.so.0, just use a soft link to add the file to your /lib folder ln -s /media/bt3/lib/libgtk.so.0 /lib/libgtk.so.0
  2. I split my hard drive on my primary laptop and installed Slackware and Backtrack2 on different partitions. I have the full functionality of a verbose linux distro, plus the software available from a good out-of-the-box pentesting distro...best of both worlds. I just boot into slackware all the time and I have my hda4 partition mounted to /media/bt2 so I can access all the application goodness directly from Slack.
  3. I actually wasn't meaning that the pentium III was obsolete, I was stating an allusion that was just as absurd to state a fact. I actually use 2 Pentium III machines and a Pentium II still within my private network. Phreaking does serve a purpose and that purpose is as simple as hacking...exploration. Just as hacking has expanded to TCP/IP networks over broadband connections with dynamic firewall systems and IDS/honeypots monitoring your every move, phone networks have change. It's just a sad fact of the matter that many have not moved into the newer "unexplored" areas of the world of telecom...the capabilities of asterisk and VOIP interconnection has barely been touched. Too many people just seem to be stuck in the past of wanting to use boxes and seize trunking line to make international phone calls, then when they are told that those things no longer work, they stand back and proudly boast that "phreaking is dead". Makes me wonder why those people have not stood on the hacking side and said the same things about many of the elements of "glorified hacking" that draw so many people in, only to find out they no longer are relevant either.
  4. I still don't quite understand why everyone is still saying that phreaking is dead. It's like saying that hacking is dead because Pentium III's are "out-dated". Phreaking is not dead, it has just evolved...I guess the phreaking history is a bit more romanticized than the hacking community's, maybe that attributes to the stagnant feel of the community.
  5. Ooo, I have a leet new 0-day...that kind of crap is completely overrated and all your doing is adding detriment to your own community by doing so. The purpose of a hacker community is so that we ALL may learn from each others explorations. Another reason is that you and your mate may be looking for a specific exploit in a system's code and say you find it first and keep it all to yourself. Then someone else finds and publishes the exploit and your buddy says "Man, I've been working on that for two weeks now." you say "Really, I've known about that for a while now, I've just been keeping it under my hat (In case you need it)." buddy says "Well, thanks for wasting my time for those two weeks...I could have been working on something more productive." It's all about consideration and compassion for your fellow hackers and the knowledge that their time is just as important as yours. If someone wastes your time by having you search for exploits in code that are already known and published...wouldn't you be a little peeved? ^^ A sad sign of the new state of the hacker world right there.
  6. There is nothing in the A+ Certification that delves into the realm of security. Poster may have been thinking of the creators of the A+ Certification (Comptia) who also have a Security+ certification. But personally, I feel the Security+ (as well as many of the "Ethical Hacker"/security) non-vendor certifications are far too broad in the curriculum to be effective in the real world. I could see taking one of those courses if you have no background in the industry and need an overview, but personally...they're worthless. Your ultimate goal if you're looking to get into the security world is knowledge and adaptation, those two things cannot be stressed enough. The problem with the Security and Network Administration industries is that you must be extremely flexible to keep up with the "latest-greatest crap" most company will put out to keep your systems more secure. Though you may not feel as though they are necessary or your system's security may be adequate or may be detrimental to your network's infrastructure...it's all about what the big bosses want. Suggestion...grab every book, every program you can get your hands on...experiment experiment experiment. Try everything you can think of, then sleep on it and try everything you never thought you could think of.
  7. Try grabbing another live cd or OS boot disk ISO and burning it with the same CD burner...I believe it may be your burner itself causing the corruption.
  8. "HE GOT ALL THE WAY INTO MY WIRELESS NETWORK!" I may buy the movie when it comes out of DVD just so I can set it on fire....
  9. We got latest edgy from MIT Media Labs Mirror the other day for my brother's system and everything checked out from there...come to think of it, I've never gotten a bad checksum on an Ubuntu download.
  10. Generally in a situation to where you may not know the producer of a firewall's code there are a few avenues you can take to discover the authors. Good documentation practices with project developers in the open source community is to always include a README file with contact information near the EOF. Many programmers will also comment the main body of their programs (usually at the beginning of a main source file) with information on the authors. There will always be the closed-source programmers (who apparently believe in "security thru obscurity" by hiding their code) and finding the authors of the code can be a bit more difficult when dealing with corporately developed code. Usually, you can pilfer thru the documentation and find a textfile on bug submission protocols and most of the time they will contain some better contact information. But any open-source firewall program will contain information on how to contact the authors, which is very handy in many different situations. What if you find a bug? Has a REAL hacker, it is your duty to alert the project group and publish your findings...so that other hackers are not covering ground that has already been explored. What if you make a modification to the code that produces a global increase in the efficiency of the code? It's your duty to publish and share your findings with the public (always the code project owners first...it's just common courtesy). That's what being a hacker is all about...
  11. Part 1...What is coming up and saying that it is loading? The WindowsXP splash screen or is it the Grub Loader screen that you are seeing? Part 2...When you type iwconfig in the terminal what comes up? You may take a look at http://www.linux.com/feature/56946 as well. I'd like to help more, but more specifics are needed for effective answers.
  12. It seems that you have surpassed the first step in my opinion, that you have studied many different fields and gained general (functional) knowledge on many different subjects. Like some of the previous responses, I agree that the time may be right for you to specialize yourself. That does not mean to limit yourself to one field of self-training, but to study a particular field that will hold your interest enough to become exceptional in that field. Personally, I'd recommend a stint of self-discovery, to really sit down and think about what really interest you the most and focus your attention on that particular subject. You'd be amazed at the directions you can take once you have become familiar enough with a system or piece of software to know what it's designed "limitations" are and where you can personally take it in ways that it was not designed.
  13. There will always be the undiscovered exploits and misconfigurations that can be used to gain entry or simply bypass a firewall. The best thing to do when trying out a firewall system that you are unfamiliar with is to study the actual tech manuals on the software. You should also check many of the exploit publishing sites like milw0rm and packetstormsecurity for possible articles on exploits that have not been acknowledged and/or patched by the firewall developers. The second thing you can do is conditional on the type of software you are using for a firewall. The primary reason I choose open-source over closed source software is for the basic fact that I can review the code myself and look for possible exploits that may be unpublished...as well as fixing them myself if necessary. If you're looking into furthering your education on network security and feel you have a good enough grasp on firewalls, group administration, security policies, and network design...you may enjoy the adventures of honeypots and all the cool configurations you can accomplish with them. Something I am looking into and have found quite interesting as of late is Reactive (Defensive) Software. Sample Chapter from a book on the subject.
  14. There are a few things I do first off on a fresh install of any linux distro. 1. Configure IPTables 2. Configure host.allow, host.deny, and run thru the /etc/rc.d folder for anything not needed. 3. Fluxbox configuration...what can I say, I love my themes and backgrounds. A comfortable working environment gets my creative juices flowing. Generally, I go thru most of the system configuration files and system administration files (/etc/passwd, /etc/group, ect ect) before I start in on any applications. Then I go thru the user and group files again to make sure nothing was arbitrarily reconfigured without admin knowledge.
  15. Just remember....you always get what you pay for. I have a Dell laptop that I purchased four years ago that has been my primary box and have had very good luck with this one (Inspirion 9200). Then I decided to get another lappy, but opt'd for a cheaper one this time. Let's just say I completely understand the beef alot of people have with the new Dell....I've had to send it off for repairs twice and I still have issues (intermittent column of screen pixels turning green and my headphone jack went out).