The vulnerability is present in the Java Runtime Environment (JRE) version 1.7 or later, Atif Mushtaq of security firm FireEye reported on Sunday, while PCs with Java versions 1.6 or earlier installed are not at risk.
He finds an exploit in JRE 1.7+ to force us to roll back to JRE 1.6 -- a version without the sound issue. Very clever.
Guess it's not terribly surprising another major bug was found in a version of Java literally plagued with bugs since the week before it was even released.
I didn't feel that the fix or description was simple, but I did all the things in this thread and one of them worked. But I can't tell you whether it was changing the shortcut or using the big ugly hack. Also, I have about 4 java/jre directories on my computer so I had to stick the big ugly hack file in them all but it finally worked. I got the problem bc of the latest java update 2 days ago. Wish I could be more help.
He finds an exploit in JRE 1.7+ to force us to roll back to JRE 1.6 -- a version without the sound issue. Very clever.
Actually, in my experience, update 32 and 33 of Java 1.6 had the KGS sound issue. I assume subsequent updates of Java 6 also do.
Edit: I just updated to 1.6 update 35, and still have the KGS sound issue. And the -J-Dsun.sound.useNewAudioEngine="false" fix did not work.
Yeah, I'm on 1.6 update 29, and haven't sound, either. I hadn't seen that fix before either, I tried adding that to my bash script, but alas it didn't work.
What are the other fixes? The only one I'd seen prior to this was "uninstall 1.7 and install 1.6"... which obviously doesn't apply to me.
LocoRon wrote:Yeah, I'm on 1.6 update 29, and haven't sound, either. I hadn't seen that fix before either, I tried adding that to my bash script, but alas it didn't work.
What are the other fixes? The only one I'd seen prior to this was "uninstall 1.7 and install 1.6"... which obviously doesn't apply to me.
I have 1.6_30 and have not had any sound issues, perhaps your issues are related to those in the KGS/Linux sound issue threads?
He finds an exploit in JRE 1.7+ to force us to roll back to JRE 1.6 -- a version without the sound issue. Very clever.
Actually, in my experience, update 32 and 33 of Java 1.6 had the KGS sound issue. I assume subsequent updates of Java 6 also do.
Edit: I just updated to 1.6 update 35, and still have the KGS sound issue. And the -J-Dsun.sound.useNewAudioEngine="false" fix did not work.
I wasn't running update 35 after all. It seems after I downloaded and installed update 35, one of the updates for some other software downloaded and installed OpenJDK. In fact, when I do use both the switch to use the old audio engine and the aoss driver when using update 35, KGS sound does work for me, including the stone click. I wonder what I was hadd running when I thought I'd tried 32 or 33?
The vulnerability is present in the Java Runtime Environment (JRE) version 1.7 or later, Atif Mushtaq of security firm FireEye reported on Sunday, while PCs with Java versions 1.6 or earlier installed are not at risk.
He finds an exploit in JRE 1.7+ to force us to roll back to JRE 1.6 -- a version without the sound issue. Very clever.
wms wrote:One of the more difficult bug fixes I've ever done.
Not surprising.
From the article:
Downgrading to an earlier version of Java is not advised, because even though earlier versions aren't vulnerable to this particular exploit, they may contain other bugs that expose still other vulnerabilities.
I wasn't running update 35 after all. It seems after I downloaded and installed update 35, one of the updates for some other software downloaded and installed OpenJDK. In fact, when I do use both the switch to use the old audio engine and the aoss driver when using update 35, KGS sound does work for me, including the stone click. 
