OpenBSD Tentando porting do Virtualbox (draft)

Ontem (23-06-2012), tentei pela primeira vez (mas era um desejo de uns 5 anos atrás), o porting do código-fonte do virtualbox para OpenBSD, tornando mais um host de virtualização.

Quando saiu o primeiro porting do Virtualbox para FreeBSD, achei que viria para OpenBSD, também.

FreeBSD build instructions
https://www.virtualbox.org/wiki/FreeBSD%20build%20instructions
http://dgz.dyndns.org/mediawiki/index.php/%28OBSD%29_HOWTO_Install_VMWARE_tools_on_a_OpenBSD_system
http://www.h-i-r.net/2009/11/virtualbox-full-screen-resolution-for.html

The FreeBSD build instructions are being worked on as the FreeBSD port advances.

If you like to help out with the FreeBSD port, please join the #vbox-dev irc channel or drop a mail on the development mailing list.

Current state: It works quite stable by now for FreeBSD 7.x and 8-CURRENT. There is a port in the FreeBSD ports tree too.
Prerequisites

You need:

[OK]    GCC 3.2.3 or later (except for the GCC 4.0.x series)
=> The default GCC should be fine.

[OK]    Yasm 0.6.2 or later
=> /usr/ports/devel/yasm

[NOK]    -> Freebsd
as86 (real mode assembler, usually part of the dev86 or bin86 package)
=> /usr/ports/devel/dev86

[NOK] -> Freebsd
bcc (Bruce Evans C Compiler; often part of the dev86 package)
=> /usr/ports/devel/dev86 (same as above)

[NOK]
IASL (Intel ACPI compiler)
=> The one installed into /usr/sbin/iasl should be fine.

[OK]
xsltproc (libxslt, XML style sheet processor)
=> /usr/ports/textproc/libxslt

[OK]
libxml2
=> /usr/ports/textproc/libxml2

[NOK]    -> Freebsd
libXcursor (required to support color mouse pointers in guest)
=> Probably installed, if not try /usr/ports/x11/libXcursor.

[OK]
libpng
=> /usr/ports/graphics/png

[OK]
libIDL
=> /usr/ports/devel/libIDL

[OK]
libSDL
=> /usr/ports/devel/sdl12

[OK]
mkisofs (required only for additions which aren’t supported yet)
=> /usr/ports/sysutils/cdrtools

[NOK] -> Freebsd
kBuild (The one provided with the VirtualBox sources doesn’t with FreeBSD 8-CURRENT)
=> /usr/ports/devel/kBuild

[OK]
curl
=> /usr/ports/ftp/curl

[NOK]    -> Freebsd
libXmu
=> /usr/ports/x11-toolkits/libXmu

Qt 4.4.x
[OK]
=> /usr/ports/x11-toolkits/qt4-gui

=> /usr/ports/net/qt4-network
=> /usr/ports/devel/qt4-moc
=> /usr/ports/net/qt4-uic
=> /usr/ports/net/qt4-rcc
=> /usr/ports/net/qt4-linguist ; or configure –disable-qt

Building VirtualBox

Change to the root directory of the sources and execute the configure script:

./configure –disable-hardening

If it finds everything it needs, it will create a file called ‘AutoConfig.kmk’ containing paths to the various tools on your system. Also, it will create an environment setup script called env.sh. This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten).

The switch –disable-hardening should not be used for building packages for redistribution or for production use.

Whenever you want to build VirtualBox, you have to open a shell and source the generated environment setup script ‘env.sh’, i.e. do

source ./env.sh

To build a release package, type

kmk all

This produces the required binaries in out/freebsd.x86/release/bin/. If you want to build a debug version, type

kmk BUILD_TYPE=debug

In case you have more than one CPU core, kmk will automatically do a parallel build.

Running your build

You can run VirtualBox directly from the build target directory (out/freebsd.x86/release/bin/).

You have to load the kernel driver first using kldload ./vboxdrv.ko as root. Make sure you give yourself read and write access to /dev/vboxdrv.

If you made a hardened build, make sure that the setuid stubs have the correct permissions:

for f in VirtualBox VBoxHeadless VBoxSDL VBoxBFE VBoxNetDHCP VBoxNetAdpCtl; do
chown root.root $f
chmod 4511 $f
done

