Friday, April 20, 2012

Right then, it's been a while but I thought I just had to share this newish (well newish to me) Linux distro.

NodeZero

A Distribution based off Ubuntu and also uses the normal Ubuntu repositories. It is basically a ubuntu with some penetration tools pre-installed that tries to look like a cooler windows Vista. If you've ever used BackTrack you'll only be interested in this if you thought it was too Linuxy.
Note: This is not my video. Straight from Utub.
You know what? I don't even recommend this, it's like going from a escort to a street hooker. Clearly BackTrack has the market share, well I'll be keeping an eye on what these boys come up with in the future, follow the utub link for more info and download links.



Tuesday, November 29, 2011

General commands

Well I'll format this a bit later, but for now it's just a few commands that are generally getting asked about...

Password stuff:

Change your nickname password:

/msg NickServ SET PASSWORD pass

Where 'pass' is your new password

Seriously with NickServ you don't need the 'msg' as /NickServ SET PASSWORD pass will work fine too.

*note, you need to be logged in as the nick


Userhost command:

/userhost 'stagnate'

where 'stagnate' is the user, will give you the host info of the nick. Useful for bannings etc.

Help Op

/helpop <?-!> question

? denotes to query the database, where ! will just ask the help operators.

QUOTE LIST
This command gives various details on rooms available in opera.
Command:

/quote list <option>
or
/raw list <option>

Options:
Not setting an option will give the full list of rooms.

> followed by a number eg: /quote list >23  will give you the list of rooms with more than 23 persons in it.
< followed by a number will give rooms with less than that prescribed number.
*mask* Matches a room to a mask
!*mask* Shows rooms that don't match a mask.


SET NAME

/setname >newname<

Allows you to change your 'real' name without disconnecting.

Thursday, June 9, 2011

IRC opera banning - to ban nicknames

Okay, I've been writing this up for ages now, it's getting nowhere so I thought to upload it and then I'll be forced to edit it sooner because everyone can see how shitty it is.So be warned - This is the first draft!
*This is now a quick edit, second draft.... Don't know what the changes will be yet.


Banning


By now you've see some cool stuff, pretend log-on scripts and a bit of privacy stuff.


If you decide to create a room in the Opera network with the Opera browser and it gets popular.....
You'll need to think about banning, auto kick and operator commands.
First off, lets say you have a cool new room: #cool_room we'll call it.
You've registered it, assigned one of your mates to gain full ops or half ops, and protect them.
That's great.
But now a particular annoying user keeps joining and being a nuisance...
You could start off just by right clicking their name and using the kick/ban options. This should be fine for most users. Adding to the ban list for that channel.

*note: The ban list is forgotten whenever the room is completely empty.
So if you're not running a bot to keep the room 'open' you should think about putting the ban list in the log-on commands list. See HERE.


Right, lets say a user 'lupin' is being really annoying, first warning you kick 'lupin' from the room, second time kick and ban him/her. - Usually just ban a nick for 1 - 8 hours depending on what I'm doing. If the user is mucking up again chuck their IP address into the ban list forever.




If the user doesn't come back - problem solved... But...
But then this nick keeps coming back and coming back!



It gets a bit tedious to keep putting ban after ban on.
First lets understand what's happening:
The user has a dynamic ip address - This is fine, most people do unless they're running a web or file server of some sort.

So under windows, all they have to do to change their ip address is in the command prompt: ipconfig /release and then ipconfig /renew.
Or most would just restart their router.
Both just request a new ip address from their isp.
So the commands for banning are as follows:

/mode #cool_room +b *!*@80.232.43.46




Now this will put a ban on the IP address only and all the users attributed to that IP address.

Alternatively you could use:



/mode #cool_room +b *!*lupin



And just ban the nick.

Right now the real surprise happens when the very same nick comes right back! This is caused by that dynamic ip stuff.
 So now to put a 'wild-card' in the banning command:

 /mode #cool_room +b *!*@80.232.43.*

The '*' bans the complete range of numbers from 0 - 255 in the last octet of the ip address. This will usually foil the nickname.
 If not;
 /mode #cool_room +b *!*@80.232.*.*

Will most certainly ruin their plans.
*note:  '/mode #cool_room +b *!*@80.232.*' will not work in opera irc at present, don't know why really.

There's a whole lot more to banning - Such as using ChanServ to kick and ban users, but opera does have decent documentation on that so I'll skip it..

Sunday, May 1, 2011

