That's funny, because I've tended to see that as the opposite in most cases (not saying it's better, just the coding-style I've seen and it seems fairly clean), e.g.
sub foo {
$var = 22;
$anothervar = 23;
if ( $var == $anothervar )
{
return $var1;
} }
Nope? This guy did commit crimes. He also committed them against powerful people. It's not at all surprising he's going to be spending a fair bit of time in prison. The interesting part is more in regards to the extradition, and possibly that he didn't suffer an "accident" on his way to the US for trial.
I've used a couple editors which pretty much represent a tab as a certain number of spaces at the line beginning, but as a tab later in the line. It looks *beautiful* in the editor.
Then I opened it in vim, and discovered that it was still inserting actual tabs but just visually formatting them to look nice and uniform. I'm pretty sure people wonder why my code looks like ass.
I do like the idea of space-from-the-left, tab-on-the-right though
e.g. spaces for function/comparison/loop/etc indents, tabs for things like lining up variable definition as
function somefunct {
$bob = 1;
$sam = 2; }
p.s. Next coding holy-war, brackets in the function definition or the following line?
To transfer 40M without going through a chain of command/authorization is absurd, even with an authenticated email (after all, the boss could have had a machine stolen/hacked/etc).
And if somebody buys a Satellite phone and then turns out to be an ISIS member, who then speaks in code so he's not detected, do you then go after the phone provider?
You want info, get a warrant. But the fact that the service exist doesn't mean it does so for the purpose of servicing a terrorist organization.
the premise of the book is decent and increasingly applicable to daily life, but frankly the writing itself is dated and rather lame. Yes, it's a classic. That doesn't make it interesting or mean that it's not overly verbose in many places.
Or, you know, the affected countries could remove the loopholes that allows this to occur. I agree that "all taxes should be paid where the revenue is generated", but that's a matter of law for the country in which the revenue is generated (including in the Americas). It's not as if this is an unknown issue, it's just that "campaign contributions" (and the fact that your politicians come from the same socio-economic class as these companies) keep the loopholes open.
Now how you do this really depends on your location and/or ISP, but some ISP's do not count in-network traffic against your bandwidth, so if you have a buddy on the same ISP you could set him/her up with a little box and a few hard drives, running something like "ez-ipupdate" to keep track of either his IP or yours. Have a sync job that runs regularly.
Worried about your somebody seeing your tax info in the backups (or ya'know, pictures of your wang, etc)? Run something like "duplicity" which encrypts the backup.
Now if your ISP does count in-network bandwidth, or just otherwise sucks, and your buddy lives farther away but still within visual range? Do what some friends of mine did and setup a point-to-point wifi. It's actually pretty cool what bandwidth you can get with a pringles can, metal colander, and some cheap wireless gear. If your buddy happens to be a neighbour, then you could also trying stringing some cat5e/cat6 between your houses.
The problem with a simple syringe is that - depending on the medical scenario - it can be quite difficult to inject somebody who is in the middle of an allergy attack (or near impossible for the person to inject himself/herself). I'd imagine that it's also a *lot* easier to do things like flying with a recognised device such as an epipen as opposed to a prepped syringe.
But yeah, it's nice to have high standards for devices but sometimes perhaps we need "not 100%, but good enough given the need".
My guess would be some sort of malware loaded onto people's computers that's ratting them out (probably snuck into various torrents). That would be "direct", but also likely fairly illegal...
Nothing is every guaranteed, but zeroing a drive is generally good enough for most consumer needs unless you've got some *really* determined people that are going to be after your data. On modern high-density spinning-rust drives, it's pretty hard to reliably recover contiguous bits of information from a zeroed drive without some special hardware (or hardware modifications).
As we move to SSD's, however, I'm not sure even a random-write will work when the hardware itself may be marking off various parts of the disk as do-not-use over time. I would think that in that case, those bits aren't being overwritten during zeroing and might have useful little bits of data in some cases.
"what's so scary about a pacemaker that can "be hacked" by someone with enough time and determination"
Well, part of it would be detection, and - depending on the hack - range. If, for example, a malicious actor could write a virus that causes all infected mobile phones to take down pacemakers in the area... that would be bad shit. Given the number of insecure IoT devices out there, it need not be a phone, but one of thousands or millions of little devices which could be converted to nefarious means.
This is pretty common for medical records too. When the hospital gives you results of cancer screening/X-Rays, it's often a bunch of files or images/videos on a DVD
Right, because it's not as if California is having enough drought to have a government site for it, or western canada. Or how about the oceans, where marine-life can be *very* temperature sensitive.
Or how about a change in parasites, which affects both humans and food-chain animals? The good news is that some parasites that like it cool may die out, but those that prefer warmer temperatures (the majority) will spread more readily.
Money goes on the books, a whole bunch of time cut off from the world has a more visible impact, is more visible to both shareholders and partners, and could have a longer-reaching effect.
A big fine could possibly be "fixed" by laying off people and cutting costs/corners to save money. Being out for 100 days, you're going to need those staff to catch up...
"First off unless you live in the 3rd world shit hole, pollution has gotten lower than it has ever been in my life time and that of my parents and even grandparents"
You realise that there different types of pollution, and not all of it comes in the form of overly visible black smog or choking dust? As for 3rd-world shitholes - as you call them - yeah those will be affected first because they're generally already on the line, but then so will your favourite vacation stops, coastal cities, and your food supply as crops go thirsty and water gets scarce.
Usually when I look back at my code from a few years back, I have a "WTF did I do it that way" moment or two. This is because I'm constantly finding better ways of doing things. IT in this way is comparable to being a mechanic. Yes, the new just-of-of-school mechanic may have been taught a few tricks about new automotive technology that the old guys don't know, but the older guys have *years* of experience in the little intricacies or gotchas of the vehicles they service, the tools they use, and the industry in general. They know that a certain pattern of wear tends to indicate a part failing in a particular way. They have a process down where the job can be done faster. They know that supplier A is cheaper but supplier B is better or faster to provide parts, or to which one is more likely to screw up an order.
All that type of knowledge also applies to IT, particular veterans of a particular company. They know your other staff, your suppliers, their habits and best practices. They know which meetings are important, and which they may wish to skip in order to get work done. They know the best time to work on gear to incur minimal downtime. They know that machine in the back rack has a weird issue the vendor hasn't been able to pin down, or hasn't documented, but how to fix it when it occurs (yes, it's in a doc somewhere but they don't need to spend 1-2h searching for the *right* doc). They know John in accounting always takes Fridays off so that's a good time to service his workstation but a bad time to schedule a meeting with him, and that you really want to use the *official* GBIC's for Company A because even though company B's work they're knockoffs and don't have unique MAC addresses. They know how to diffuse a conflict even with somebody who they really *really* don't like, or to smile and answer the big boss's questions about his home router.
All that shit is important, and it's all stuff that you learn from experience that makes you a better worker. Not all of it is portable between companies, but a surprising amount of it can be. It's that 5-minute conversation or trick that saves days of hassle, and possibly a whole lot of money. That's not to say all older IT people are equal, but there's a value to experience that can never quite be captured.
As long as you're not including things like "jaywalking" or smaller traffic violations in those crimes unless they show a clear pattern.
Now stopping people who are just getting into petty theft, drug crimes, petty violence etc is probably a good idea. At the same time though, giving the early offenders means and motivation to straighten their shit out before they become big offenders is probably a good idea.
By the same token, seizing the car of some rich shit who doesn't give a f*** about those parking/speeding tickets he's been accumulating might help prevent him from killing somebody in a vehicular homicide later on, while ticketing the shit out of a poorer person isn't going to help things at all.
Those only work in one of two ways a) Domains which a company has the SSL keys to (presumably ones they own), in order to detect malicious attempts such as SQL injections etc etc. They don't do much about encrypted outgoing traffic if it's permitted. Alternately, the SSL may be terminated at the security device and non-SSL traffic passed to the webserver etc. Again, this does nothing for 3rd-party sites and/or connections going out from desktops.
b) Companies which generate a non-legitimate global SSH key which is trusted for all domains and is loaded (by policies etc) in to the load browsers. E.G. a cert which applies for *.com; *.net; etc etc. Outgoing SSL actually connects to the appliance which has the master key for the non-legit cert, which basically performs a MITM and then proxies the SSH connection to the outside site. You have to have some pretty strict policies and browser-restrictions to really make this work, and frankly it has some pretty ugly privacy violations because it's faking out *all* SSL from potential attack sites to your employees' medical provider.
Slashdot Mirror
That's funny, because I've tended to see that as the opposite in most cases (not saying it's better, just the coding-style I've seen and it seems fairly clean), e.g.
sub foo
{
$var = 22;
$anothervar = 23;
if ( $var == $anothervar )
{
return $var1;
}
}
Nope?
This guy did commit crimes. He also committed them against powerful people. It's not at all surprising he's going to be spending a fair bit of time in prison. The interesting part is more in regards to the extradition, and possibly that he didn't suffer an "accident" on his way to the US for trial.
I've used a couple editors which pretty much represent a tab as a certain number of spaces at the line beginning, but as a tab later in the line. It looks *beautiful* in the editor.
Then I opened it in vim, and discovered that it was still inserting actual tabs but just visually formatting them to look nice and uniform. I'm pretty sure people wonder why my code looks like ass.
I do like the idea of space-from-the-left, tab-on-the-right though
e.g. spaces for function/comparison/loop/etc indents, tabs for things like lining up variable definition as
function somefunct {
$bob = 1;
$sam = 2;
}
p.s. Next coding holy-war, brackets in the function definition or the following line?
To transfer 40M without going through a chain of command/authorization is absurd, even with an authenticated email (after all, the boss could have had a machine stolen/hacked/etc).
You don't really wake up on fire, but you do have to start worrying if burns when you pee...
And if somebody buys a Satellite phone and then turns out to be an ISIS member, who then speaks in code so he's not detected, do you then go after the phone provider?
You want info, get a warrant. But the fact that the service exist doesn't mean it does so for the purpose of servicing a terrorist organization.
Choose 2
* More product
* Less overhead
* Better quality
Guess which one is losing out in many of these cases...
the premise of the book is decent and increasingly applicable to daily life, but frankly the writing itself is dated and rather lame. Yes, it's a classic. That doesn't make it interesting or mean that it's not overly verbose in many places.
Parallel construction, aka "a conveniently timed and helpful anonymous tip"
Another thing encryption helps with: making it harder to plant evidence on digital devices...
Yeah... I'm in the "go f*** yourself" camp on this one.
Or, you know, the affected countries could remove the loopholes that allows this to occur. I agree that "all taxes should be paid where the revenue is generated", but that's a matter of law for the country in which the revenue is generated (including in the Americas). It's not as if this is an unknown issue, it's just that "campaign contributions" (and the fact that your politicians come from the same socio-economic class as these companies) keep the loopholes open.
"removes high-risk drivers from the road"
Well, presumably applying for a false identification would be a criminal violation, so going to jail would remove one from the road...
Now how you do this really depends on your location and/or ISP, but some ISP's do not count in-network traffic against your bandwidth, so if you have a buddy on the same ISP you could set him/her up with a little box and a few hard drives, running something like "ez-ipupdate" to keep track of either his IP or yours. Have a sync job that runs regularly.
Worried about your somebody seeing your tax info in the backups (or ya'know, pictures of your wang, etc)? Run something like "duplicity" which encrypts the backup.
Now if your ISP does count in-network bandwidth, or just otherwise sucks, and your buddy lives farther away but still within visual range? Do what some friends of mine did and setup a point-to-point wifi. It's actually pretty cool what bandwidth you can get with a pringles can, metal colander, and some cheap wireless gear. If your buddy happens to be a neighbour, then you could also trying stringing some cat5e/cat6 between your houses.
The problem with a simple syringe is that - depending on the medical scenario - it can be quite difficult to inject somebody who is in the middle of an allergy attack (or near impossible for the person to inject himself/herself). I'd imagine that it's also a *lot* easier to do things like flying with a recognised device such as an epipen as opposed to a prepped syringe.
But yeah, it's nice to have high standards for devices but sometimes perhaps we need "not 100%, but good enough given the need".
So in other words, "direct detection" is still pretty a source-IP based identifier. Pretty weak.
My guess would be some sort of malware loaded onto people's computers that's ratting them out (probably snuck into various torrents). That would be "direct", but also likely fairly illegal...
Nothing is every guaranteed, but zeroing a drive is generally good enough for most consumer needs unless you've got some *really* determined people that are going to be after your data. On modern high-density spinning-rust drives, it's pretty hard to reliably recover contiguous bits of information from a zeroed drive without some special hardware (or hardware modifications).
As we move to SSD's, however, I'm not sure even a random-write will work when the hardware itself may be marking off various parts of the disk as do-not-use over time. I would think that in that case, those bits aren't being overwritten during zeroing and might have useful little bits of data in some cases.
"what's so scary about a pacemaker that can "be hacked" by someone with enough time and determination"
Well, part of it would be detection, and - depending on the hack - range. If, for example, a malicious actor could write a virus that causes all infected mobile phones to take down pacemakers in the area... that would be bad shit. Given the number of insecure IoT devices out there, it need not be a phone, but one of thousands or millions of little devices which could be converted to nefarious means.
This is pretty common for medical records too. When the hospital gives you results of cancer screening/X-Rays, it's often a bunch of files or images/videos on a DVD
Right, because it's not as if California is having enough drought to have a government site for it, or western canada. Or how about the oceans, where marine-life can be *very* temperature sensitive.
Or how about a change in parasites, which affects both humans and food-chain animals? The good news is that some parasites that like it cool may die out, but those that prefer warmer temperatures (the majority) will spread more readily.
Money goes on the books, a whole bunch of time cut off from the world has a more visible impact, is more visible to both shareholders and partners, and could have a longer-reaching effect.
A big fine could possibly be "fixed" by laying off people and cutting costs/corners to save money. Being out for 100 days, you're going to need those staff to catch up...
"First off unless you live in the 3rd world shit hole, pollution has gotten lower than it has ever been in my life time and that of my parents and even grandparents"
You realise that there different types of pollution, and not all of it comes in the form of overly visible black smog or choking dust? As for 3rd-world shitholes - as you call them - yeah those will be affected first because they're generally already on the line, but then so will your favourite vacation stops, coastal cities, and your food supply as crops go thirsty and water gets scarce.
Usually when I look back at my code from a few years back, I have a "WTF did I do it that way" moment or two. This is because I'm constantly finding better ways of doing things. IT in this way is comparable to being a mechanic. Yes, the new just-of-of-school mechanic may have been taught a few tricks about new automotive technology that the old guys don't know, but the older guys have *years* of experience in the little intricacies or gotchas of the vehicles they service, the tools they use, and the industry in general.
They know that a certain pattern of wear tends to indicate a part failing in a particular way. They have a process down where the job can be done faster. They know that supplier A is cheaper but supplier B is better or faster to provide parts, or to which one is more likely to screw up an order.
All that type of knowledge also applies to IT, particular veterans of a particular company. They know your other staff, your suppliers, their habits and best practices. They know which meetings are important, and which they may wish to skip in order to get work done. They know the best time to work on gear to incur minimal downtime. They know that machine in the back rack has a weird issue the vendor hasn't been able to pin down, or hasn't documented, but how to fix it when it occurs (yes, it's in a doc somewhere but they don't need to spend 1-2h searching for the *right* doc). They know John in accounting always takes Fridays off so that's a good time to service his workstation but a bad time to schedule a meeting with him, and that you really want to use the *official* GBIC's for Company A because even though company B's work they're knockoffs and don't have unique MAC addresses. They know how to diffuse a conflict even with somebody who they really *really* don't like, or to smile and answer the big boss's questions about his home router.
All that shit is important, and it's all stuff that you learn from experience that makes you a better worker. Not all of it is portable between companies, but a surprising amount of it can be. It's that 5-minute conversation or trick that saves days of hassle, and possibly a whole lot of money. That's not to say all older IT people are equal, but there's a value to experience that can never quite be captured.
"can fail before my phone battery does"
No worries - with your phone using the Bluetooth radio constantly - the extra battery drain ensures it will fail first!
As long as you're not including things like "jaywalking" or smaller traffic violations in those crimes unless they show a clear pattern.
Now stopping people who are just getting into petty theft, drug crimes, petty violence etc is probably a good idea. At the same time though, giving the early offenders means and motivation to straighten their shit out before they become big offenders is probably a good idea.
By the same token, seizing the car of some rich shit who doesn't give a f*** about those parking/speeding tickets he's been accumulating might help prevent him from killing somebody in a vehicular homicide later on, while ticketing the shit out of a poorer person isn't going to help things at all.
Those only work in one of two ways
a) Domains which a company has the SSL keys to (presumably ones they own), in order to detect malicious attempts such as SQL injections etc etc. They don't do much about encrypted outgoing traffic if it's permitted. Alternately, the SSL may be terminated at the security device and non-SSL traffic passed to the webserver etc. Again, this does nothing for 3rd-party sites and/or connections going out from desktops.
b) Companies which generate a non-legitimate global SSH key which is trusted for all domains and is loaded (by policies etc) in to the load browsers. E.G. a cert which applies for *.com; *.net; etc etc. Outgoing SSL actually connects to the appliance which has the master key for the non-legit cert, which basically performs a MITM and then proxies the SSH connection to the outside site. You have to have some pretty strict policies and browser-restrictions to really make this work, and frankly it has some pretty ugly privacy violations because it's faking out *all* SSL from potential attack sites to your employees' medical provider.