Multi-Boot USB Thumb Drive

February 14, 2010 at 01:34 (linux, Uncategorized) (, , , , , , , )

Ever thought it might be cool to only have an USB-Stick where all your individual security / pentest / recovery / hack-a-tack bootdiscs can be booted?

I thought so!

Crawling the Internet looks promising and shows two different ways how to get an bootdisc on your USB thumbdrive:

  • Booting a bootdisc as ISO stored on the drive (which is not compatible to most bootdisc’s)
  • Booting abootdisc ISO extracted to a extra Partition on the USB-Drive (which is more compatible)

Remember: both ways are possible on a single Stick, so you can have ISO’s there AND extra partitions with the contents of the original ISO.

Read the rest of this entry »

Permalink Leave a Comment

Microsoft, please get a XBOX QA-Responsible!

February 1, 2010 at 17:17 (Computer, Everything Else) (, , , , )

Lol lol lol…

What i really like when i hear “Microsoft” is that they want to make good products but they always manages to make a very uber big FAIL.
I must say im not a fan of this company – but i use, like a lot of people, some of their products.

Today i started playing XBOX360 () in a free time schedule i had between my job and my familiy…
Playing playing pla, – zzzz – Freeze
Damn. Ok no prob. Console turned off and on again.

But what the heck is that?! 3 red lights?
Fuck! This is the red ring of death.

Read the rest of this entry »

Permalink Leave a Comment

SipToSis with Asterisk

February 1, 2010 at 16:59 (Asterisk) (, , , , , )

I was little busy these days, had a lot of work to do like re-waterproofing my bathtub..

2010-02-17 Edit: Please Read the references i shown on the end of this Post to have an HowTo how to exactly install SipToSis! If i find the Time i can write a detailed Howto with Display environment variables etc, but only if i get some comments to do so :)

Nevertheless i finally managed to Get a working Skype <-> Asterisk connection via SipToSis. Hurray!
I didn’t get Skypeiax to work..

This is how i did it – with Asterisk 1.4.x branch on the same machine skype should also do – running Debian 5.0

Read the rest of this entry »

Permalink 1 Comment

Windows 7, Windows XP and the strange Active Directory

September 17, 2009 at 14:04 (Windows) (, , , , )

Windows 7 and Windows XP just give different errormessages for the same Problem, mainly when you are in MANY AD Groups (like me) and you want to work with that System:

Windows XP says most time: 
“Not enough Storage is availible to Complete this command”

Windows 7 says:
 “Naming information cannot be located because:

The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
Contact your system administrator to verify that your domain is properly configured and is currently online.”

Under Win7 even Outlook 2007 didn’t wanted to start!

Win7 Kerberos Problem

Win7 Kerberos Problem

Here is the detailed cause and solution to the Problem:

Cause:
The user is not able to authenticate because the Kerberos token that is generated during authentication attempts has a fixed maximum size.

Transports such as remote procedure call (RPC) and HTTP rely on the MaxTokenSize value when they allocate buffers for authentication. In Windows 2000 (the original released version), the MaxTokenSize value is 8,000 bytes. In Windows 2000 Service Pack 2 (SP2) and Microsoft Windows Server 2003, the MaxTokenSize value is 12,000 bytes.

If a user is a member of more than 120 groups, the buffer that is determined by the MaxTokenSize value is not large enough. As a result, users cannot authenticate, and they may receive an “out of memory” error message. Before you apply the hotfix that is described in this article, every group that is added to a user account increases this buffer by 40 bytes.

NOTE: In many scenarios, Windows NTLM authentication works as expected; you may not see the Kerberos authentication problem without analysis. However, scenarios in which Group Policy settings are applied may not work as expected.

Solution:

A registry parameter is available after you apply this hotfix that you can use to increase the Kerberos token size. For example, increasing the token size to 65 KB allows a user to be present in more than 900 groups. Because of the associated SID information, this number may vary.

To use this parameter:

  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry: HK_Local_Machine\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters*
  3. If this key is not present, create the key. To do so:
    • Click the following key in the registry: System\CurrentControlSet\Control\Lsa\Kerberos
    • On the Edit menu, click Add Key.
    • Create a Parameters key.
    • Click the new Parameters key.
  4. On the Edit menu, click Add Value, and then add the following registry value:
    • Value name: MaxTokenSize
    • Data type: REG_DWORD
    • Radix: Decimal
    • Value data: 65535
  5. Quit Registry Editor.