Log-on scripts for irc (Opera browser)




So you'll all know by now that these irc details are aimed for people that are using the Opera browser with its built-in irc client.
See Here for more info on that stuff. Once read, you should be fine with simple commands, masking your IP address and stuff.
There are lots of persons that are new to irc and only even heard of it through installing Opera. It is for these people that I write this. And any others that would like to see what they can 'do' with Opera.

Making a log-on 'script' 

The Opera browser doesn't by default include a way to integrate a log-on script like rub or python.
So we'll have a look at integrating commands to initiate upon connection.
It's really not that difficult to make simple commands run on login, and if users want to run more than just commands they'll use another irc client.


So, in the Opera menu navigate to mail and chat accounts > open the account you wish to configure > click on the 'outgoing' tab > now you'll see a text box underneath 'Perform commands when connected'

The GUI will look something like this (I've added some commands in):
The text box with with various commands is what you want.






The log-on commands explained:


So /msg NickServ IDENTIFY *******

Just logs me in. Yes you should love this, instead of typing it in every damn time you want to start chatting on Opera!
Note: I have added '*******' this isn't my password!
And sure if someone gains access to my computer they can find out my password. But I'm not really that paranoid!


/mode stagnate +x does what?? See HERE 

/mode stagnate +T

Where 'stagnate' is your nickname.
This command prevents other users from using the /ctcp command (Client to client protocol) to your nickname.

/join #opera 

Yes so now you can auto join channels upon connection...
Note:  /j #opera is just the shortened version of /join #opera and both work the same.

/silence + superstar
Please note needs the + to work, I forgot to put it in the screen shot..
This will prevent annoying pm's (personal messages) from the nickname 'superstar'.

/motd
-This command gives the 'message of the day': motd! If you've ever used the CISCO CLI you'll know all about this command.

If you are a room operator you can set your bot to automatically chuck in bans ect. But I don't think any one would dream of running a bot through Opera any time soon...



Synopsis:
Cool, so now you can go forth and create a set of log-in commands that Opera will automatically enter on your behalf when connected. It can be very handy for those methodical commands.

*Next week: How to run a bot through Opera



Wednesday, April 27, 2011

Privacy in the irc world


Hi! Right then. 
Note: This piece is assuming users (you) have at minimal basic irc knowledge.
Go and check out the Introduction for the previous entry on irc commands.


So you've registered a nickname and cruised around a few channels right?
Great!
Now we'll talk privacy.

What users can find out about you, and how to stop them.

First off, if you've just joined irc, the chances are that your ip address is showing and quite possibly ( I see it a bit ) your real name and/or email address can be easily found. From this, malice users can commence port scans, ping your address to hell with broken 'ack' requests and the like, find out your facebook details, and heaps more details to scare the heck out of you. Just remember that when opera prompts you for your 'real name' and 'email' this information is clearly visible to all other users (excluding the domain name of your email address).


The commands that users can use and their meanings.

First we'll start simple.
The /who <nick> command

typing /who stagnate 
Would give you the default information on a nickname.
The outcome of this command will look like this:

#ruby bill CPE-124-177-167-92 irc.opera.com stagnate Hr 0 bob lehcror

#ruby being the channel the user last joined 'bill' being the users 'email address' -

*Note: Users will know that most persons will be using @hotmail, @yandex or any other popular mail servers - so it's not too hard to fill in the gap.

 - that opera asked for. CPE-124-177-167-92 being the users connection (ip address) and 'bob lehcror' being the users 'real name'

More information can be acquired by the /whois command which can be shortened to /w

Not to be missed is the /whowas command, this gives some info on a few of the last connections a nick has made.

Access list

NickServ stuff
There are a few different servers on the network (NicServ, ChanServ, HelpServ, BotServ and MemoServ)


Using NickServ to find info
/msg NickServ info <nick>
This command will bring back info such as; last seen on the network, time and date registered and any options that the nick has configured.

/msg NickServ status <nick>
This give info on the status of the nickname you input. NickServ will give back the status 0 1 2 or 3
0 is off-line
1 I don't know
2 registered but only with the access mask
3 on-line and registered


Client to client protocol
Using the command of /ctcp users can discover what o.s. and irc software you're using, and some other stuff

typing the command /ctcp <nick> version
will give back something like this:

VERSION Opera/9.80 (X11; Linux i686; U; en) Presto/2.7.62 Version/11.01

So a user can find out what operating system, platform and irc client you're using.
This info is fine to share mostly, some irc clients block client to client protocol by default, or have witty replies built in.

The <ping> command and <time> can also be used in /ctcp through the opera irc client.
These will be entered in the same format eg: /ctcp <nickname> time

Note: ctcp queries will bring up results in a new window when using the opera built in irc client. These queries cannot be seen by a general opera user.


DCC

Direct client connection
This allows the sharing of files between users.
In opera this will always prompt you to accept or decline. If you're not sure don't accept!
It's something like: /DCC send <nick> <file>
Just right click the users name you want to send something to in the user list, it's heaps easier.
Note: Some routers will block some ports that DCC use by default and can cause headaches ~. 




Okay, so in summary we can see that other users can see: 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 

Your I.P. address
Your real name (If entered)
Part of your email address (If entered)
Any security protocols you may be using (ssh, ect)
Your operating system
Your irc client

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


That's quite a bit of info other users can gain from a few simple commands right??
But relax! There are just not that many irc users out there that can really 'DO' stuff with that info, harmful stuff I mean. Sure. the average user might find your facebook, iptrace you to your suburb if they're lucky. But that's not going to harm you.
So how to block/prevent your personal info being available to everyone?

Masking and preventing access to your information 

Right so you should know by now who to prevent your real name and email address from being shown right? .... Just don't enter them! Problem solved!

To mask your I.P. address the command is:

/mode <your_nick_here> +x

Stopping incoming (and outgoing ctcp requests)
This is where users can find you operating system information and even flood you and force your irc client to disconnect!

/mode <your_nick_here> +T

To stop users sending private messages:
Note: This command doesn't 'stop' the user from sending the messages, it just stops you from reciving them :).

/silence + <nickname>



Synopsis:
Right then, you can now block those curious requests and possible you may be more well equipped in the irc world :).
The NickServ queries can't be blocked, but they really don't matter unless you have a stalker!
If you've even read this far try the command: /msg NickServ access list.
You can even add and delete addresses from your access list! Eg:
/msg NickServ access add *lehcror@127.0.0.1 


