Installing VMware Server is pretty straight-forward on Ubuntu 7.04
(Feisty Fawn). Make sure you have the build-essential package and
the correct linux-headers for your kernel.
$ sudo apt-get install build-essential linux-headers-`uname -r`
Download VMware and extract the contents to vmware-server-distrib. Run
the installation script and read through it all. I ended up just saying
'yes' throughout the entire script
$ sudo ./vmware-server-distrib/vmware-install.pl
I encountered a little problem compiling the vmmon module while
installing VMware Server on Ubuntu Feisty Fawn (7.04). At some point,
the install script will ask you if you'd like to run
/usr/bin/vmware-config.pl automatically. I did and I ran into a
problem while compiling the vmmon modules:
What is the location of the directory of C header files that match your running kernel?
[/lib/modules/2.6.20-14-386/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.20-14-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-14-386'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/linux/driver.c:80:
/tmp/vmware-config0/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘compat_exit’
/tmp/vmware-config0/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’
/tmp/vmware-config0/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to ‘int’ in declaration of ‘_syscall1’
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-14-386'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.
If you experience this exact problem, download
vmnet.tar
and
vmmon.tar
and place them (do not extract their contents!) in
/usr/lib/vmware/modules/source/.
After doing so, re-run the config script and you should not have any
more problems.
$ sudo /usr/bin/vmware-config.pl
What is the location of the directory of C header files that match your running kernel?
[/lib/modules/2.6.20-14-386/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.20-14-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-14-386'
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config2/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config2/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config2/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config2/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config2/vmmon-only/common/task.o
CC [M] /tmp/vmware-config2/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config2/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config2/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config2/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-14-386'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
The module loads perfectly in the running kernel.
Finish up configuration and you're good to go. To start VMware, simply
run vmware from the command line or from Applications > System Tools
> VMware Server Console.
Posted by Marcin on Sunday, April 22, 2007 in
Linux.
Hey everyone, for those who don't know, it's Earth Day today. Stop by
Home Depot and get a free light
bulb. Plant a tree,
clean up some garbage, ride a bike, carpool, get out there (weather is
great!) and have fun. Cheers :)
Posted by Marcin on Sunday, April 22, 2007 in
Other.
So I hit up the Security Bloggers
Network and
what do I see? A post on
Technobabylon with a bunch of
penises (sp?) some Indian dude with a Swastika shirt, and a whole slew
of personal infromation.. Someone doesn't like Ross Brown or eEye
Digital Security... Here's what was posted since the site was taken
down:
WhiteHat Manifesto: Life at eEye
[img removed]
Hi,
My name is Ross Brown, eEye Squirting Research CEO.
I'm an addict. I'm addicted to the same all-dancing, all-singing
crap that this so-called "security industry" is made of. I sell
utterly flawed products through my company and employ brilliant
individuals such as Marc Maiffret who can't even read. I also work
for the company who was behind Code Red and nowadays pretends to
promote "responsible disclosure". We are nothing but blood sucking
animals. We suck the motivation and altruism out of the really
talented people, and turn them into industry whores.
We are the ones making this whole security consultant image. College
degree, responsible individual with a dog and nice family, with a
feminist girlfriend who buys "French donuts" and cracks you up every
night. We are utterly hopeless, and thus we are being owned by crack
commandos from outerspace.
We have tainted the whole thing already. We manipulate people
through press releases, we release "0-day patches" and products that
allegedly protect from the problems that "the bad guys" create. We
are the ones who buy "exploits", information from third-parties and
anything that can boost our market share by spreading fear. We
create the problems for the solutions we sell. But we are retarded
enough that our own products are flawed to their knees. A single
look over their source code would cause you deadly diarrhea. I know
this because Tyler knows this.
All we do now is blogging, "podcasting" and utterly gay crap. We
would rather shut the fuck up but we feel like telling the world how
bad h4x0rs are and how they can snap off your cybercock.
[img removed]
We invented beautiful terms such as "responsible disclosure",
"vulnerability response time", "proof of concept", "penetration
testing", "ethical hacking", etc. We also invented rubber fists, but
that's another story.
I'm a whitehat and this is my manifesto. You may snap off my cock,
but you may not stretch my anus with a rubber fist. You may release
your evil 0days or own me with them. I'll stand anyway. Because I
have no other intention than buying CANVAS licenses and IDA Pro (ah,
we employ Andre Protas too, don't tell Ilfak about his leak of IDA
Pro 5.0 Advanced to CRACKLab.ru). I have no other intention than
fucking up the real sense behind this. I have no other intention
than building up a industry based on fear and public relations.
Space monkeys have been sent on mission. Fuck yeah, I pen-test the
world, ethically!
[img removed]
More information: http://technobabylon.typepad.com
In the meanwhile, please contribute to eEye's "Save a Whitehat"
campaign and share your credit card details with us:
Ross Brown American Express [cc# info removed]
[address removed]
Call me ASAP at my personal phone: [removed] Erotic line, 10
cents/min. Travesties and goats welcome.
rbrown@eeye.com - 60fdabb8659569b94166592e53876404 (I don't like
threesomes)
Regards.
Posted by Marcin on Friday, April 20, 2007 in
Security.
I'm looking for suggestions on any tools to reverse engineer programs
for Windows based systems. I have the *nix and BSD bases covered; I'm
just lacking a good, Windows toolkit. Particularly, tools to analyze
memory, disassemble, debug, etc... I've heard positive reviews for IDA
Pro, from DataRescue. Any other,
[free] alternatives?
Post a comment here, I appreciate any feedback. Thanks :)
Posted by Marcin on Wednesday, April 18, 2007 in
Security.
People panic!
Last night, TurboTax was
unavailable
for people to file their taxes. The problems have been since resolved,
but let it be a lesson to all of us that we cannot depend entirely on
technology. Technology will eventually fail us, like it did so many
people last night. Hopefully, those people have now learned that waiting
until the last minute to hand something in as important as your taxes,
should prioritize and get it done a couple weeks before the deadline.
These aren't your library books you'll be fined a couple cents for,
these are your taxes (you're only fined when you owe the government).
Taxes suck, but they make our economy go 'round.
At school, we hand in assignments and sometimes take quizzes or tests
online. At times, the servers have been known to go down and were
unavailable around midnight on Sundays (usually when maintenance was
being done). I'd get a message from a couple students CC'ing the entire
class they couldn't get their work in on time. You know what? Tough.. If
you had done it before you wouldn't be shitting your pants right now.
Regardless of the customers, TurboTax screwed up big time. Someone at
TurboTax should know its market share. People waiting until the last
minute is not news, and any company getting into such a business should
know that.
Lessons of the day:
- Don't wait until the last minute to do anything
- Plan for the worst, and implement solutions to mitigate (in this
case, heavy server loads)
- Let all of your customers know of any maintenance windows and any
unexpected periods of downtime
- Availability, Availability, Availability!
See Slashdot
for more commentary, and IRS on Filing Late
Returns
Posted by Marcin on Wednesday, April 18, 2007 in
News and
Tech.
