frozencarbonite said:hahaha Don't be sorry. Powerbooks not being affected by this is a good thing to me. I'm still holding tight to my PPC.
PPC FOREVER!!! Intel must die a horrible death along w/ M$!
frozencarbonite said:hahaha Don't be sorry. Powerbooks not being affected by this is a good thing to me. I'm still holding tight to my PPC.
backdraft said:I'm not downloading a sh script to my mac. lol
#! /bin/sh
echo -n "Finding channel and signal strength....."
sleep 1
echo "DONE!!"
echo -n "Preparing shellcode."
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo -n "."
echo "Adding connection information for remote client."
echo -n "Sending attack"
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo "."
echo "Waiting for response"
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo -n "."
sleep 1
echo -n "."
echo "Got Shell"
#Note, requires public key files on remote machine to connect without password
ssh bad@192.168.1.50 'ls'
ssh bad@192.168.1.50
yellow said:??
sleep and echos?
Is this a joke?
It must be a joke.
schenz said:Well... but at least it's not Apple's fault, because they didn't produce the driver. Therefore it's actually not a concern of Apple's but of the driver's producer's.
On the other hand Apple did include it into it's OS seemingly without testing it thorougly, and that is, of course, a concern of Apple's. So they will have to work together to get rid of that - and I'm sure they will - and I may be smug again.![]()
longofest said:The exploit is apparently in the device driver, and so its more of an issue with Atheros than with Apple. I mean, a vulnerability is a vulnerability, and it still needs to be fixed, but the compromised code is most likely not Apple's at least.
matznentosh said:I completely agree. It would be a big surprise to me that any method of connecting to an OS X Mac would allow it to be controlled without specific permissions granted by the administrator account, suggesting these guys left the account open on purpose or allowed remote access with the password known. In other words, once you access the computer you still have to get the operating system to give you permission to screw around.
On the other hand, if this exploit is actually true, it doesn't really matter who's driver is to blame: somehow they were able to subvert OS X's security. THAT would be an issue for Apple and for all of us.
All things considered, I don't believe they did what they claim they did.
thestaton said:Instead of the headline reading macbook hacked in 60 seconds it should of read x vendor welcome to your lawsuit we promise it wont last 60 seconds!
wnurse said:The macbook was HACKED, PERIOD!. End of story.
Than what did get hacked?yellow said:It's not entirely clear what happened, or how.
And it wasn't the Macbook (nor OS X) that got hacked..
JBot said:Than what did get hacked?
The wireless card that was plugged into the macbook.
I know what youre saying, and they have made it clear, this isnt an attack on macs that allowed this hack. any machine is supposedly open to be 'hacked.'
How come it is extremely imporbable and unlikely?gwangung said:Yeah, but their presentation was extremely poor. If it was to show that ANY system could be hacked, why choose a set up that is EXTREMELY improbable and unlikely? It weakens their case and encourages folks to dismiss them.
yellow said:It's just FUDtardery.
yeah, using a third-party card AND driver software. stuff that 99.9% of macbook owners would never use anyway...if their goal was to show THAT a macbook could be hacked, they did show it. but they did not show that a macbook being used in a normal way using macbook drivers and hardware can be hacked. pretty piss-poor, IMO.yellow said:And apparently now they admit that it was bull-****.
http://www.tuaw.com/2006/08/18/secureworks-admits-to-falsifying-macbook-wireless-hack/
![]()
Now, isn't that something. What a great way of proving the 'Get a Mac' commercials wrong. If anything, the myth that Macs are invulnerable is strengthened when they make up lies and are caught.yellow said:And apparently now they admit that it was bull-****.
http://www.tuaw.com/2006/08/18/secureworks-admits-to-falsifying-macbook-wireless-hack/
![]()
yellow said:And apparently now they admit that it was bull-****.
http://www.tuaw.com/2006/08/18/secureworks-admits-to-falsifying-macbook-wireless-hack/
![]()
Despite SecureWorks being quoted saying the Mac is threatened by the exploit demonstrated at Black Hat, they have provided no evidence that in fact it is, Apple Director of Mac PR, Lynn Fox, told Macworld. To the contrary, the SecureWorks demonstration used a third party USB 802.11 devicenot the 802.11 hardware in the Maca device which uses a different chip and different software drivers than those on the Mac. Further, SecureWorks has not shared or demonstrated any code in relation to the Black Hat-demonstrated exploit that is relevant to the hardware and software that we ship.
Yeah, in the beginning I had some respect for what they did, because some parts of the Mac community needs to get some perspective, but now they just look pathetic.benthewraith said:Busted. Boy do I hate to be those guys.![]()
wnurse said:The macbook was hacked in 60 seconds. Why it was hacked or whoose software was responsible is irrelevant. The macbook was HACKED, PERIOD!.
End of story.
JBot said:How come it is extremely imporbable and unlikely?
They presented there script against a mac because the mac strives on the claim that they are the safest pc out there.
They said in there interview they targeted the mac because they hate the commercials.
Explain how that makes there presentation poor.