*next week: I don't know, maybe a solid banning reference, I haven't seen one of those around for opera...

Tuesday, April 26, 2011

Intermediate guide to commands

Welcome to the opera irc!
If you haven't got your opera browser please go HERE and get it!

So this first section I'll write about some simple commands for the advanced user - the one who wants to go further than registering their nickname and registering channels.
All basic info you need for that is located Here (Opera's irc blog)

There are many irc clients out there and a lot of them are really good. I use opera simply because the web browser has proved more secure and stable than the other main web browsers. Well I don't think I'll have time to write any cool irc commands in today, will add to this soon though.

Saturday, April 23, 2011

The real walk

Yeah it took a while, had a lot to do..
The walk I ended up doing has restricted access, it's restricted due to some government towers ( no idea what they do) at the peak. And they deem it to be a security risk or a bloody terrorist threat if someone wanted to go up there and blow them up. But really, no one is going to be bothered carrying explosives or the tools to bring down a coupla towers. And anyway if they could be bothered they'll do it regardless of the crazy warning signs all over the place. 

But I say, F 'em. They want to block access in a national park?? I've read the act and the only legal way there can be restricted access is due to damaging the local ecosystem.

Right then, I'll start with: No Swedish backpackers' on this trip!
What a pity.
It was a nice walk started out with a lot of switch-backs which get damn tiresome really quick. I didn't even make it to the peak.

I didn't see one other person on this walk, must be due to the signs at the start. I should mention that yes there is a large fence at the start of the walk, and there is a (one) guard person at the location too. I checked him out  a week before asking about the track and just had a polite chat.
He started off denying that there was ever a walking track there!
Until I convinced him I knew my walking tracks around the area and told him where the track went to. He admitted the existence of the track but has been closed since a cyclone has been through.
I didn't push him too much as to why they blocked off this one section due to dangerous conditions (That's the official version) which is illegal. All nation parks are deemed dangerous that's why there is no clause to restriction access to a park for that very reason.

Anyway the walk was bloody rough! It hadn't been trod for ages... I was happy to have taken my machete because the vines and crap were covering the track like crazy.
 So I get a fair way up and there is a cool view of the waterfall through some trees, that's my destination I though. But alas I had been walking for almost two hours and it was really tough going. I turned back, defeated, I have to go back. Also saw signs of wild pigs too, do NOT want to encounter those while walking solo.

I'll get back to that walk another day...