Lets put it another way. Even if I left my house door wide open, opened all the windows etc. It still does not give you the right to come in and f*ck with my house.
It doesn't give anyone the right to come tamper with your house.
However, if they walk in a door you opened, they haven't "broken in".
They're just trespassing (possibly); hopefully you don't have a doormat that says "Welcome", "Come In", or something such as that.
If you do, then w/ the door held open: you've invited them in.
Yeah, I have, it's built into the C programming language.
union { };
For actual programmers... well, I think it's better to stick with professional societies, such as the Programmer's Guild, and the NAP (National Association of Programmers).
If a programmer's union were to form, we'd soon see a union of helpdesk workers, DBAs, Server admins, Storage admins, Network admins, Webmasters, would all have their own unions.
Mr. Server admin.. don't even think of
plugging/unplugging a network cable into your server to attempt to troubleshoot a possible networking issue, union arrangements provide that only a member of the network technicians union can touch networking equipment, which that cable is.
And god help you if you write a SQL statement, the DBAs will have your ass...
You get fired if you write a line of HTML or CSS for the webapp, only members of the Webmasters' union can do that (not programmers).
I think the logic is basically since you aren't working at the office, except when you're called, that it somehow makes up for all that time you are on-call offhours.
I think it's bumpkis. The average webmaster is working during the day.
Being at office doing day-to-day tasks when you want to be home having fun is work.
The security issue here is unencrypted WiFi at a public place that is easily intercepted by other people at a public place, or by the owner of the WiFi
Your VPS is 1000x more trustworthy than unencrypted WIFI connection.
Forward all traffic down a VPN tunnel.
There are actually VPN services ala HotSpotVPN, anonymizer, Witopia, that may also help here.
Or Tor... but I do not recommend tor, doing online banking through tor is a sure way to get pwned.
but if I were a captain of a ship being raided, I doubt I would prefer gumming up their motors to blowing them out of the water. Not only that but if you just mess with the pirates equipment they will just go on to do the same again later once they repair it.
Many countries in that region forbid ships that contain the necessary guns (to blow a vessel out of the water) from entering, and forbid ships whose crew are armed with personal guns from entering their waters, or their ports. Only pirates can carry deadly weapons (legally).
Also, Somalia, and several other countries in that region, have an international arms embargo in place. It's a violation of international law to bring weapons through there. Thus, only the criminals have guns.
Most ships don't want to even carry real guns, anyways, let alone armament capable of blowing other vessels out of the water.
Gunpowder can accidentally be ignited: an accident on board could blow _themselves_ out of the water, let-alone the possibility of their own weapons being used to hijack the vessel.
If pirates board, they can takeover control of those weapons and use them to kill people.
They also have more weapons and ammo which may otherwise be a little hard for pirates to get.
Having deadly weapons on-board poses risks.
So, these are just some reasons to prefer stun devices.
Also the obvious matter, that stunning still stops the pirates, maybe allows them to be arrested and dealt with by authorities, with minimal loss of life (including minimal damage / minimal loss of life to the possibly captured vessel and innocent bystanders the pirates were attempting to use to capture the bigger vessel).
That's just the difference between an IT Development/Architect role and an IT Support role.
Software or Hardware design/building is Development.
IT Support roles are things like QA, testing, system administration, internet helldesk.
To the naive person, it's just IT.
Some engineers don't like being called "IT Guys", because they want to make sure they stay as far away as the helldesk as possible. Many developers had bad experiences there in their early years, before they came adept in their field of software development, and now want to distance themselves as far as possible.
Seeing "looking for IT guy" in a job solicitation can be scary.. it's almost like seeing "College Graduate" as the only required qualification...
it makes the job look less important, which may reduce it's attractiveness to higher-end applicants ---- this is a marketing error (unless the intent is to hire as cheap applicants as possible, and coax them into other IT roles like sysadmin on the side).
There are people who will see "IT Guy" or see your computer-based role, and assume you can help them with all their petty problems.
So carving out a name like "Engineer" offers some protection (although that name Engineer is really already taken by a completely different discipline that has nothing to do with software development).
Anyways... whether developers WANT to be called IT guys or not, is a separate question from Are they IT guys? in fact.
You know, writing software requires troubleshooting, and fixing problems (in software you made though), much like IT Support roles.
Perhaps developers and IT sysadmins are only really that different at a superficial (and social) level, and in regards to the specific subject matter.
Troubleshooting your own code that you have full control over might be a lot easier than troubleshooting complex proprietary systems you don't have control over, and can't necessarily even see the source code to.
Why isn't it Open-Source?
TrustLeap's technology could be mis-used, diluting or even compromizing it: open-source is now an on-ramp to very profitable closed data services. And if you are not rich enough to prevent others from stealing from you in the first place, then the 'rule of law' just helps the guilty to ruin you.
And after reading items on this timeline.
I begin to question the author's sanity...
I like environments without garbage collection, it gives more control, and doesn't degrade system performance while everything has to slow down continuously for GC.
But as for working in an environment without protected memory... that's just crazy talk.
Information technology (IT), as defined by the Information Technology Association of America (ITAA), is "the study, design, development, implementation, support or management of computer-based information systems, particularly software applications and computer hardware."
IT deals with the use of electronic computers and computer software to convert, store, protect, process, transmit, and securely retrieve information.
You ARE in IT.
However, it's the equivalent of calling a Brain surgeon a Doctor
Or referring to a Nuclear physicist as a scientist.
It is kind of vague. Sometimes being more specific is good, as it points out people's specialty more.
No, but if you rewrote the Windows kernel and service APIs (kernel.exe, user32.dll, GDI, mstdc, svchost, kernel32.dll, advapi32, win32k.sys, comctl32, comdlg, shell32, shlwapi, Winsock, NetDDE, RPC, NetBIOS, Internet Explorer, etc) in Python, it might be faster, have fewer buffer overflows.
Although i'm sure MS would still figure out some way of introducing security problems of some sort.
Trade buffer overflows for kernel-mode Python code injection vulnerabilities.
And since python is such an easier language to understand, python code injection in kernel mode is oh so much easier to exploit, even by novices...
No, i'm just kidding.. but it's a good idea to be careful about what you're actually getting fed, when your programming language is trying to feed you.. computers don't tend to be that intelligent, and they might be accidentally feeding you from the wrong jar:)
It's the equivalent to writing a program against the Windows API, not testing it, and calling the API buggy when you find that it is failing in the wild.
The API may not match the spec perfectly, but it's your software that's buggy.
Intel can revise the proc, or revise the spec to be in agreement.
MS is trying to use an APIC interrupt for timing that isn't normally used for that purpose.
It's the equivalent of attaching an alarm clock to your electric car's engine, and complaining when the idling speed deviates due to a power saving feature.
Nehalem processors were out long before 2008 R2 or the newest Hyper-V release.
intel Nehalem is a processor with features very attractive to users of virtualization, it's one of the most common procs to be used in new server deployments.
There is absolutely no excuse for MS not extensively testing and qualifying including stress-testing their Hypervisor on Nehalem CPUs before releasing the code.
It would be like you or me writing a piece of desktop software today (in 2009), designed for use with Windows, and extensively testing it on Windows '98 and XP, but not discovering a frequent crash on Vista, that almost always occurs as soon as starting the program.
It's not a processor bug, it's a Windows bug.
The advisory should say "download this Windows update" that properly fixes it, not "stop using this processor, because it causes our bug to show up"
Then they should register their domains through a russian domain registrar that is outside the US jurisdiction, or through their.RU ccTLD.
Because Network Solutions is a US-based competitive registrar, which has to obey any lawful order made by a US court, under penalty of contempt, and has to obey DMCA notices from companies like Microsoft or risk liability.
Registrars are not immune, and the only reason they haven't frozen DNS for the domain is they weren't ordered to, and Microsoft may not have requested it.
That's because a JVM is not something that you just dump something on. It's not a big truck. It's a series of tubes. And if you don't understand, those tubes can be filled, and if they are filled, when you put your program in, it gets in line, and it's going to be delayed by anyone that puts into the tube enormous emounts of information, enormous amounts of information.
And then, if it gets too congested, your JVM explodes, taking the entire internet with it!
As if the people who manufacture biological weapon delivery system contrary to US law will care about a EULA clause in the JVM they run their software on.
Slashdot Mirror
Lets put it another way. Even if I left my house door wide open, opened all the windows etc. It still does not give you the right to come in and f*ck with my house.
It doesn't give anyone the right to come tamper with your house.
However, if they walk in a door you opened, they haven't "broken in".
They're just trespassing (possibly); hopefully you don't have a doormat that says "Welcome", "Come In", or something such as that.
If you do, then w/ the door held open: you've invited them in.
Yeah, I have, it's built into the C programming language.
union { };
For actual programmers... well, I think it's better to stick with professional societies, such as the Programmer's Guild, and the NAP (National Association of Programmers).
If a programmer's union were to form, we'd soon see a union of helpdesk workers, DBAs, Server admins, Storage admins, Network admins, Webmasters, would all have their own unions.
Mr. Server admin.. don't even think of plugging/unplugging a network cable into your server to attempt to troubleshoot a possible networking issue, union arrangements provide that only a member of the network technicians union can touch networking equipment, which that cable is.
And god help you if you write a SQL statement, the DBAs will have your ass... You get fired if you write a line of HTML or CSS for the webapp, only members of the Webmasters' union can do that (not programmers).
I think the logic is basically since you aren't working at the office, except when you're called, that it somehow makes up for all that time you are on-call offhours.
I think it's bumpkis. The average webmaster is working during the day.
Being at office doing day-to-day tasks when you want to be home having fun is work.
Merchants follow the official laws of the established authorities, to be properly classified under the maritime law as merchants.
Pirates follow their own laws, and the unofficial laws of the (corrupt) established authorities.
The security issue here is unencrypted WiFi at a public place that is easily intercepted by other people at a public place, or by the owner of the WiFi
Your VPS is 1000x more trustworthy than unencrypted WIFI connection.
Forward all traffic down a VPN tunnel.
There are actually VPN services ala HotSpotVPN, anonymizer, Witopia, that may also help here.
Or Tor... but I do not recommend tor, doing online banking through tor is a sure way to get pwned.
At 1.2 miles, or even 1000 feet.. you don't know that they're pirates. You could be shooting innocent people
You know... one crowbar, or one person with the right tools can defeat a key lock..
A weapon is only worth as much as you spend on training the crew to use it effectively.
Military needs to learn from them, and disguise some military ships as cargo vessels :)
but if I were a captain of a ship being raided, I doubt I would prefer gumming up their motors to blowing them out of the water. Not only that but if you just mess with the pirates equipment they will just go on to do the same again later once they repair it.
Many countries in that region forbid ships that contain the necessary guns (to blow a vessel out of the water) from entering, and forbid ships whose crew are armed with personal guns from entering their waters, or their ports. Only pirates can carry deadly weapons (legally).
Also, Somalia, and several other countries in that region, have an international arms embargo in place. It's a violation of international law to bring weapons through there. Thus, only the criminals have guns.
Most ships don't want to even carry real guns, anyways, let alone armament capable of blowing other vessels out of the water. Gunpowder can accidentally be ignited: an accident on board could blow _themselves_ out of the water, let-alone the possibility of their own weapons being used to hijack the vessel.
If pirates board, they can takeover control of those weapons and use them to kill people. They also have more weapons and ammo which may otherwise be a little hard for pirates to get.
Having deadly weapons on-board poses risks.
So, these are just some reasons to prefer stun devices.
Also the obvious matter, that stunning still stops the pirates, maybe allows them to be arrested and dealt with by authorities, with minimal loss of life (including minimal damage / minimal loss of life to the possibly captured vessel and innocent bystanders the pirates were attempting to use to capture the bigger vessel).
That's just the difference between an IT Development/Architect role and an IT Support role.
Software or Hardware design/building is Development.
IT Support roles are things like QA, testing, system administration, internet helldesk.
To the naive person, it's just IT.
Some engineers don't like being called "IT Guys", because they want to make sure they stay as far away as the helldesk as possible. Many developers had bad experiences there in their early years, before they came adept in their field of software development, and now want to distance themselves as far as possible.
Seeing "looking for IT guy" in a job solicitation can be scary.. it's almost like seeing "College Graduate" as the only required qualification... it makes the job look less important, which may reduce it's attractiveness to higher-end applicants ---- this is a marketing error (unless the intent is to hire as cheap applicants as possible, and coax them into other IT roles like sysadmin on the side).
There are people who will see "IT Guy" or see your computer-based role, and assume you can help them with all their petty problems. So carving out a name like "Engineer" offers some protection (although that name Engineer is really already taken by a completely different discipline that has nothing to do with software development).
Anyways... whether developers WANT to be called IT guys or not, is a separate question from Are they IT guys? in fact.
You know, writing software requires troubleshooting, and fixing problems (in software you made though), much like IT Support roles.
Perhaps developers and IT sysadmins are only really that different at a superficial (and social) level, and in regards to the specific subject matter.
Troubleshooting your own code that you have full control over might be a lot easier than troubleshooting complex proprietary systems you don't have control over, and can't necessarily even see the source code to.
I would suspect a brain surgeon specializes on performing surgery on the brain specifically.
Whereas a Neurosurgeon might perform more spinal-column and peripheral-nervous-system type surgery, but may also perform brain surgery.
It never crashes or has a bug.
If it seems to have a bug, then it must be that big companies Poisoned DNS servers!
And after reading items on this timeline. I begin to question the author's sanity...
I like environments without garbage collection, it gives more control, and doesn't degrade system performance while everything has to slow down continuously for GC.
But as for working in an environment without protected memory... that's just crazy talk.
You ARE in IT.
However, it's the equivalent of calling a Brain surgeon a Doctor
Or referring to a Nuclear physicist as a scientist.
It is kind of vague. Sometimes being more specific is good, as it points out people's specialty more.
I don't think you need worry about that much..
It would take like 25 years to re-write COM in python, and that's a conservative estimate (in reality it would probably take much longer).
No, but if you rewrote the Windows kernel and service APIs (kernel.exe, user32.dll, GDI, mstdc, svchost, kernel32.dll, advapi32, win32k.sys, comctl32, comdlg, shell32, shlwapi, Winsock, NetDDE, RPC, NetBIOS, Internet Explorer, etc) in Python, it might be faster, have fewer buffer overflows.
Although i'm sure MS would still figure out some way of introducing security problems of some sort. Trade buffer overflows for kernel-mode Python code injection vulnerabilities.
And since python is such an easier language to understand, python code injection in kernel mode is oh so much easier to exploit, even by novices...
Yeah, it tries to spoonfeed you... arsenic....
No, i'm just kidding.. but it's a good idea to be careful about what you're actually getting fed, when your programming language is trying to feed you.. computers don't tend to be that intelligent, and they might be accidentally feeding you from the wrong jar :)
There's an alternative: Professor Wikipedia is not a scam.
It's the equivalent to writing a program against the Windows API, not testing it, and calling the API buggy when you find that it is failing in the wild.
The API may not match the spec perfectly, but it's your software that's buggy.
Intel can revise the proc, or revise the spec to be in agreement.
MS is trying to use an APIC interrupt for timing that isn't normally used for that purpose.
It's the equivalent of attaching an alarm clock to your electric car's engine, and complaining when the idling speed deviates due to a power saving feature.
Nehalem processors were out long before 2008 R2 or the newest Hyper-V release.
intel Nehalem is a processor with features very attractive to users of virtualization, it's one of the most common procs to be used in new server deployments.
There is absolutely no excuse for MS not extensively testing and qualifying including stress-testing their Hypervisor on Nehalem CPUs before releasing the code.
It would be like you or me writing a piece of desktop software today (in 2009), designed for use with Windows, and extensively testing it on Windows '98 and XP, but not discovering a frequent crash on Vista, that almost always occurs as soon as starting the program.
It's not a processor bug, it's a Windows bug. The advisory should say "download this Windows update" that properly fixes it, not "stop using this processor, because it causes our bug to show up"
By the sound of it MS' fix is abysmal and shoddy.
Then they should register their domains through a russian domain registrar that is outside the US jurisdiction, or through their .RU ccTLD.
Because Network Solutions is a US-based competitive registrar, which has to obey any lawful order made by a US court, under penalty of contempt, and has to obey DMCA notices from companies like Microsoft or risk liability.
Registrars are not immune, and the only reason they haven't frozen DNS for the domain is they weren't ordered to, and Microsoft may not have requested it.
That's because a JVM is not something that you just dump something on. It's not a big truck. It's a series of tubes. And if you don't understand, those tubes can be filled, and if they are filled, when you put your program in, it gets in line, and it's going to be delayed by anyone that puts into the tube enormous emounts of information, enormous amounts of information.
And then, if it gets too congested, your JVM explodes, taking the entire internet with it!
As if the people who manufacture biological weapon delivery system contrary to US law will care about a EULA clause in the JVM they run their software on.