When installing Backtrack 4 on a Windows Virtual PC VM this afternoon I got an error when attempting to start the X server. After initially booting the DVD inside the virtual machine I set up for the Backtrack 4 installation I got the error starting X with the startx command. Resolving it was easy for me though I don’t know that it would always be as easy for others. Below I describe the error received when starting X and what I did to resolve the problem.addscreen/screeninit, backtrack, bt4, error, fatal server error, fixvesa, GUI, installation, startx, virtual machine, VM, x11, xorg, xorg.conf, xorg.conf-vesa
Posts Tagged “GUI”
Apr 13 2010
This is going to be a little bit of a different style post then we usually do on Question-Defense. I have been completely amazed lately at the amount of unsecured web interfaces on the Internet and I figure another post cant hurt. I am assuming every one knows that when you buy a new piece of hardware you need to change the default user name and password. “well of course I know that” most people would say. Well how about we do a little recon and see if that is really true.default, GUI, HTTP, HTTPS, insecure, Internet, login, password, purehate, shodan, web
Apr 30 2009
I beat my head on the wall for awhile with the below error because the information online was fairly limited. Let me start by saying that using TortoiseSVN as a SVN client for Windows will authenticate against a Linux server running svnserve using SASL DIGEST-MD5 encryption. This means you should be able to authenticate against svnserve set up with these options configured which are “use-sasl = true”, “min-encryption = 128″, and “max-encryption = 256″.
When all of this started my goal was to create a SVN server with one repo for testing. I upgraded from TortoiseSVN 1.5.2 to the latest stable build of TortoiseSVN which was version 126.96.36.1992. I downloaded the latest stable release from the TortoiseSVN site here. Once installed everything was going fine with my original goal until I got to checking out the repository on my local PC.128-bit, 256-bit, CRAM-MD5, DIGEST-MD5, error, failure, GUI, SASL, Subversion, svn, tortoiseSVN, windows, xp
Mar 13 2009
If you are having trouble communicating between the wired and wireless networks after installing or upgrading your Linksys WRT600N wireless router with dd-wrt firmware then the issue is likely related to the VLAN configuration. After you flash the firmware on a Linksys WRT600N you will have the default dd-wrt settings. One of these settings includes separating the wired and wireless traffic because this is the correct way to secure things because the wireless network is much more likely to be breached than the wired network. Switching this setting to allow communication between wired and wireless devices is easy by following the directions below.
It is easy to add static DNS entries to the dd-wrt GUI interface. Follow the below simple steps and then reboot your router. In the below directions the dd-wrt version is v24-sp2.