The trouble is that this might not be really a attack, just a scan. Also a lot of routers have some firewall settings that migitate DoS attacks, but without any real possiblity to tune this, or even a good description if the thing in the log is anything important.
The fact that some log says there is a DoS attack does not mean there really is a attack. It only says there is a log.....
SHowing the log is not enough, you have to add some explanation.
One side is callem them terrorists, some other side is calling them freedom fighters.
With freedom of the media you might be able to see both sides from your armchair.
By the way, youtube is a bad example for politcal video's. Youtube takes down objectionable material, and adds advertisements to others. I think liveleak might be a better example.
Kicking the car might have give a dent, something that was provable. Besides that, if you touch the car of some people they get very aggressive. Think about that twice in country with lax firearms laws.
If you are talking about a thing like the scheduler, or memory allocation, yes, lots of eyes have gone over that. However there are many corners in the kernel that do not get many eyes. Are there really that many eyes on the drivers for broadcom ethernet drivers? Or complex things like the TCP/IP scheduleing...
And security researchers are looking for errors in the code. Deliberity inserted vulnerabilities might be much harder to find. Maybe they even are found, but are shot down by the maintainer that shakes his head....
From the leftovers of app inventor as created by MIT you can still make perfectly happy fart button implementation.
The trouble with most of those graphical environments is mostly the same thing. You can create a nice 60% ready app in a minimal time. However the fine tuning and the doing of special things will require effort that equals hard code coding.
Think again. why REALLY why do you want to put your source on the internet?
-Recognision. Your name? --> Then only post excellent code.
-To get some work done? -> post it, document it, expect notthing.
-Someone lese to debug your code? -> unlikely, but possible. Users are more likely to recompile and look for the #define NUMBEROFBUGS 9 and change that value. Making a good build environment available helps a lot if you want more people compiling your code. Please include as much depenancies in your tar.gz as possible, even if that is not your code.
Do not expect miracles however. For every 1000 binary downloads, 30 people will bitch about the colors, 20 will put in feature request that are not feasable, 10 people will download the source, 5 will compile it, and 1 will give you really useful feedback on the source or patch it.
You can focus on makeing that "1000" number much bigger, or make the percentage of usefule feedback better. The latter requires documentation.
The problem there is that a lot of developers do not understand their build environment. It just works. They are not aware that they use libray X Y and Z. You only need to be aware of that if something is not running.
But a few lines in the readme hinting what environment was used can get you a long way.
No, it is like truning your computers off to migitate the problems of as DOS-attack that is happening. Who needs hackers if you have management that does not understand problems.
Your "productivity" is just such a problem. There are always better products in the market, but big bang switches to them on a ad-hoc basis is the recipe to downtime.
How about the japanese situation. Big disaster. Politics decide to take all nuclair power down. Not based on new security rules, but based on the political situtaion.
Now what if you invested 9/10 digits just before such a situation.
However the rules changes about breaking applications: -Security. If there needs a security bug to be fixed (null pointer checks and so on) all bets about compability are off. -open standards. If some standard like posix says a function should return X and linux returns Y, THen there is the choice to stay on the linux island and keep returning X or change the ABI to be compliant to some other unix.
And if you use the wrong language to some maintainer (since you are an engineer, not a politician....), or happen to do something in a subsystem that has an inactive maintainer you patches will stay silently in some unknown patch queue.
I think you will get a visit from the analog police after this.:)
It is like sueing the detective for getting Data he should not have had, because he knew that data should have been private.
If you put a bone in front of a dog, he will get and eat it. You cannot ask the dog owner to pay up for it. you gave the bone. (analogy : dog: users. dog owner: ipadress registrants, bone...;) ) If you want to get rid of the analog, please quote law.
" The question would be whether the downloader knew or reasonably would have known that the copyright holder had uploaded it and intended to distribute it."
Could also be reverted.
"The question would be if the uploader knew when it published the files on bittorrent, the files would be downloaded."
But without some law i would add: {citation needed}
Yup. It is all fancy way to tell services are not in a local closet, but in a specialized center.
It all seems fancy, until you hit downtime, and your SLA happens to be "best effort" and the response time is nothing more than someon looked at it within a certain time. You will never get a sla that returns money for the lost productivity.
You will still have to figure out how to get your backups regularly out of the cloud, and retreive the data if the cloud operator stops. You will have to provide a fast internet link, or maybe even a double link, since if one provider fails, it might be cheaper to have a second provider instead of having one with a expensive business SLA.
Stating "put it in the cloud"sounds simple, but a lot of details are really important. Notice how the Tarticle is a consulting firm in such things? and even they hoose to do in inhouse for quite some time?
Slashdot Mirror
The trouble is that this might not be really a attack, just a scan. Also a lot of routers have some firewall settings that migitate DoS attacks, but without any real possiblity to tune this, or even a good description if the thing in the log is anything important.
The fact that some log says there is a DoS attack does not mean there really is a attack. It only says there is a log.....
SHowing the log is not enough, you have to add some explanation.
You can buy simulaor watch phones in in china.
Where do you live?
management could review on formatting, since that is what a lot of these open access journals do.
You cannot see bullets.
The sound of the laser hitting something (something getting hot very fast will not disintegrate silently) might give the same effect.
Adding a little bit of smoke would give a very big light effect, with the disatvantage of giving your position away.
But as said before, the main problem now is getting enough concentrated enery in a small and safe package.
Wouldn't cause reflection on a real parralel laser (without some focus point) cause bit problem...
Some reflection.... oops there goo all the camera's on the site...
Some reflection ... I hope you were not to attached to that arm of yours...
One side is callem them terrorists, some other side is calling them freedom fighters.
With freedom of the media you might be able to see both sides from your armchair.
By the way, youtube is a bad example for politcal video's. Youtube takes down objectionable material, and adds advertisements to others. I think liveleak might be a better example.
code? If they want learn to code, it should result in things they find interesting. Game creator?
10 print you are awasome
20 goto 10
won't cut it anymore in 2013....
Kicking the car might have give a dent, something that was provable. Besides that, if you touch the car of some people they get very aggressive. Think about that twice in country with lax firearms laws.
If you not living in the amerikas but in the United states of europe, It is so unthought of, it is funny.
But wait... what is that camera doing there....
If you are talking about a thing like the scheduler, or memory allocation, yes, lots of eyes have gone over that. However there are many corners in the kernel that do not get many eyes. Are there really that many eyes on the drivers for broadcom ethernet drivers? Or complex things like the TCP/IP scheduleing...
And security researchers are looking for errors in the code. Deliberity inserted vulnerabilities might be much harder to find. Maybe they even are found, but are shot down by the maintainer that shakes his head....
... 640 Kb should be enough... ... watch out son, that gun is loaded... .... THe price of 1 GB will not go much below 1$....
Well, maybe the dollar is the problem that will be solved then, not as much the scale of the process.....
From the leftovers of app inventor as created by MIT you can still make perfectly happy fart button implementation.
The trouble with most of those graphical environments is mostly the same thing. You can create a nice 60% ready app in a minimal time. However the fine tuning and the doing of special things will require effort that equals hard code coding.
By the way, the number 1% download the source is from observations on sourceforge 5 years ago, never looked in this numbers in these GIT days.
Think again. why REALLY why do you want to put your source on the internet?
-Recognision. Your name? --> Then only post excellent code.
-To get some work done? -> post it, document it, expect notthing.
-Someone lese to debug your code? -> unlikely, but possible. Users are more likely to recompile and look for the
#define NUMBEROFBUGS 9
and change that value. Making a good build environment available helps a lot if you want more people compiling your code. Please include as much depenancies in your tar.gz as possible, even if that is not your code.
Do not expect miracles however. For every 1000 binary downloads, 30 people will bitch about the colors, 20 will put in feature request that are not feasable, 10 people will download the source, 5 will compile it, and 1 will give you really useful feedback on the source or patch it.
You can focus on makeing that "1000" number much bigger, or make the percentage of usefule feedback better. The latter requires documentation.
The problem there is that a lot of developers do not understand their build environment. It just works. They are not aware that they use libray X Y and Z. You only need to be aware of that if something is not running.
But a few lines in the readme hinting what environment was used can get you a long way.
No, it is like truning your computers off to migitate the problems of as DOS-attack that is happening. Who needs hackers if you have management that does not understand problems.
Your "productivity" is just such a problem. There are always better products in the market, but big bang switches to them on a ad-hoc basis is the recipe to downtime.
How about the japanese situation. Big disaster. Politics decide to take all nuclair power down. Not based on new security rules, but based on the political situtaion.
Now what if you invested 9/10 digits just before such a situation.
what?
Since The review was in English, I suppose the bedbugs also spoke English. In the french rooms there was no problem at all.
However the rules changes about breaking applications:
-Security. If there needs a security bug to be fixed (null pointer checks and so on) all bets about compability are off.
-open standards. If some standard like posix says a function should return X and linux returns Y, THen there is the choice to stay on the linux island and keep returning X or change the ABI to be compliant to some other unix.
And if you use the wrong language to some maintainer (since you are an engineer, not a politician....), or happen to do something in a subsystem that has an inactive maintainer you patches will stay silently in some unknown patch queue.
I think you will get a visit from the analog police after this. :)
It is like sueing the detective for getting Data he should not have had, because he knew that data should have been private.
If you put a bone in front of a dog, he will get and eat it. You cannot ask the dog owner to pay up for it. you gave the bone. (analogy : dog: users. dog owner: ipadress registrants, bone... ;) ) If you want to get rid of the analog, please quote law.
Your line of reasoning is flawed.
" The question would be whether the downloader knew or reasonably would have known that the copyright holder had uploaded it and intended to distribute it."
Could also be reverted.
"The question would be if the uploader knew when it published the files on bittorrent, the files would be downloaded."
But without some law i would add: {citation needed}
This is very simple:
-Cop videos bad guy: video is entered as proof.
-Cop videos police violence: Video gets lost/camera was off.
And if everything is always recorded/on the record, people might not want to talk to police anymore since EVERYTHING is recorded.
The paper is up and there
Paper>
Note that the range between 2 nodes (some feet) is comparable to RFID systems.
Yup. It is all fancy way to tell services are not in a local closet, but in a specialized center.
It all seems fancy, until you hit downtime, and your SLA happens to be "best effort" and the response time is nothing more than someon looked at it within a certain time. You will never get a sla that returns money for the lost productivity.
You will still have to figure out how to get your backups regularly out of the cloud, and retreive the data if the cloud operator stops. You will have to provide a fast internet link, or maybe even a double link, since if one provider fails, it might be cheaper to have a second provider instead of having one with a expensive business SLA.
Stating "put it in the cloud"sounds simple, but a lot of details are really important. Notice how the Tarticle is a consulting firm in such things? and even they hoose to do in inhouse for quite some time?