free net tools

[donkey42]

keep yourself protected by scanning every week after updating the definitions

recommended firewalls - ZoneAlarm & Comodo

malware scanners - Malwarebytes & SuperAntiSpyware

Antivirus - Avast & Avira

with the firewalls & Antivirus choose only one but you need both malware scanners

all software posted here is freeware but i do recommend you purchase SuperAntiSpyware Pro
personally i use Avast, Malwarebytes, SuperAntiSpyware Pro & ZoneAlarm, but you can choose either ZoneAlarm of Comodo and either Avast or Avira

other free & useful stuff
CCleaner - for clearing crap
FileAssasin - for deleting pesky files the above malware finds but cannot remove
RegAssasin - as above but removes registry entries the above malware cannot remove

other free stuff you should install

WebBrowser

Firefox - browser (obviously turn on the Phishing filter - Tools-> Options -> Security tab)

with these Addins WOT (Web Of Trust) - it gives you a warning or a popup if you are browsing a bad website
Customize Google - makes google very helpful
Noscript -protect yourself from clickjacking
Xmarks - backup your bookmarks and store them online

 

[cube_]

Hey this is way cool! I use CCleaner and AVG AntiVirus. Both are excellent.
Could you recommend something similar to PeerGuardian thats compatible for Vista x64? I've had good experiences with PG but it doesn't have Vista x64 compatibilities!

 

[donkey42]

Could you recommend something similar to PeerGuardian thats compatible for Vista x64? I've had good experiences with PG but it doesn't have Vista x64 compatibilities!

peerguardian appears to be some kind IP blocker that only works on IPv4 & not IPv6 so, it will be useless in about 3 years (when IPv6 takes over the world

other than that, peerguardian doesn't seem to fit into any category, however it seem to exist as a compliment to your firewall,

in conclusion
PeerGuardian doesn't seem to be of much or any use (except to IPv4) however, so long as you use it as a compliment to your firewall and only use it until IPv6 takes control (by then there will probably be an IPv6 version out), but i don't see it as doing any harm on IPv4

Edit: sorry Scorps, i didn't intentionally p1ss on your bonfire, but i would prefer it if someone was honest, like they were with me :beer:

 

[cube_]

personally i've never liked AVG as in the past Avast has beaten AVG to the ground with a big stick, i can't actually remember much about AVG, but i do remember that Mega didn't like itpeerguardian appears to be some kind IP blocker that only works on IPv4 & not IPv6 so, it will be useless in about 3 years (when IPv6 takes over the world

I've seen the IPv6 and 4 services and never understood what they were. Are they protocols?

other than that, peerguardian doesn't seem to fit into any category, however it seem to exist as a compliment to your firewall

Interesting you say that. I've been using PG without a firewall! I was always annoyed with 3rd party firewall apps such as ZoneAlarm which always required your permission for every action on the web! Which is why i never installed one and opted for Windows Firewall (i know... very unsafe decision).

Edit: sorry Scorps, i didn't intentionally p1ss on your bonfire, but i would prefer it if someone was honest, like they were with me :beer:

Its cool, i'd prefer you be honest than not ;)

 

[donkey42]

I've seen the IPv6 and 4 services and never understood what they were. Are they protocols?

well, think of it this way IP Version 4 is what almost all current internet services use (kinda like Ice on an Ice skating rink) & IP Version 6 is kinda dormant but waiting along side IPv4 for the eventual takeover then IP4 will probably be be improved & renamed something like IPv8, & it will in a possibility replace IPv6 when IPv6 is old & gray & ready to retire then in all probability

when IPv8 is ready to retire it's replacement will probably be waiting in the wings ready to take over

BTW: a lot of this is my opinion on what the future holds & i have reached this opinion by reading stuff like the TCP/IP guide & other docs

Interesting you say that. I've been using PG without a firewall! I was always annoyed with 3rd party firewall apps such as ZoneAlarm which always required your permission for every action on the web! Which is why i never installed one and opted for Windows Firewall (i know... very unsafe decision).

well with ZoneAlarm (old version) you could specify which progs had ingoing or outgoing permission & obviously it would remember which progs had permission

if theres anything you don't understand & if i can help i will, even if you have a query about the relation between the theory and practical application of networking :doh:[ot]still struggling with that, but i will probably help me to understand to if i explain it to someone else[/ot]

its cool, i'd prefer you be honest than not

me too :beer:[ot]what is it like being dragged kicking & screaming into the future ?[/ot]

 

[cube_]

well, think of it this way IP Version 4 is what almost all current internet services use (kinda like Ice on an Ice skating rink) & IP Version 6 is kinda dormant but waiting along side IPv4 for the eventual takeover then IP4 will probably be be improved & renamed something like IPv8, & it will in a possibility replace IPv6 when IPv6 is old & gray & ready to retire then in all probability

when IPv8 is ready to retire it's replacement will probably be waiting in the wings ready to take over

Thanks man, that clears up a bit

if theres anything you don't understand & if i can help i will, even if you have a query about the relation between the theory and practical application of networking :doh:[ot]still struggling with that, but i will probably help me to understand to if i explain it to someone else[/ot]

Thanks, i'll let you know! Maybe we will help each other out. Right now i'm reading this and this about how the internet works. I've always wanted to know.

[ot]what is it like being dragged kicking & screaming into the future ?[/ot]

LOL

 

[donkey42]

Thanks man, that clears up a bit

:good:

Thanks, i'll let you know! Maybe we will help each other out. Right now i'm reading this and this about how the internet works. I've always wanted to know.

well it does help me as i try explaining things other people i actually explain things better to myself

i personally try to think "if i'd have done it, how would i have done it ?

LOL

you think that was funny, you've no idea

Edit: IPv4 @ wiki & IPv6 @ wiki

 

[cube_]

I just read a whole article about how servers work in the most simplest form. I understand so much now! For some reason, it feels good to know that servers use port 80 9by default) to send a web server request to a client!

