Something wrong with my Virtualbox 5.1

Unfortunately my virtualbox 5.1 is crash and freeze the desktop

Yes and that was just happen to me recently and it makes me frustrate. Everytime i try to start the virtual machine in my virtualbox, it end up freeze the host and i cant do anything much at that time, i can only push the power button long enough to power off my laptop but that was not fixing the problem turns out it happen again and again. so if you having same problem with me, i recommend you to uninstall everything that have connection with virtualbox including the dkms.

so i uninstall of the all utility:

~# sudo apt-get purge virtualbox virtualbox-dkms dkms

and i try to install the version 5.2:

~# sudo nano /etc/apt/sources.list (update the sources.list file)

~# deb http://download.virtualbox.org/virtualbox/debian xenial contrib (add the following line at the end of line or at the first line)

~# wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add - (to add the respository key)

~# sudo apt-get update (update the changes)

~# sudo apt-get install virtualbox-5.2

~# sudo apt-get install dkms

and its done ! fortunately the virtual machine is running smoothly

actually i don't know what is the cause of the bug, but it was start when i try to install vagrant in my host OS, i kinda skeptical that vagrant is the cause of the problem. so i will try to search for more clue and tell if i find the answer.

Comments

Having fun analyzing nginx log to find malicious attacker in the net (ง'̀-'́)ง (day 37)

What makes you sleepless at night? is it because of a ghost or scary stories? is it because you have an important meeting tomorrow? or is it because you have an exam? For me, what keeps me up all night is that I keep thinking about what happens to a website that I just created, is it safe from an attacker (certainly not) or did I missing some security adjustments that lead to vulnerability? well I'm not the best secure programmer in the world, I'm still learning and there is a big possibility that I can make a mistake but for me, a mistake can be a valuable investment to myself or yourself to be better so from this idea, I want to know more about what attackers casually do when attacking a website. Here in this post, I'm going to show you how I analyzed attack to the website that I have permission to design and also some interesting findings that I could get from the analysis Background: All of this analysis comes from the traffic that is targeted to th...

Utilize Pwntools for crafting ROP chain :') (day 69)

who doesn't like pwntools? it is a very versatile tool and can be customized according to our need using the python script but did you need to know that pwntools itself can help us to automatically craft a rop chain for us? so in this post, I will show you how to make rop chain less painful and make pwntools do all the heavy lifting. To demonstrate this I will use the binary challenge callme 64 bit from ropemporium link: https://ropemporium.com/challenge/callme.html Crashing the app: Like any other exploitation process, we need to crash the program by generating a long string pattern to determine the offset. based on the information from the above figure we can see that we required to provide 40 bytes of offset Fun stuff: now this where the fun stuff began write the following python script: as in the guideline of the challenged said we need to chain the function call by first to call the callme_one function, callme_two function and then callme_three funct...

Make writing shellcode in linux 32 bit little bit simple (ง'̀-'́)ง (day 53)

Disclaimer: This post is only for education only and not for causing destruction to a lived system. Be smart! In every exploit development process, the shellcode is one of the vital components to making your exploit reliable. Shellcode itself is just basically an assembly instruction that converted into opcodes (the hexadecimal thingy) "\x6a\x66\x58\x99\x6a\x01\x5b\x52\x53\x6a\x02\x89" "\xe1\xcd\x80\x89\xc6\x5f\xb0\x66\xb3\x04\x52\x56" "\x89\xe1\xcd\x80\xb0\x66\x43\x89\x54\x24\x08\xcd" "\x80\x93\x59\xb0\x3f\xcd\x80\x49\x79\xf9\xb0\x0b" "\x52\x68\x2f\x2f\x73\x68\x68\x2f\x62\x69\x6e\x89" "\xe3\x52\x53\xeb\xca"; that will instruct the program what to do next after the exploitation process is done But when it comes to creating it not many people willing to devote their time to learn it, they rather to just used a precompiled shellcode for example that come from http://shell-storm.org/ because they think that is some...

Court of Analysis and Testing

Search This Blog