Jump to content

pngwen

Active Members
  • Posts

    6
  • Joined

  • Last visited

About pngwen

  • Birthday 06/09/1980

Contact Methods

  • AIM
    pngwen00
  • MSN
    pngwen00@hotmail.com
  • Yahoo
    pngwen00
  • Skype
    pngwen

Profile Information

  • Gender
    Male
  • Location
    Knoxville, TN
  • Interests
    Hacking, Coding, Mathematics, Computer Science, Artificial Intelligence, Hiking, Reading, and everything else. I like it all!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pngwen's Achievements

Newbie

Newbie (1/14)

  1. You may want to look at a linux application called gmrun. It's a small thing that does pretty much what you are interested in. It's written in C++ and uses GTK for its gui displays. It's only about 2000 lines long. Depending on if you want to make your app open or not, you could just take their C++ code and build on it. Behold the glory of open source!
  2. One small thing before I start. I am a teacher of coders, particularly in the ways of C, Computer Architecture, and Theoretical Computer Science. I am in a weird sort of guru mode tonight, so I will tell you a story, one which will make plain the ways of memory. Gather round my young nerdlings, and attend my tale. In the days of the before time, the long long ago, machines ran but one program at a time. These machines were usually directly coded in their pure languages. The humans did move things in and out of memory, and all was well. But then, more people wanted to command these magical boxes, and there were not enough of these boxes to go around, and so the idea of time sharing was born. First, the idea was simple. "Let us write monitors" the gurus of that day said. "They will manage memory, and give slices to processes. One shall execute and once, and they shall not cross the boundaries of another." But alas, this did not appease the crowds, another way had to be found. "Let us rapidly switch from one running task to another." One of the gurus said. "But how can we do that? Yay, verily the process of ones own brother would utterly blorch the memory of ours." and then they spake saying "Let us not concern ourselves with the true memory. We shall hide it behind a magical wall, one which will manage memory. Let it's name be called MMU, for that is the unit which manages the memory. It shall move memory in pages, and physical addresses will become as transitory as we are." and the people did see that their process could all live in piece, thinking that each had complete access to the machine on its own, and the MMU did keep their segments apart. The processes could be located anywhere in memory. Memory could be disjoint, and well used, and everyone was very pleased for it was very good. That is why you cannot get the physical address from the pointer, for the pointer is not wise. The pointer sees only the illusion of its self. You must go higher, and ask the OS for the true address. BUT! Be cautious young programmers, for once thou knowest the true memory location, there is no guarantee that the memory shall reside there the next time. Pages swap. Physical addresses are no more constant than lotus blossoms floating on a river. When the master thus spake to his students, they asked of him, Students: "But how can we know the truth if not even the pointers know?" Guru: "You must reach out to the OS, and make a call to its API to find it." Students: "How shall we call it?" Guru: "Well, it depends upon the OS. You mentioned Olly DBG, so I assume you are running on the Redmond attrocity. Seek you out documentation on the MmGetPhysicalAddress function. Seek you out its breatheren, the other redmond calls which begin Mm, and you can truly pwneth they boxen!" Students: "What of the unixes? Do they know their memory address" Guru: "But of course, you must simply ask the kernel." Students: "But how shall we call it?" Guru: "Read the source my younglings. The answer you seek lies within there. You need naught but your own eyes and patience to know all that there is of unixes. Now go! Look up those functions, read the memory mapping code, and become enlightened. Our time is brief, soon we shall page out of this world, into a most corruptible swap. Now meditate on the transitory nature of all things."
  3. On my multipass I have: OS's: Gentoo Backtrack 5-R1 UBCD 5.1.1 Puppy 528 (lucid variant) DSL 4 OpenBSD 5.0 UBCD4Win Yggdrasil (yes, the ancients rock out on my usb drive) Ok, so that last OS probably looks a bit odd for those who know what yggdrasil is/was. It was the first linux version I ever ran. I customized its initrd so I could boot from USB disks and I keep it around for nostalgic days. Gentoo is my primary distro, and I use a custom AUFS config on my flash disk to be a portable main usage linux machine. The others are pretty self explanatory for how they get used. I have persistence turned on in just about all of them. Bootloaders syslinux isolinux grub lilo Portable Apps for Windows In addition to the OS's, I keep a lot of portable apps on my drive so I can service windoze machines. I have quite a lot of these apps. Generally I use them to pentest windows machines and/or do recovery for computers that have been left alone with n00bs for too long. Hardware Tools Ok, not quite what was asked, but I consider this a part of my mutlipass build. I carry a cybertool 29 swiss army knife. I have carried it for around 13 years and I gotta tell you, you can completely dismantle an entire server room with one of those bad boys! I highly recommend keeping one near your usb stick in your pocket at all times. I also keep a pocket set of lockpicks to go with it. (Note, your local laws may not let you carry these.) I started keeping the lockpicks around when I went in to service a rack and it had a lockable steel grating, and the owners had no idea where the key was. Server room locks are easy to work, so those little pocket folding sets do just fine. Also, you can be a hero to friends who lock their keys in their car. Conclusion The above tools are on my person at all times. Whenever someone comes to me with a broken laptop, I can usually fix it on the spot. I can also diagnose networks, recover passwords, recover wep keys, run post mortems, set up temporary firewall machines, install any flavor of linux, set up permanent firewall machines,... pretty much anything, all with what I have with me at all times. You know, looking at the list, I could be a real menace just with what is in my pockets. Of course, I only hack for the good of mankind ;)
  4. I did some testing with a fresh 9V battery and I was able to run my pineapple for about 3.25 hours. That was with relatively little activity though. I'm sure the time goes down if there are a lot of connections. As for the ready built one someone linked to, it looks exactly like what my finished battery adapter looks like. The only advantage I can see to building one is that you may already have the parts on hand, and if not they are available at a brick and mortar store. The hand built ones are a little cheaper too, but only by pennies, not enough for that to matter.
  5. First off, I've been enjoying my mark III pineapple. I had drooled over my buddy's mark II for quite a while, and I was very happy to get my hands on the MK III. Now, on to the good stuff. I put together a USB power cable so I wouldn't be reliant on the battery pack (which takes some wiggling to make work), and then I started thinking about the voltages that this device operates at. The AA battery pack gives 6V, USB is (of course) 5V, and the AC adapter is 12V. Given that there seems to be a wide range of voltages that the pineapple can run at, I thought I'd try out using a 9V battery (aka, transistor battery). I'm happy to report that this works quite well. I haven't run a battery down all the way yet, but I was able to run my pineapple for about 1.5 hours on a 9V. 9V is well within the range of 5-12V, so it really isn't surprising that it works. All you need to do this is a couple of easily obtainable parts (radio shack even sells them). So here's the build: PartList: 1.) N-Size Coaxial Power Adapter (radio shack sells these in 2 packs) 2.) 9V battery clip with leads Simply solder the red wire to the inner pin of the power adapter, the black to the outer pin, and then Bingo! You can use a 9V battery to power the pineapple. These batteries are lighter and smaller than the AA battery pack, so they are more convenient. I'm not sure of the battery life, I'll do some testing with it tomorrow to find out, and I'll update you. Given that the capacity of the 9V is the same as the AA's, it should be comparable to the AA battery pack. Another advantage is that the radio shack adapters are better than the one on the battery pack that I received with the pineapple. It fits the router better! Now, as a bonus, the power adapters are in a 2 pack. So, you can use the other one to make a USB adapter. That way you have even more power options. (I can see myself using the USB power more than the 9V when I work with my laptop. The 9V is so I can leave the pineapple running hidden in a drop ceiling or somesuch place). I know this has been posted elsewhere, but I'll add this to my post for convenience: USB Power Supply 1. N-Size Coaxial Power Adapter 2. USB cable. The build is the same. Solder the red wire to the inner pin, black to the outer. (Assuming standard cable lead colors. If not, the pinouts of a USB A connector (looking end on) are: | +5V D- D+ Gnd | So the "Red" wire is the one on the far left, and the "black" wire is the one on the far right. D- and D+ are the Data lines, btw. These are fun to mess with if you have a few microcontrollers lying around, but I digress. So there you have, a couple of power builds for the Mark III, with specific power adapter size info. I hope this is useful to you, and I apologize if this has been posted elsewhere. I couldn't find it though. Let me know if you have any questions/comments about it. Enjoy!
×
×
  • Create New...