Finally, you can start one of the frontends, e.g.

LD_LIBRARY_PATH=. ./VirtualBox

SAP NetWeaver 7.0 – Trial Version on Linux / SLES 11 PoCs

SAP NetWeaver 7.0 – Trial Version on Linux
Click here for download

This Sneak Preview on Linux includes SAP NetWeaver 7.0 ABAP and J2EE 7.0 Application Server, SAP NetWeaver Developer Studio (Windows Version), Web Dynpro ABAP and Java, SAP Interactive Forms by Adobe.

System Requirements:

  • Min. 1536MB, recommended 2GB RAM
  • Intel Pentium IV or higher
  • 15GB hard disc space
  • Download 64-Bit Linux Version for x86_64 based upon MaxDB 7.6(7x650MB)

To use SAP Interactive Forms by Adobe, you must install the necessary credential file and activate it using a unique password. Download the latest credential and password from SDN.

http://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/60d6c8b7-5d8f-2910-31bf-ebdf74fefd8b

SAP MAXDB 7.8.02.27 FOR LINUX (X86, 64 BIT)

Click here for download

With this installation package you install the SAP MaxDB software. This package is not for use with SAP applications. For that purpose, refer to the Download Area in the SAP Service Marketplace (login required). To install the software, download the package on your local computer and double-click the file. Installation Manager opens and leads you through the installation process.

System requirements

SAP MaxDB License (PDF)

Documentation

http://www.sdn.sap.com/irj/scn/maxdb-downloads?rid=/webcontent/uuid/10854ce1-72b4-2e10-f1a3-8d58d06fc312

SAP MAXDB 7.7.07.33 FOR LINUX (X86, 64 BIT)

Click here for download

With this installation package you install the SAP MaxDB software. This package is not for use with SAP applications. For that purpose, refer to the Download Area in the SAP Service Marketplace (login required). To install the software, download the package on your local computer and double-click the file. Installation Manager opens and leads you through the installation process.

System requirements

SAP MaxDB License (PDF)

Documentation

http://www.sdn.sap.com/irj/scn/maxdb-downloads?rid=/webcontent/uuid/1034dff6-70b4-2e10-5595-96c9da57a3db

SAP MAXDB 7.6.06.22 FOR LINUX (X86_64, 64 BIT)

Click here for download

With this installation package you install the SAP MaxDB software. This package is not for use with SAP applications. For that purpose, refer to the Download Area in the SAP Service Marketplace (login required). To install the software, download the package on your local computer and extract it. Run SDBSETUP to start the Installation Manager, which leads you through the installation process.

System requirements

SAP MaxDB License (PDF)

Documentation

http://www.sdn.sap.com/irj/scn/maxdb-downloads?rid=/webcontent/uuid/e02edb07-a9b3-2e10-5abe-f74c3dbb6af0

The Complete SAP MaxDB Documentation

http://maxdb.sap.com/documentation/

http://www.sdn.sap.com/irj/scn/maxdb-downloads

Downloads

http://www.sdn.sap.com/irj/scn/nw-downloads

SLES 11 for SAP

https://www.suse.com/documentation/sles_for_sap/sles_for_sap_guide/?page=/documentation/sles_for_sap/sles_for_sap_guide/data/s4s_inst_inst.html

Difference between Kali Linux and and Backtrack 5

