Hi All,

Been a while, but I have been busy and took my LPIC-101 exam, which I failed.... :-((( So I scheduled a new one in May. I won't go into real detail, but I was nervous as hell and that might be one of the reasons why. Also I concentrated on the wrong things I guess and probably under estimated the exam a bit. But hey, next time better.

These were my results:

First two are pretty good, but I need to concentrate more on the last two. Good to know for next month!

I updated the site with a new section called Documents, which will be filled up with documents that I find useful, documents that are harder to find and exam preps. I just wanted to have everything in one place, so instead of filling up my Google Drive I thought I would share and keep it a bit organised this way for people to browse through. Most of the time (because of the business model behind it I guess) good documents and training material is hard to find, because that's where people want to make money when it comes to Linux and / or free software.

Another thing you might have noticed is the usermenu. If you sigh up, you can keep your test results and it will remember where you left off the last time.

Have fun!

regards,

CornElvis

Hi All,

 

Not much of a daily blogger hey? LOl

But anyway, I have been busy working and stuff like that and busy building a KALI Linux machine on my trusty Dell E6410.

I have build it from USB with Rufus and a Kali ISO image. Everything went pretty fine actually. Only thing is when I boot up and log in it just hibernates and then when I click the on/off button again it boots in straight away....really weird.

I don't see anything I can use when running dmesg but anyway. It works and it works properly as far as I can tell.

The funny thing is because everything is ran as root in KALI, Chrome is complaining its ass off, so I use FireFox ESR for now and I probably stick to it.

I already used pen-testing tools like airmon-ng, aireplay-ng and aircrack-ng. Couldn't hack into the naeighbours wifi but I was close enough. Tested my own wifi security as well and it seems to be fine. Thing I never will understand that it comes to a word list at the end and then trying to figure out the password... I would expect that I could check character by character instead of a fixed word, but maybe I am missing out. I am a rookie anyway and learning a great deal at the moment.

I used this article to learn and try out : http://lewiscomputerhowto.blogspot.nl/2014/06/how-to-hack-wpawpa2-wi-fi-with-kali.html

I have to run now, but will be back with more stories soon.

Have fun and take care

 

CornElvis

Hi,

It has been a couple of days, but I have added 10 more questions to the LPIC-1 test. Chapter 14 this time, so 6 more to go from the book. I hope you learn from it and will enjoy what I done there.

The test didn't seem to take 60 questions somehow, so I added up to 145 now. I noticed that you can come back and it will get back where you left off, unless you clear your browser's cache of course.

Regards,

CornElvis

Hey All, (whoever this is reading anyway)

I haven't been writing for a while due to the fact I was busy with all sort of things.

Mostly linux, work and music though.

I am using Kali now and I am learning all sort of things about pentesting, vpn and the whole hacking community.

I messed up my kali root partition the other day and luckily Linux creates a new "home" directory structure for you at next log on. AFter I messed up I realized I needed to backup my own stuf as much I can I created a crontab job to backup every hour.

If you haven't made one, here is the the command to check if you have anything running: crontab -l (to list it) and if you don't have anything it will be all commented out. There is a example thing in it and if you google it a bit you can do what every you want with it,

Mine is looking like this now:

# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
0 */1 * * * tar -zcf /var/backups/bckp.tgz /root/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command

 

I also made sure it is opening with leafpad when I open it with crontab -e, but that's up to you and your distro.

I had to recreate my .bashrc file again and I have set it to this now:

##################################Custom .bashrc Script##################################
#bashprompt
export PS1="\[\e[1;33m\]\u@\h->\[\e[m\] "
#aliases
alias cls="clear"
alias ls="ls -lai"
alias lfp="leafpad"
#default editor
export EDITOR=leafpad

Also I had made a adjustment to rc.local which I shouldn't and that's where it all started with. I wanted to get that fixed, which made me copy paste and error into the code which remove my ~ directory.......duh.... just because of an space that occurred in the command out of laziness by copy paste from a website! So f.... stupid. Before I knew it my background disappeared and my notes / files were gone. Luckily it wasn't much, but still enough to make me swear! Ah well must have been that learning curve..

Anyway, I have it all fixed again and I fixed that rc.local thing as well. I took out the extra line I had put in there in the first place and forgot all about. So actually I fixed the thing I messed up in the first place, to mess it up even more and then clean it up ;-)
It took me hours to find that out. Every google you do leads to something else, until you interpret some of the answers properly: "rc.local is obsolete, it shouldn't be doing nothing at all" ...go figure when you try to fix an error.... SO you shouldn't be fixing anything, YOU SHOULD NOT USED IT!!

It turned out well, anyway.

there should be nothing in you rc.local file except the : exit 0!
This is what mine looks like now

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Numlock enable
#[ -x /usr/bin/numlockx ] && numlockx on

exit 0
I had the line with the numlock enabled, because my numlock isn't enabled when I start.

As I know google is your friend, but it can be your enemy as well.

Have fun and a great weekend.

Regards,

CornElvis

 

Hi There,

didn't add any new questions to the test, but I did configure it to be 60 questions and take random questions out of the 135 which are there at the moment. Will add some more this week, but I had a busy weekend and a birthday party today, so I was occupied for most of the day.

I decided to make my machine dual boot and not the conventional way, because I don't have a USB stick available at the moment and I don't have writable DVD's at the moment either. 

I have a Dell machine (E6410) and have 2 disks in there, one is a Modular Bay HDD and is 120GB in Size. SO I took that one to be my main Linux disk. This way I can just pick the Bios bootloader to start from the Modularbay HDD instead of fooling around with a Grub2 bootloader and also decreasing the risk to mess up my Windows 10 system, which is spinning just rigth for me at the moment (Will need it to run Cubase, Roland Studio Capture and stuff like that, so as long as I can't run that on a Linux machine I am stuck with Windows anyway)

So how did I manage this to begin with? I tried to figure out how to start ISO's from a HDD and found pretty soon that I needed grub for that again and needed a running Linux machine to do that in the first place. What I done in the past and will do again is to configure VirtualBox to use my entire drive to install Linux on. Google it to find stuff about it, but here is the "monkey" trick, because VBox doesn't have it out of the box. You should go to a command prompt and CD to the following location:

CD C:\Program Files\Oracle\VirtualBox

There you can run the following (make sure you run CMD as an admin btw)

VBoxManage internalcommands createrawvmdk -filename "C:\Users\[username]\Path\to\VMs\[yourVMfilenamehere.vmdk]" -rawdisk \\.\[Your Target Drive here]

To find what the name of your target drive is you can go the Disk manager and check the number on the left hand side:

 

So in my case it is Disk 1 and the name will be \PhysicalDrive1 and will look similar to this: "C:\Users\[username]\Path\to\VMs\[yourVMfilenamehere.vmdk]" -rawdisk \\.\PhysicalDrive1

Another hint, you need to run VBOX as an admin otherwise it will salute you with an error that it can't open de vmdk file to begin with.

Then a second hint, make sure you delete the partition and leave it Unallocated as in the screenshot above, otherwise (at least mine did) Linux will error out that it can't write to it, BLK errors etc. I had it formatted with exFat and a drive letter assigned to it in Windows and I guess Windows kept it in use.

At the moment I am in the middle of installing Kali Linux to it, and all seems to go well now as I am writing this.

When I installed successfully I will update this article or write another tomorrow

Have fun and keep things simple ......!

;-)

Regards,

CornElvis