The default value for MaxTokenSize is 12000 decimal. We recommend that you set this value to 65535 decimal, FFFF hexadecimal. If you set this value incorrectly to 65535 hexadecimal (an extremely large value) Kerberos authentication operations may fail, and programs may return errors.

Permalink 3 Comments

ProLiant G6 and acpitabl.dat

September 17, 2009 at 09:06 (Computer) (, , , )

Had recently an ProLiant DL370 G6 which had an installed Windows Server 2008 that stopped working after doing HP Updates.

I had the following symptoms:
– Windows  is booting forever in the splashscreen
– in Safe Mode Windows stopped at “acpitabl.dat”
– PXE Boot was very slow – about 5 seconds reaction time between Keystrokes

After changing all Hardware, including Network Card and Array Controller P410, HP Technical provided us with the solution:

The Array Controller need to be placed in Slot 7 (it was in Slot 2) AND we had to clear the NVRAM (this is switching a dipswitch as shown in the Manual of that System)

Changing the Array Controller rendered Windows usable again, clearing the NVRAM recovered the PXE function useable :)

Hail to the King ;)

Permalink Leave a Comment

Recovering an D-Link DWL-2100AP after failed flash

September 16, 2009 at 13:27 (Computer) (, , , , )

My Colleague, namely Predictor, gave me recently a DWL-2100Ap which he managed to brick in trying to date the firmeware uo to a more recent.

A little while i didn’t find any Documents about it but then i found a simple description that shows me the Serial Port on that box.

After that i found some notices that D-Link has an backup-image that is loaded after a failed firmware update.

The trick is that you don’t reach that backup image Webconsole via 192.168.0.1 – which is standard for this system- but 10.0.0.1, then you can just give it a new Firmware and everything is fine again :)

 

This document let me to the right direction (don’t understand italia language but i can read the IP’s ;):
http://nag.ru/2007/0407/segreti-dwl-2100ap.pdf

Edit:
I “mirrored” the file in case the above Website is offline:
https://devbios.files.wordpress.com/2009/09/segreti-dwl-2100ap.pdf

Permalink 5 Comments

OpenVPN bridge and VMWare ESX 3.5

July 12, 2009 at 13:53 (VMWare) (, , , , )

These days i wanted to add an OpenVPN Server in bridged mode to my Network Infrastructure.

But there was one big problem: the OpenVPN System can’t live on a special Subnet and it cannot be routed through because the Network is maintained by other People which do not want to give me another Subnet and i don’t want to set the OpenVPN Gateway as default gateway in the Network.

 
So the only solution to this was a bridged OpenVPN Server and i set it up in my VMWare ESX 3.5 the following way:

VMWare ESX & OpenVPN

I can connect to the Server from Outside and get an IP-Address from the OpenVPN Server as specified in “server-bridge …..”

 

However i can’t connect to the other system’s in the Subnet, with tcpdump i only see a lot of “who-has” requests but it seems that the ARP replies didn’t go back to the Connected VPN Client.
I tried virtually anything and after a day of research i finally got it working. Why? Simple after all :)

  • First you need to enable Promisc mode for the Virtual Network, this is a setting of the vSwitch under the “Security”  Tab
  • Second, ensure you DO NOT connect more than one Network card to the Virtual Switch providing the vSwitch your OpenVPN Server is connected. That was my main problem.
  • Third, ensure you enable ip_forwarding -> “echo 1 > /proc/sys/net/ipv4/ip_forward”
  • Forth, if you do ping tests and your VPN client is Windows, double, triple-check the firewall is off :)

 VMWare Single

After removing the other Network cards from the Virtual Switch i could reach my complete Network instantly!

Permalink 20 Comments

Back to World

July 12, 2009 at 09:29 (Uncategorized)

Hi ppl!

This is my first entry, so i think i would better introduce me to you :)

I’m BioS, a not the best english writing german boy who is called a “Freak” by his colleagues, intrested in Electronics, Networking, IT, Security and everything else that can be powered..

Told as a young boy not to sit all day long in front of the C64, now earning his money with this kind of hobby.

Have a family with a little child which is trying to use Backtrack with 10 Months and a wife who plays in the evening WoW with me :)

Okay, enough for now..

Permalink Leave a Comment

« Previous page