The most obvious is the shift from Ubuntu to Debian . You’ll immediately feel the difference in the looks and feel of the new Kali Linux.
There are no puny errors like “Error connecting to wicd’s D-bus bla bla” when you try to fire up Wicd in Backtrack 5. Kali Linux is much cleaner in these respects than Backtrack 5.
Kali Linux is more stable than Backtrack 5. However, my Kali has hung up on a few occasions, but I’m guessing that’s coz of some crappy package I installed because I keep trying out new packages on Kali.
In Kali, There’s no /pentest directory like in Backtrack 5. Personally, I don’t miss it and neither should you, because now you can fire up any tool just by typing it’s name in the shell.
They have removed Nessus Vulnerability Scanner in Kali, You can manually install it by downloading it from Tenable. However, I don’t understand why they removed it from default tools in kali, coz I really liked scanning for Vulnerabilities in Nessus. May be coz Nessus itself has security bugs??
Kali Linux is Smaller in size than Backtrack 5 (which was around 3 GB if I remember correctly). Kali’s ISO is just 2 GB in size. They’ve separated “Top 10 Security Tools” in the Menu of Kali Linux which contains some much-hyped security tools.
Bluetooth works great on Kali Linux. I don’t know about you, but I faced a lot of trouble getting my bluetooth up in Backtrack 5 r3, really frustrating. But in Kali Linux, bluetooth works fine with a click of a mouse, which helps me pen test bluetooth devices with ease now.
VLC Player comes pre-installed with Kali linux. This was not the case with Backtrack 5 where you had to manually install it and then it gave you an error saying “Won’t run in root mode” and then you had to hex-edit the VLC binary. In Kali VLC is pre-installed (however I did notice some lag problems in VLC in Kali).
Firefox has been replaced by Iceweasal which is again a good move. They are both given by Mozilla and very similar. However like Firefox in Backtrack comes with ‘noscript’ and such add-ons for security, Iceweasal in Kali comes clean.
That irritating light pdf viewer in Backtrack has been replaced by ‘Document Viewer’.
No ‘gedit’ in kali, instead you can use ‘Leafpad’
In Backtrack, there wasn’t a way to control your back-light. I remember searching for a way to control back-light but not finding it. It was set to Max by default. Very tiring for the eyes. No such problem in Kali Linux
Streamlined repositories synchronize with the Debian repositories 4 times a day, constantly providing you with the latest package updates and security fixes available.Relentlessly packaging dozens of useful tools, painstakingly making sure our packages are Debian compliant.
Many of the tools in toolbox need to be “bleeding edge”. This means we have take on the task of packaging and maintaining upstream versions of many tools, so that our users are constantly kept up to date where it matters.
As our source packages are now also Debian compliant, you can quickly and easily get the required sources of each tool, then modify and rebuild them with a couple of commands.
One of the many benefits of our move to a Debian compliant system, is the ability to Bootstrap a Kali Installation/ISO directly from our repositories. This means that you can easily build your own customizations of Kali, as well as perform enterprise network installs from a local or remote repository.
Kali Linux installations can now be automated using pre-seed files. This allows for enterprise wide customization and deployment on multiple systems.
BackTrack 5 brought with it new support for ARM hardware. Our ARM build-bot was a modified Motorola Xoom tablet, which suffice to say, didn’t last for long. To help remedy this, Offensive Security has donated a Calxeda ARM cluster to our project, allowing reliable and long term development of Kali Linux ARM images.
Our new build and repository environments allow for complete flexibility in generating your own updated Kali ISOs, with any desktop environment you like. Do you prefer KDE? LXDE? XFCE? Anything else? Then change your Kali desktop environment yourself.
Another benefit derived from the move to a Debian compliant system is the ability to seamlessly upgrade future major version of Kali. No longer will you have to reinstall your penetration testing machine due a new version of Kali coming out.

Reference :

http://www.kali.org/news/kali-linux-whats-new/

http://metasploit.hackplanet.in/2013/05/difference-between-kali-linux-and-and.html?goback=.gde_1080357_member_244219695

Quick and Dirty – Eclipse – Instalando plugin Perl

Falando Quick and Dirty como fazer com que a IDE Eclipse instale plugin Perl e o ambiente de programação reconheça scripts perl com debugger.

Na verdade, isso é mais para uma demonstração, pois prefiro fazer a codificação de scripts perl no VIM, mas se por algum motivo quiser usar o Eclipse, siga os passos.

1. Passo:

O plugin do Eclipse para Perl se encontra em:

http://e-p-i-c.sf.net/

Screenshot from 2012-12-26 01:22:21

Screenshot from 2012-12-26 01:23:06

Screenshot from 2012-12-26 01:23:24

Screenshot from 2012-12-26 01:23:45 Screenshot from 2012-12-26 01:24:09 Screenshot from 2012-12-26 01:25:06 Screenshot from 2012-12-26 01:25:30 Screenshot from 2012-12-26 01:25:57 Screenshot from 2012-12-26 01:26:27 Screenshot from 2012-12-26 01:26:38 Screenshot from 2012-12-26 01:26:58 Screenshot from 2012-12-26 01:27:19 Screenshot from 2012-12-26 01:28:03 Screenshot from 2012-12-26 01:28:52

 

@firebitsbr