One might argue that a "malware researcher" might already be at increased risk of having already contracted some sort of exploit that might manifest as a malicious redirect.
Then again, where Equifax and their recent security fumbles are concerned, it's certainly within the realm of possibility that such an exploit found its way into their services. Unless there's an independent and unbiased analysis of the Equifax systems and protocols, it's unlikely we'll ever be certain.
We have a guy in the office with an Android phone... on which he had installed an app that he mistakenly configured in such a way that it killed all wireless connections within 50 yards. Apparently, it had a feature to create an ad-hoc network, which he gave the same name as our corporate wireless network. Joe Employee tried to connect to the corporate wireless network with a particular name, it spotted the ad hoc network and refused to connect. We had all kinds of complaints.
I would agree wholeheartedly with this recommendation. As a ham myself, I can say that many hams would very much enjoy the opportunity to solve a radio-related mystery like this for the public.
Here's the cool thing: if a ham determines that the source of interference also happens to interfere in any way whatsoever with ham radio communications, then the FCC will take notice and will compel the responsible party to correct their systems. The upside is that while the potentially-affected licensed services get fixed (ham radio), so do the unlicensed services (wifi). That is to say, messing with ham communications is bad. There are many cases where hams have had the FCC compel even electric companies to make needed changes and repairs to their systems. Of course, this may not be the case, but it doesn't hurt to investigate it.
We'll even track the problem down for free. Of course, like you said, pizza and beer are good, too.
A private building does not equate to a public road. All licensed drivers in properly licensed vehicles may use public roads and highways. If you don't like the rolling road block ahead of you, choose a different road or get used to the fact that those people in front of you have the same rights that you do.
What's really scary is that there are people out there who actually believe exactly what you said. In their disturbed little minds, if everybody in the world could just have kind, happy thoughts all the time, then we would all get along.
These self-proclaimed pacifists literally become violent if you don't have the right kind of happy thoughts.
Hack magic? They're called quotes. If a string has spaces in it, I enclose the entire string in quotes. One could also delimit the spaces with a backslash in a one-liner. Sometimes, I change the Input Field Separator (IFS) to exclude spaces within a script. It's not magic. Just the nature of language.
It's Not a Security Device
on
Life Recorder
·
· Score: 1
This would be better classified as a surveillance device, not a security device. Cameras don't provide security -- that's what locks, restraints, and other physical barriers do. Cameras only serve to provide evidence afterwards... or to gather amusing videos of its owner doing stupid things so they can be posted on break.com.
Kinda my attitude, too. Had this affect a bunch of servers yesterday. Started researching, found the cause, and solved the problem in 30 minutes on 35 or so servers. Totally my own damned fault for not staying upgraded. Worst impact was that messages were delayed on a few mail server for half an hour and uploads to a handful of webservers threw errors because of the way I scan them. Users tried again. Problem solved.
Get enough people redirected to goatse.fr when they click that link promising cute kittens and they might get shocked enough to simply stop clicking on cute kitten links. Then again, there will always be people who keep clicking through hoping that that adorable little feline will ultimately appear if they click it enough times.
Yeah, we can't fix stupid; we can only try to protect them from themselves.
Most users rarely use the F1 key for its intended purpose: to get help on whichever application they're fumbling through and instead just ask the nearest person to them who "knows a lot about computers" for help. So, the risk here is probably pretty small.
If your target were stationary, with good light, and several seconds to steady yourself, with no stress -- sure, one could hit a target an inch across.
Now do that under stress, in poor light, with a very small moving target, covered by clothing and hair, and don't forget that you have about half to two seconds in which to land that shot.
Every moment that ticks by is another moment that the assailant has to kill you. A violent criminal actor is not going to stop because you've shot him in the chest with a.22 -- odds are pretty good that even if you hit his aorta, he'll still have about 20 to 30 seconds more to do what he's going to do to you.
There's a reason that people who carry a handgun for self defense often go for larger calibers. Primarily because they're more effective than smaller calibers.
All fine points. And don't forget that it's only a.22. One would need to achieve a series of headshots to effectively stop a violent criminal actor. Center of mass with a.22 won't stop a violent actor intent on killing you. And at the 7000 euro price point, they're not going to sell many of these except to maybe a few government agencies or people with more money than brains.
Now that he's finished the game, he'll have to start playing World of Reality -- and start meeting and interacting with some actual people. There are far more quests and achievements out here to earn.
Frankly, I'm ignoring the majority of comments on/. about this because, well, the few that I did see seem to be leaning towards the Apple is Overpriced/Evil/Worthless/NotAsGoodAsSomeOtherOS angle, which doesn't seem to be too helpful.
So, here's a real-world solution that's worked for me so far:
I started by subscribing to the Leopard Server Quick Tour podcast ( http://tinyurl.com/ccwqup ) -- It's only highlights and a bit of detail to get going, but worth watching.
Then I started collecting some of the OSX Server Admin manuals from Apple ( http://tinyurl.com/l336ux but there are others ). The most helpful so far have been Server_Administration_v10.5.pdf and Open_Directory_Admin_v10.5_3rd_Ed.pdf
I wasn't given a budget to go directly to a live Enterprise deployment and take advantage of Apple's fee-based solutions specialists. Instead, it's a learn as I go development first then staged deployment. So, I started with a refurbished Mac Mini ($450) and a 10-user license of OSX 10.5 Leopard Server found on Amazon for $250 -- the upgrade to unlimited users (which we'll need eventually) is only $250 more at the moment.
I'm currently getting my Macs working with the OSX Open Directory server then I'll get Open Directory to talk with Active Directory. Once that's sorted out, it's on to the Apple NetBoot for remote deployments of new machines and users.
Yes, it looks like a real firearm. Very nicely done, actually.
No, it does not look like an AK of any design -- more like the Barrett 50 as somebody else said.
Most reasonable-thinking people probably wouldn't care if it were slung over a shoulder. But if the person transporting it were, for example, at the low ready with it, then people would start getting nervous. If while at the low ready, they happen to sweep it in the direction of somebody who also happened to have an actual, legally-possessed, legally-concealed firearm then, well, somebody's not going to walk away.
That said, in typical/. fashion, I haven't read the entire post, so don't know the particulars of how this thing was being transported.
I use GOTO regularly while debugging and even in some production-level stuff. I've cultured the good|bad habit of leaving 'on error goto errortrap' in code. Predictable errors are one thing. It's those unpredictable ones I usually need to have the whole thing stop without causing problems. Do not pass go, do not collect $200, and absolutely never, ever 'on error resume next'.
There was some code that another sysadmin wrote long ago at work that was doing something like sifting through a huge file tree, checking the files' attributes and content, then deleting the file if certain criteria had been met. Something happened with one of the checks where instead of bailing out, it just started deleting files... all 2.5 million of them.
Thankfully, we have hourly backups.
Reviewing the problem, the first line of their code was 'on error resume next'. They didn't know why it was there, but that's "just the way we've always done it"... which is obviously a warning flag. I changed it to a GOTO -- explained the whole error trap thing to them in painful detail -- then ran it again. The GOTO and error trap did exactly what was expected so we could fix the problem with the object tests... without risk of destroying live data.
Sure, there are better things than the GOTO out there, but to borrow the analogy from hairyfeet, once in a while, you still need a chainsaw to cut down a tree.
It's not the customer's job to know the technical details of a complex computer system and its software. That's what the support tech is for.
It's your job as a tech to listen to the customer's needs, interpret them, devise a solution, and drag them kicking and screaming to that solution.
Irritating? Sure. But that's why they pay you.
Can you educate them? Maybe. Most people just want to click the mouse and see the expected result. Or press the pedal on the floor to make the car go forward. Or push the green Send button and hear a ring. Not everyone wants to learn the details of how things work.
Slashdot Mirror
One might argue that a "malware researcher" might already be at increased risk of having already contracted some sort of exploit that might manifest as a malicious redirect.
Then again, where Equifax and their recent security fumbles are concerned, it's certainly within the realm of possibility that such an exploit found its way into their services. Unless there's an independent and unbiased analysis of the Equifax systems and protocols, it's unlikely we'll ever be certain.
No, really. iDid. It's funny because it's so sad; one has no choice but to laugh. Well, laugh or just stop buying Apple products. ...typed from my Mac.
We have a guy in the office with an Android phone... on which he had installed an app that he mistakenly configured in such a way that it killed all wireless connections within 50 yards. Apparently, it had a feature to create an ad-hoc network, which he gave the same name as our corporate wireless network. Joe Employee tried to connect to the corporate wireless network with a particular name, it spotted the ad hoc network and refused to connect. We had all kinds of complaints.
I would agree wholeheartedly with this recommendation. As a ham myself, I can say that many hams would very much enjoy the opportunity to solve a radio-related mystery like this for the public.
Here's the cool thing: if a ham determines that the source of interference also happens to interfere in any way whatsoever with ham radio communications, then the FCC will take notice and will compel the responsible party to correct their systems. The upside is that while the potentially-affected licensed services get fixed (ham radio), so do the unlicensed services (wifi). That is to say, messing with ham communications is bad. There are many cases where hams have had the FCC compel even electric companies to make needed changes and repairs to their systems. Of course, this may not be the case, but it doesn't hurt to investigate it.
We'll even track the problem down for free. Of course, like you said, pizza and beer are good, too.
A private building does not equate to a public road. All licensed drivers in properly licensed vehicles may use public roads and highways. If you don't like the rolling road block ahead of you, choose a different road or get used to the fact that those people in front of you have the same rights that you do.
What's really scary is that there are people out there who actually believe exactly what you said. In their disturbed little minds, if everybody in the world could just have kind, happy thoughts all the time, then we would all get along.
These self-proclaimed pacifists literally become violent if you don't have the right kind of happy thoughts.
Pacifists scare me.
Hack magic? They're called quotes. If a string has spaces in it, I enclose the entire string in quotes. One could also delimit the spaces with a backslash in a one-liner. Sometimes, I change the Input Field Separator (IFS) to exclude spaces within a script. It's not magic. Just the nature of language.
This would be better classified as a surveillance device, not a security device. Cameras don't provide security -- that's what locks, restraints, and other physical barriers do. Cameras only serve to provide evidence afterwards... or to gather amusing videos of its owner doing stupid things so they can be posted on break.com.
Maybe try to uninstall and purge your existing configs then reinstall from the global repository. Might take care of it in just a few minutes.
Kinda my attitude, too. Had this affect a bunch of servers yesterday. Started researching, found the cause, and solved the problem in 30 minutes on 35 or so servers. Totally my own damned fault for not staying upgraded. Worst impact was that messages were delayed on a few mail server for half an hour and uploads to a handful of webservers threw errors because of the way I scan them. Users tried again. Problem solved.
Get enough people redirected to goatse.fr when they click that link promising cute kittens and they might get shocked enough to simply stop clicking on cute kitten links. Then again, there will always be people who keep clicking through hoping that that adorable little feline will ultimately appear if they click it enough times.
Yeah, we can't fix stupid; we can only try to protect them from themselves.
Most users rarely use the F1 key for its intended purpose: to get help on whichever application they're fumbling through and instead just ask the nearest person to them who "knows a lot about computers" for help. So, the risk here is probably pretty small.
If your target were stationary, with good light, and several seconds to steady yourself, with no stress -- sure, one could hit a target an inch across.
Now do that under stress, in poor light, with a very small moving target, covered by clothing and hair, and don't forget that you have about half to two seconds in which to land that shot.
Every moment that ticks by is another moment that the assailant has to kill you. A violent criminal actor is not going to stop because you've shot him in the chest with a .22 -- odds are pretty good that even if you hit his aorta, he'll still have about 20 to 30 seconds more to do what he's going to do to you.
There's a reason that people who carry a handgun for self defense often go for larger calibers. Primarily because they're more effective than smaller calibers.
All fine points. And don't forget that it's only a .22. One would need to achieve a series of headshots to effectively stop a violent criminal actor. Center of mass with a .22 won't stop a violent actor intent on killing you. And at the 7000 euro price point, they're not going to sell many of these except to maybe a few government agencies or people with more money than brains.
"There will be no (criminal) charges whatsoever," Luque said.
But there should be some charges here. Alas, there's no Criminal Stupidity laws on the books that could be leveled at the vice principal.
Wait a minute. When did Canada become part of the European Union? Did Europe finally remove the whole World Geography section from their textbooks?
Now that he's finished the game, he'll have to start playing World of Reality -- and start meeting and interacting with some actual people. There are far more quests and achievements out here to earn.
On a Mac, use the Active Screen Corners feature of Exposé in System Preferences. Set one corner to start the screensaver. Then, go to the Security page and hit the checkbox next to "Require password..."
That part's easy.
Then you have to train your users to move the mouse over and park in the chosen corner of the screen.
That part's hard.
The human element will always be the weakest link in the security chain.
Frankly, I'm ignoring the majority of comments on /. about this because, well, the few that I did see seem to be leaning towards the Apple is Overpriced/Evil/Worthless/NotAsGoodAsSomeOtherOS angle, which doesn't seem to be too helpful.
So, here's a real-world solution that's worked for me so far:
I started by subscribing to the Leopard Server Quick Tour podcast ( http://tinyurl.com/ccwqup ) -- It's only highlights and a bit of detail to get going, but worth watching.
Then I started collecting some of the OSX Server Admin manuals from Apple ( http://tinyurl.com/l336ux but there are others ). The most helpful so far have been Server_Administration_v10.5.pdf and Open_Directory_Admin_v10.5_3rd_Ed.pdf
I wasn't given a budget to go directly to a live Enterprise deployment and take advantage of Apple's fee-based solutions specialists. Instead, it's a learn as I go development first then staged deployment. So, I started with a refurbished Mac Mini ($450) and a 10-user license of OSX 10.5 Leopard Server found on Amazon for $250 -- the upgrade to unlimited users (which we'll need eventually) is only $250 more at the moment.
I'm currently getting my Macs working with the OSX Open Directory server then I'll get Open Directory to talk with Active Directory. Once that's sorted out, it's on to the Apple NetBoot for remote deployments of new machines and users.
Naturally, YMMV.
If you can't turn it off, I'm sure a pair of wire cutters will solve the problem: high-tech annoyance, meet low-tech solution.
As if my Karma could get any lower...
Yes, it looks like a real firearm. Very nicely done, actually.
No, it does not look like an AK of any design -- more like the Barrett 50 as somebody else said.
Most reasonable-thinking people probably wouldn't care if it were slung over a shoulder. But if the person transporting it were, for example, at the low ready with it, then people would start getting nervous. If while at the low ready, they happen to sweep it in the direction of somebody who also happened to have an actual, legally-possessed, legally-concealed firearm then, well, somebody's not going to walk away.
That said, in typical /. fashion, I haven't read the entire post, so don't know the particulars of how this thing was being transported.
I use GOTO regularly while debugging and even in some production-level stuff. I've cultured the good|bad habit of leaving 'on error goto errortrap' in code. Predictable errors are one thing. It's those unpredictable ones I usually need to have the whole thing stop without causing problems. Do not pass go, do not collect $200, and absolutely never, ever 'on error resume next'.
There was some code that another sysadmin wrote long ago at work that was doing something like sifting through a huge file tree, checking the files' attributes and content, then deleting the file if certain criteria had been met. Something happened with one of the checks where instead of bailing out, it just started deleting files... all 2.5 million of them.
Thankfully, we have hourly backups.
Reviewing the problem, the first line of their code was 'on error resume next'. They didn't know why it was there, but that's "just the way we've always done it"... which is obviously a warning flag. I changed it to a GOTO -- explained the whole error trap thing to them in painful detail -- then ran it again. The GOTO and error trap did exactly what was expected so we could fix the problem with the object tests... without risk of destroying live data.
Sure, there are better things than the GOTO out there, but to borrow the analogy from hairyfeet, once in a while, you still need a chainsaw to cut down a tree.
Scan Obama's brain for that abnormality. You might find it there.
Here's the miniskirt. Here's the coffee. If you're looking for something else sometimes provided by secretaries, you'll have to look elsewhere.
It's not the customer's job to know the technical details of a complex computer system and its software. That's what the support tech is for. It's your job as a tech to listen to the customer's needs, interpret them, devise a solution, and drag them kicking and screaming to that solution. Irritating? Sure. But that's why they pay you. Can you educate them? Maybe. Most people just want to click the mouse and see the expected result. Or press the pedal on the floor to make the car go forward. Or push the green Send button and hear a ring. Not everyone wants to learn the details of how things work.