I remember reading something by some ex-microsoftie. One of the comments he said stuck in my mind. he said that it's not that microsoft doesn't like standards, it's more that if you follow a standard, then you're admitting that you can't do better than the standard. Why use opengl when you could change a whole heap of things to make it "better" and have directx instead?
Which seems to me to miss the point of having standards. The value in standards isn't in whatever the standard specifies, it's the fact that everyone else is implementing the same standard.
You know, this gives a whole new look on money you get with those monopoly games. Turns out that if you are a monopoly you can print your own currency and have people use it....
the i386 has no hardware support for an "execute" bit. It just has a read bit and a write bit. If you have read access to a page then you can execute that code. The "NX" bit is the implementation of the "execute" bit, except when it's/set/ it prevents execution as opposed to the expected reverse, which is why it's called "NX" not "X":)
I work for a network research group ("WAND") at Waikato University in New Zealand. We have a similar visualisation which you can see various stages of evolution here, there are also some animations.
The universities internal network IP range is mapped onto the left hand face of the cube, the rest of the world is mapped onto the right face. They are mapped so similar addresses are clustered together and addresses further apart are uh, further apart. A box represents one packet, the volume of the particle is proportional to the size of the packet, and the colour is based on port number.
Also we "light" each end of the connection for a bit after the packet has been sent. So machines appear to be glowing in the colour of the traffic they are sending.
We use it to show off "networks" to people who think we just sit at computers and type into stuff, however it has been very useful to detect attacks and broken machines since they provde distinctive patterns. Portscans are a series of "sparkly" packets. Network scans are a row of marching lines. Virii infected machines appear as a cone centered on the infected machine.
I live in New Zealand. America got quite irritated with us not supporting them fully during the war with Iraq. They made it quite clear. Australia did, and got a Trade Agreement that New Zealand missed out on. Unfortunately Australia's trade agreement had these DMCA issues (amongst others), so really, New Zealand came out of this much better off.
If America's going to treat it's friends like this, I think I'd prefer not to be in America's best buddies list.
Except that they are trying to do this with.NET..NET requires a completely different programming language (C#), and completely different programming API (the class libraries).
If they can convince everyone to port to.NET then they can switch out the hardware underneath the OS without recompiling their applications. And if their compeditors weren't ready for the switch, well, bad luck for them.
One idea I've had is to hold anything that has an attachment that starts with the letters "MZ" (which are the "magic" for.EXE files) for 24 hours, then rerun the virus scanner over them. 24 hours is more than enough time for virus checkers to be updated and the virus hopefully will be dropped then. People who are legitimately (?!) sending executables around in email, just get a 24h delay.
Microsoft hires researchers to make sure that noone else has them. If they churn out something useful every now and again, then Wee! Bonus! But imagine if MS's R&D department went and worked for someone else, or, got bored and worked on Open Source projects!
I wanted a place for highly technical information about Linux, particularly programming documentation. I'd read the HOWTO's and had used google, but was irritated that google tended to find me the question, but rarely the answer.
My solution was to set up the WLUG Wiki. If you can find a group of like minded people to "seed" the community with your problems (and solutions) then slowly, over time other people join in. We've been running the wlug wiki for 18 months now, and it's now the top hit on google for all kinds of things, and is linked from all kinds of official pages as documentation.
Theres been several people that have said that they'd love to have a general "system administration" wiki for Windows, but there are none (and I'm not going to set one up -- I don't know enough about administering windows!)
So, set one up, it's not difficult. Try and write down what problems you've solved each day and what their solution were into the wiki, and try and get a couple of other people to join in. Pretty soon you'll have created you're own resource
When we can get proper limits per/64 and/48 etc. ircu gives kiddies a stupid number of IP addresses, so we don't want them to just evade all the time, or to load up 2^64 clones in under a second...
Easy, because I have one IPv4 address, and I want to be able to ssh directly into machines behind the NAT box without having to ssh to the NAT box first.
Most do actually. They generally configure themselves via autoconf.
Sorry, I wasn't clear, I meant that distro's should enable 6to4 (or perhaps teredo[1]) on a machine, if it has a realworld IPv4 address, but no globally scoped v6 addresses.
[1]: Are there Teredo clients for Linux/BSD? Or just windows?
I use IPv6 for my home network, so I can ssh in from around the world directly into machines rather than having to SSH into the NAT gateway, then ssh into the machine behind the NAT that I want.
In general IPv6 was pretty painless to setup, my biggest problems were caused by the fact I was using 6to4 which means my IPv6 addresses are based on my IPv4 address, which isn't static, so it took a bit of scripting to get everything to happen correctly when my v4 address changed (changing routes etc).
Almost all application support v6 one way or another, however notably missing is Apache 1, you need extra patches to get IPv6 support, and most apache log analysers get confused with IP addresses with:'s in them.
I'm surprised that Distro's don't enable v6 by default. (If you have a non-RFC1918 address, use 6to4, if you only have a RFC1918 addresses, use teredo).
I've IPv6 enabled our local LUG server (http://www.wlug.org.nz/), you get a dancing penguin for the logo if you use v6.
Traditionally protocols on the Internet double in bandwidth consumed every 2 weeks, and traditionally they aren't protocols used "for money", but are because they let people do something. eg:
* Email * HTTP * P2P
have all shown this growth, none of them were expected, and only HTTP was considered "useful" by management at the time.
UPnP requires upgrading every NAT device on the Internet. Toredo lets a computer behind a NAT device have full IPv6 connectivity (Including incoming connections) through a NAT *and* is installed on all Windows XP machines with SP1 installed.
6to4 is the technology to replace NAT. For one IPv4 address you get 65536 times the current size of the internet addresses for use in your local company.
Toredo lets you do IPv6 even if there is a NAT in the way and is supported by Windows XP.
IPv6 isn't hard, just people need to start doing it.
if you have a static IPv4 address today, you already have a static IPv6/48 thanks to 6to4.
IPv6 is designed to work in a mixed v4 and v6 network. IPv6 can even work through IPv4 NAT (with toredo), allowing outside connections to initiate IPv6 connections with machines behind NAT.
What we need is things like Linux Distributions to enable 6to4 by default on an interface that has a non RFC1918 address, and toredo on interfaces that do.
Windows supports 6to4/toredo etc, however it's not configured by default, you have to turn it on.
The "permanently" is until the next power cycle. There are 5 attempts before you have to completely power cycle the drive, therefore slowing down brute force attacks on the password.
You can reset the password but you lose all the data currently on the drive, look up SMART, I believe smartmontools under linux can tinker with these settings.
Slashdot Mirror
a lot of sites keep insisting that .rpm files are "real player media" files, and while I've never seen such a .rpm, it at least seems feasible.
I remember reading something by some ex-microsoftie. One of the comments he said stuck in my mind. he said that it's not that microsoft doesn't like standards, it's more that if you follow a standard, then you're admitting that you can't do better than the standard. Why use opengl when you could change a whole heap of things to make it "better" and have directx instead?
Which seems to me to miss the point of having standards. The value in standards isn't in whatever the standard specifies, it's the fact that everyone else is implementing the same standard.
You know, this gives a whole new look on money you get with those monopoly games. Turns out that if you are a monopoly you can print your own currency and have people use it....
the i386 has no hardware support for an "execute" bit. It just has a read bit and a write bit. If you have read access to a page then you can execute that code. The "NX" bit is the implementation of the "execute" bit, except when it's /set/ it prevents execution as opposed to the expected reverse, which is why it's called "NX" not "X" :)
I work for a network research group ("WAND") at Waikato University in New Zealand. We have a similar visualisation which you can see various stages of evolution here, there are also some animations.
The universities internal network IP range is mapped onto the left hand face of the cube, the rest of the world is mapped onto the right face. They are mapped so similar addresses are clustered together and addresses further apart are uh, further apart. A box represents one packet, the volume of the particle is proportional to the size of the packet, and the colour is based on port number.
Also we "light" each end of the connection for a bit after the packet has been sent. So machines appear to be glowing in the colour of the traffic they are sending.
We use it to show off "networks" to people who think we just sit at computers and type into stuff, however it has been very useful to detect attacks and broken machines since they provde distinctive patterns. Portscans are a series of "sparkly" packets. Network scans are a row of marching lines. Virii infected machines appear as a cone centered on the infected machine.
I live in New Zealand. America got quite irritated with us not supporting them fully during the war with Iraq. They made it quite clear. Australia did, and got a Trade Agreement that New Zealand missed out on. Unfortunately Australia's trade agreement had these DMCA issues (amongst others), so really, New Zealand came out of this much better off.
If America's going to treat it's friends like this, I think I'd prefer not to be in America's best buddies list.
Except that they are trying to do this with .NET. .NET requires a completely different programming language (C#), and completely different programming API (the class libraries).
.NET then they can switch out the hardware underneath the OS without recompiling their applications. And if their compeditors weren't ready for the switch, well, bad luck for them.
If they can convince everyone to port to
One idea I've had is to hold anything that has an attachment that starts with the letters "MZ" (which are the "magic" for .EXE files) for 24 hours, then rerun the virus scanner over them. 24 hours is more than enough time for virus checkers to be updated and the virus hopefully will be dropped then. People who are legitimately (?!) sending executables around in email, just get a 24h delay.
Microsoft hires researchers to make sure that noone else has them. If they churn out something useful every now and again, then Wee! Bonus! But imagine if MS's R&D department went and worked for someone else, or, got bored and worked on Open Source projects!
There are two types of program, one thats so simple there are obviously no bugs, and one that's so complex, there are no obvious bugs.
I wanted a place for highly technical information about Linux, particularly programming documentation. I'd read the HOWTO's and had used google, but was irritated that google tended to find me the question, but rarely the answer.
My solution was to set up the WLUG Wiki. If you can find a group of like minded people to "seed" the community with your problems (and solutions) then slowly, over time other people join in. We've been running the wlug wiki for 18 months now, and it's now the top hit on google for all kinds of things, and is linked from all kinds of official pages as documentation.
Theres been several people that have said that they'd love to have a general "system administration" wiki for Windows, but there are none (and I'm not going to set one up -- I don't know enough about administering windows!)
So, set one up, it's not difficult. Try and write down what problems you've solved each day and what their solution were into the wiki, and try and get a couple of other people to join in. Pretty soon you'll have created you're own resource
Yep, thats the one!
Bwahahahaha.
/64 and /48 etc. ircu gives kiddies a stupid number of IP addresses, so we don't want them to just evade all the time, or to load up 2^64 clones in under a second...
When we can get proper limits per
Hmm, perhaps not the clearest.
You can get IPv6 addresses by signing up with a tunnel broker near you.
You can *also* get IPv6 addresses by using 6to4. For an IPv4 address, you get 2002:::/48 as a network to assign IPv6 addresses out of.
You can get a tunnel from a tunnel broker.
Given a IPv4 address you can use all the addresses in 2002:::/48 (yep, thats 2**(128-48) addresses per IPv4 address...), This is called "6to4"
Easy, because I have one IPv4 address, and I want to be able to ssh directly into machines behind the NAT box without having to ssh to the NAT box first.
- IPv6
- IPv6 Setup
- 6to4
- IPv6 Lessons Learnt
The site is a wiki, feel free to add questions, correct mistakes, add your experiences, or other sites you found interesting/helpful.Most do actually. They generally configure themselves via autoconf.
Sorry, I wasn't clear, I meant that distro's should enable 6to4 (or perhaps teredo[1]) on a machine, if it has a realworld IPv4 address, but no globally scoped v6 addresses.
[1]: Are there Teredo clients for Linux/BSD? Or just windows?
I use IPv6 for my home network, so I can ssh in from around the world directly into machines rather than having to SSH into the NAT gateway, then ssh into the machine behind the NAT that I want.
:'s in them.
In general IPv6 was pretty painless to setup, my biggest problems were caused by the fact I was using 6to4 which means my IPv6 addresses are based on my IPv4 address, which isn't static, so it took a bit of scripting to get everything to happen correctly when my v4 address changed (changing routes etc).
Almost all application support v6 one way or another, however notably missing is Apache 1, you need extra patches to get IPv6 support, and most apache log analysers get confused with IP addresses with
I'm surprised that Distro's don't enable v6 by default. (If you have a non-RFC1918 address, use 6to4, if you only have a RFC1918 addresses, use teredo).
I've IPv6 enabled our local LUG server (http://www.wlug.org.nz/), you get a dancing penguin for the logo if you use v6.
Traditionally protocols on the Internet double in bandwidth consumed every 2 weeks, and traditionally they aren't protocols used "for money", but are because they let people do something. eg:
* Email
* HTTP
* P2P
have all shown this growth, none of them were expected, and only HTTP was considered "useful" by management at the time.
UPnP requires upgrading every NAT device on the Internet. Toredo lets a computer behind a NAT device have full IPv6 connectivity (Including incoming connections) through a NAT *and* is installed on all Windows XP machines with SP1 installed.
All we need is a reason to use it.
6to4 is the technology to replace NAT. For one IPv4 address you get 65536 times the current size of the internet addresses for use in your local company.
Toredo lets you do IPv6 even if there is a NAT in the way and is supported by Windows XP.
IPv6 isn't hard, just people need to start doing it.
if you have a static IPv4 address today, you already have a static IPv6 /48 thanks to 6to4.
IPv6 is designed to work in a mixed v4 and v6 network. IPv6 can even work through IPv4 NAT (with toredo), allowing outside connections to initiate IPv6 connections with machines behind NAT.
What we need is things like Linux Distributions to enable 6to4 by default on an interface that has a non RFC1918 address, and toredo on interfaces that do.
Windows supports 6to4/toredo etc, however it's not configured by default, you have to turn it on.
Practical internet for consumers in New Zealand is "JetStart" which is 128kbit ADSL. So yeah, it is much faster. :)
The "permanently" is until the next power cycle. There are 5 attempts before you have to completely power cycle the drive, therefore slowing down brute force attacks on the password.
You can reset the password but you lose all the data currently on the drive, look up SMART, I believe smartmontools under linux can tinker with these settings.