I guess that's what it feels like to be a nerd :x:

And was there something more to off topic comment you made at the end that i didn't understand!?

 

[donkey42]

I just read a whole article about how servers work in the most simplest form. I understand so much now! For some reason, it feels good to know that servers use port 80 9by default) to send a web server request to a client!

key:

* <scheme>: The URL scheme, as described above.

* <user> and <password>: Authentication information for schemes requiring a login, in the form of a user name and password.

* <host>: An Internet host, usually specified either as a fully qualified DNS domain name, or an IP address in dotted-decimal notation.

* <port>: A TCP or UDP port number to use when invoking the protocol appropriate to the scheme.

* <url-path>: A resource location path. This is usually a full directory path expressing the sequence of directories to be traversed from the root directory to the place where the resource is located, and then the resource's name. For example, if on a device there is a directory called “project1” and within it a subdirectory called “memos” containing a text file called “June11th-minutes.txt”, the URL path “project1/memos/June11th-minutes.txt” would refer to that resource.

Note that the slash before the <url-path> is required, and while it is technically not considered part of the path, it serves the purpose of “acting” like the slash denoting the root directory in many file systems. Also, the <url-path> may end in a slash, which means that the path refers specifically to a directory. However, this is often not required, as the server will treat the URL as a directory reference by context when needed. A path may also refer to a virtual file, program or resource other than a “normal” file.

* <params>: Scheme-specific parameters included to control how the scheme is used to access the resource. Each parameter is generally of the form “<parameter>=<value>”, with each parameter specification separated from the next using a semi-colon.

* <query>: An optional query or other information to be passed to the server when the resource is accessed.

* <fragment>: Identifies a particular place within a resource that the user of the URL is interested in.

Source
so, you know how it works & can now implement it, FTP works very similar, see here

I guess that's what it feels like to be a nerd :x:

welcome to my world, there's a loada crap going on up here

And was there something more to off topic comment you made at the end that i didn't understand!?

what ?

 

[cube_]

Wow, something i totally didn't know about. I'll definitely look into this when i get the chance!

And as for the last thing, lol when you said "what is it like being dragged kicking & screaming into the future ?", i wrote "LOL". Then you wrote "you think that was funny, you've no idea".
So, i didn't get what you meant by it :confused:
Or was it intended as a figure of speech?

 

[donkey42]

And as for the last thing, lol when you said "what is it like being dragged kicking & screaming into the future ?", i wrote "LOL". Then you wrote "you think that was funny, you've no idea".
So, i didn't get what you meant by it :confused:
Or was it intended as a figure of speech?

no, i was referring to how funny i can be if i want