It's gotta terminate somewhere on the Internet. That's the point where the blacklist would take effect. It might be data couldn't go out of the country the HAM terminator was, or couldn't get to the terminator to be transmitted via radio.
The idea was to sectionalize the Internet so that it still worked inside the effected area, but it was totally cut off from the external networks.
I wrote but never submitted an RFC for administering blocks....it was to be done at the backbone level, on the ordered authority of IANA or the IETF. (Explicitly *not* ICANN)
That way the traffic never gets out of their continent. If they want to cross oceans, they're going to be doing it over leased lines, and those lines can have blacklists applied.
If the Mozilla Foundation came up with an open-source replacement for shdoclc.dll (the Internet Explorer Rendering Engine) you could replace the IE application backend with the Firefox application backend.
If you ask me, that's something people should be working towards.
RUNAS [ [/noprofile |/profile] [/env] [/netonly] ] /user:<UserName> program
RUNAS [ [/noprofile |/profile] [/env] [/netonly] ] /smartcard [/user:<UserName>] program
/noprofile specifies that the user's profile should not be loaded.
This causes the application to load more quickly, but
can cause some applications to malfunction. /profile specifies that the user's profile should be loaded.
This is the default. /env to use current environment instead of user's. /netonly use if the credentials specified are for remote
access only. /savecred to use credentials previously saved by the user.
This option is not available on Windows XP Home Edition
and will be ignored. /smartcard use if the credentials are to be supplied from a
smartcard. /user <UserName> should be in form USER@DOMAIN or DOMAIN\USER
program command line for EXE. See below for examples
The guy wrote a book to describe where broadband signaling came from?
It's passing different signals on different frequencies over the same wire -- multiplexing of sorts.
DSL is a broadband service - voice and data on different frequencies on the same wire. Cable is the same idea -- different frequencies carrying the different data.
Why does he need to write a book to describe something that's been around since as long as electrical signals have been?
My 1998 Honda had a problem with the ignition that, if a certain combination of environmental factors, driving habits, and the phases of the moon and planets all combined correctly, the contacts would corrode under the extreme voltage and cut power to the engine while in operation. Their response: Take the car to a dealer to have the ignition switch replaced free of charge.
I.e.: This otherwise safe and well designed car has a small flaw that under certain conditions may manifest itself in a potentially annoying to potentially dangerous way, depending on what you are doing.
Now, let's pretend it is a computer.
Your well-engineered and hardened security Windows 2003 Server system has a flaw in a protocol parser that allows, with the right combination of messsages, someone to cause code to be executed on your system.
In other words: This otherwise safe and well designed server operating system has a flaw which, depending on several factors, may manifest itself in an annoying or dangerous way.
Any complex system is going to have problems with it. Millions of lines of code, or hundreds of thousands of moving or conductive parts, each can have something fail if there's a tiny problem with it.
Microsoft releases their fixes free of charge, just like a dealer service recall on an automobile.
What's the problem here? You can eliminate 95% of these vaunerabilities by simply *not running without a firewall* and *not running unneeded services* which is (GASP) something you'd do on Linux as well. Linux is just as vaunerable if it's sitting open and unprotected on a network with 500 services running as root. Would you do that? No. So why do you do it with a Windows box?
If it's because Windows is more of a "turn-key" solution, and the user doesn't think to secure their box, it's not Microsoft's fault, the blame rests surely in USER ERROR.
I think for an FX card, writeback speed pretty much doesn't matter in the slightest.
It's not like your video card really needs to be able to communicate with the processor at a superfast rate. AGP reedback rates are abysmal (as low as O(KB/sec) on some implementations, and that doesn't seem to effect much.
This same principle allows me to legally operate ROM images in emulators of videogame consoles that I no longer own, but still have dozens of cartridges for sitting in storage.
Go with, customer may perform any modifications to the source code and program for the purpose of developing applications for their customers, but may not resell the source code without an additional license fee/royalties.
I.e.
May modify code and build modified binaries, and redistribute binaries.
Many schools WILL provide you with a computer. Georgia Tech, for example, will rent a system to students for a fee per semester.
They ARE saying "If you want on our network, you will put this on your system." If you're not using their network, you don't have to play by their rules.
It's fairly simple. The network administrator is a jealous beast. He hates the system administrator and he hates the user. It is his territory, you play by his rules, or you don't play at all.
This functionality is already enabled by using Windows 2003 Domains with "Quarintine" routing enabled.
Basically -- you log in to the domain, the AD server authenticates your system for a number of factors: installed security patches, security settings, user-configurable data (AV signatures match such and such a date) and depending on whether or not you pass, you are either assigned a standard address or routed into a segmented network where you cannot address the machines that did pass.
GPOs in a Windows domain can be used to push patches, security updates, and specially configured Antivirus packages (sdat comes to mind: publish sdat as a GPO and it will instll itself; no prompts required.) They can also be used to install software (publish an MSI or ZAP of the software as a GPO) and automate network configuration.
Tools such as Altiris and Viewpoint automate this for more granular control, but are built on top of an AD framework.
Earth->Moon communications are O(1000ms) so that's not too bad for realtime requests to the servers on Earth.
Earth->Mars communications are O(20 minutes) so caching would probably become quite important.
I see UDP taking a greater role; where archives are sent via UDP with a sequence number embedded in them (CRC32 for integrity of course) The document is reconstructed in RAM; requests for missing segments can be sent as soon as they are detected and the missing packets can be appended onto the end of the data stream, so the overhead of a session buildup-teardown for the packets could be avoided.
Interplanetary Internet links would be disastriously slow...Internets would be mostly seperated by the planets themselves. Until something more efficient than lightspeed radio or laser links was thought up, interplanetary communications will not be instant.
I am thinking about entering politics once I get my degree finished...a politician with a CS degree, that's unheard of.
But, I'd be in touch with important issues.
I.e.: Don't install face recognition systems -- they don't work. Instead, spend $BILLION to pay the minimum wage rentacops at the airports to actually care whether or not a terrorist goes through.
I will fight for the consumer's rights against Corporate America, and ensure your privacy in the digital age.
SNES was a hightly optimized piece of equipment, and taxing games often had their own coprocessors on the cart themselves to do things. 3D effects processors courtesy of Rare, for their more intricate 3D games, sound processors, etc. Plus, when you're only dealing with (for the most part) 2d sprite/vector graphics, rotating those in hardware isn't that difficult to accomplish.
The slower, fading battle transitions on these discs were a very good way of making it seem like there was less loading -- because your screen was doing something that appeared integral to the action, you wouldn't notice the fact that it actually had to hit the CD ROM to load a lot of the data for it.
Slashdot Mirror
It's gotta terminate somewhere on the Internet. That's the point where the blacklist would take effect. It might be data couldn't go out of the country the HAM terminator was, or couldn't get to the terminator to be transmitted via radio.
The idea was to sectionalize the Internet so that it still worked inside the effected area, but it was totally cut off from the external networks.
a "Data Embargo" type deal.
I wrote but never submitted an RFC for administering blocks....it was to be done at the backbone level, on the ordered authority of IANA or the IETF. (Explicitly *not* ICANN)
That way the traffic never gets out of their continent. If they want to cross oceans, they're going to be doing it over leased lines, and those lines can have blacklists applied.
If the Mozilla Foundation came up with an open-source replacement for shdoclc.dll (the Internet Explorer Rendering Engine) you could replace the IE application backend with the Firefox application backend.
If you ask me, that's something people should be working towards.
Interesting but for people like me who have all forms of caching anything disabled for security reasons, that'd never go.
The guy wrote a book to describe where broadband signaling came from?
It's passing different signals on different frequencies over the same wire -- multiplexing of sorts.
DSL is a broadband service - voice and data on different frequencies on the same wire. Cable is the same idea -- different frequencies carrying the different data.
Why does he need to write a book to describe something that's been around since as long as electrical signals have been?
I'm not sure I agree with your way of looking at it, but I definately understand where you're coming from.
Windows until recently wasn't built to be attack proof. MS wised up about the "big city" deal with their 2003 server release, hardened to the bone.
BartPE.
'nuff said.
Think of it like a car.
My 1998 Honda had a problem with the ignition that, if a certain combination of environmental factors, driving habits, and the phases of the moon and planets all combined correctly, the contacts would corrode under the extreme voltage and cut power to the engine while in operation. Their response: Take the car to a dealer to have the ignition switch replaced free of charge.
I.e.: This otherwise safe and well designed car has a small flaw that under certain conditions may manifest itself in a potentially annoying to potentially dangerous way, depending on what you are doing.
Now, let's pretend it is a computer.
Your well-engineered and hardened security Windows 2003 Server system has a flaw in a protocol parser that allows, with the right combination of messsages, someone to cause code to be executed on your system.
In other words: This otherwise safe and well designed server operating system has a flaw which, depending on several factors, may manifest itself in an annoying or dangerous way.
Any complex system is going to have problems with it. Millions of lines of code, or hundreds of thousands of moving or conductive parts, each can have something fail if there's a tiny problem with it.
Microsoft releases their fixes free of charge, just like a dealer service recall on an automobile.
What's the problem here? You can eliminate 95% of these vaunerabilities by simply *not running without a firewall* and *not running unneeded services* which is (GASP) something you'd do on Linux as well. Linux is just as vaunerable if it's sitting open and unprotected on a network with 500 services running as root. Would you do that? No. So why do you do it with a Windows box?
If it's because Windows is more of a "turn-key" solution, and the user doesn't think to secure their box, it's not Microsoft's fault, the blame rests surely in USER ERROR.
..so they're detonating their integrated hardware controllers with the explosive devices?
Pulvarized electronics are probably just as dangerous to the environment as smoke from combustion of black powder.
I think for an FX card, writeback speed pretty much doesn't matter in the slightest.
It's not like your video card really needs to be able to communicate with the processor at a superfast rate. AGP reedback rates are abysmal (as low as O(KB/sec) on some implementations, and that doesn't seem to effect much.
Each PCIe channel is, IIRC, 150MB/sec independant bandwidth, and they come in 1, 4, and 16-channel slots.
a 16-channel PCIe slot is 2.4GB/sec of bandwidth...
I bet a high-resolution FX card would use most of that. But then again, they probably use PCIe-16 because PCIe-4 would be far too little.
Word.
This same principle allows me to legally operate ROM images in emulators of videogame consoles that I no longer own, but still have dozens of cartridges for sitting in storage.
It's on the front page of cnn.com today. That makes it a bit more credible.
u sp ect.ap/index.html
http://www.cnn.com/2004/US/South/06/26/bloody.s
(slashcode will probably put a space in there somewhere.)
It has to be a sinking ship because 5 TRU locations I was aware of previously are all boarded up abandon wrecks now.
I don't know of a single brick and mortar TRU location nearby any more.
Go with, customer may perform any modifications to the source code and program for the purpose of developing applications for their customers, but may not resell the source code without an additional license fee/royalties.
I.e.
May modify code and build modified binaries, and redistribute binaries.
May not distribute their source code in any form.
Many schools WILL provide you with a computer. Georgia Tech, for example, will rent a system to students for a fee per semester.
They ARE saying "If you want on our network, you will put this on your system." If you're not using their network, you don't have to play by their rules.
It's fairly simple. The network administrator is a jealous beast. He hates the system administrator and he hates the user. It is his territory, you play by his rules, or you don't play at all.
This functionality is already enabled by using Windows 2003 Domains with "Quarintine" routing enabled.
Basically -- you log in to the domain, the AD server authenticates your system for a number of factors: installed security patches, security settings, user-configurable data (AV signatures match such and such a date) and depending on whether or not you pass, you are either assigned a standard address or routed into a segmented network where you cannot address the machines that did pass.
GPOs in a Windows domain can be used to push patches, security updates, and specially configured Antivirus packages (sdat comes to mind: publish sdat as a GPO and it will instll itself; no prompts required.) They can also be used to install software (publish an MSI or ZAP of the software as a GPO) and automate network configuration.
Tools such as Altiris and Viewpoint automate this for more granular control, but are built on top of an AD framework.
Basically, nothing new here.
Earth->Moon communications are O(1000ms) so that's not too bad for realtime requests to the servers on Earth.
Earth->Mars communications are O(20 minutes) so caching would probably become quite important.
I see UDP taking a greater role; where archives are sent via UDP with a sequence number embedded in them (CRC32 for integrity of course) The document is reconstructed in RAM; requests for missing segments can be sent as soon as they are detected and the missing packets can be appended onto the end of the data stream, so the overhead of a session buildup-teardown for the packets could be avoided.
Interplanetary Internet links would be disastriously slow...Internets would be mostly seperated by the planets themselves. Until something more efficient than lightspeed radio or laser links was thought up, interplanetary communications will not be instant.
That's a DAMN good idea.
Put $1b of something on the moon, document it's location.
Dare someone to go retrive it. Finder's, keeper's.
You sir are correct.
They can't just demans you provide your name if you're making an anonymous speech in a public forum or something.
Only if you might be somebody they're looking for already.
I am thinking about entering politics once I get my degree finished...a politician with a CS degree, that's unheard of.
But, I'd be in touch with important issues.
I.e.: Don't install face recognition systems -- they don't work. Instead, spend $BILLION to pay the minimum wage rentacops at the airports to actually care whether or not a terrorist goes through.
I will fight for the consumer's rights against Corporate America, and ensure your privacy in the digital age.
So, who'll vote for me?
SNES was a hightly optimized piece of equipment, and taxing games often had their own coprocessors on the cart themselves to do things. 3D effects processors courtesy of Rare, for their more intricate 3D games, sound processors, etc. Plus, when you're only dealing with (for the most part) 2d sprite/vector graphics, rotating those in hardware isn't that difficult to accomplish.
The slower, fading battle transitions on these discs were a very good way of making it seem like there was less loading -- because your screen was doing something that appeared integral to the action, you wouldn't notice the fact that it actually had to hit the CD ROM to load a lot of the data for it.
Trickery, on their part.
Making a false report to police is a crime, btw.