It's really easy to get KDE to behave the usual way actually. I just installed (null) and indeed, the desktop was exactly like GNOME's but the redhat desktop for GNOME is not the original one either. it took me about 10 minutes to set KDE to behave exactly the way I want it too and to use all the original KDE icons.
Sun should not be congratulated, I think. Linux does not need OpenOffice, and I really do not care if anyone thinks that this is a naive statement.
Well that's good...
Because it is a very naive statement.
OpenOffice is a serious project based on a code base that is gaining a tremendous amount of maturity and also bleeding edge technology.
It is one of the projects that actively participate in an real implementation of linux for business users.
Without business interest in linux, there won't be any sponsors, any redhat, etc...
Unniversities will stop working on linux based projects since no one else than teenagers actually does anything productive with it.
I think it is time to see past the little jealousy crisis with companies that actually know what they're doing (like sun for example) and are willing to help the OSS community as long as obviously this community doesn't try to run them out of business.
I think it is a nice gesture from sun.
You seem to be confusing the changelog with a marketing tool, which is pretty much what microsoft just released.
All of a sudden, the microsoft people announce that users may chose the default browsers, email software, media player (which they could already do before), and microsoft decides to release some of their code in open source, blablabla...
They see the new thing that's starting to work and they want their piece of the pie... It seems logic enough to me.
Also the kernel changelogs are made to be understood by developers, not end users.
The end user that wants to be able to read a changelog and understand will read the major distributions' changelogs and will see something they can read like "Now brews your coffee every morning".
This is the marvel of marketing my friend.
X-Force has verified that this issue is exploitable on Apache for
Windows (Win32) version 1.3.24. Apache 1.x for Unix contains the same
source code, but X-Force believes that successful exploitation on most
Unix platforms is unlikely.
and
From Apache.org:
In Apache 1.3 the issue causes a stack overflow. Due to the nature of the
overflow on 32-bit Unix platforms this will cause a segmentation violation
and the child will terminate. However on 64-bit platforms the overflow
can be controlled and so for platforms that store return addresses on the
stack it is likely that it is further exploitable. This could allow
arbitrary code to be run on the server as the user the Apache children are
set to run as.
We have been made aware that Apache 1.3 on Windows is exploitable in this
way.
Now, what were you saying about Windows vs. *nix?
--------
Well this at least shows that the feeling of slashdot people about the people at ISS-XForce posting "advisories" and "announcements" based on half fiction was founded after all...
Also, system administrators of any platform, especially 64Bit platforms have the option to
browse through the apache CVS code where the security risk has been eliminated and patch their own apache, or simply disable chunk request responses, still in the source.
Once again, I really don't think you have this option if you decide to run an IIS server, which has bigger issues with the same problem (HTTP requests fragmentation).
Slashdot Mirror
It's really easy to get KDE to behave the usual way actually.
I just installed (null) and indeed, the desktop was exactly like GNOME's but the redhat desktop for GNOME is not the original one either.
it took me about 10 minutes to set KDE to behave exactly the way I want it too and to use all the original KDE icons.
It's really not that bad.
slashdot effect. any HTML page we could look at ?
Sun should not be congratulated, I think. Linux does not need OpenOffice, and I really do not care if anyone thinks that this is a naive statement. Well that's good... Because it is a very naive statement. OpenOffice is a serious project based on a code base that is gaining a tremendous amount of maturity and also bleeding edge technology. It is one of the projects that actively participate in an real implementation of linux for business users. Without business interest in linux, there won't be any sponsors, any redhat, etc... Unniversities will stop working on linux based projects since no one else than teenagers actually does anything productive with it. I think it is time to see past the little jealousy crisis with companies that actually know what they're doing (like sun for example) and are willing to help the OSS community as long as obviously this community doesn't try to run them out of business. I think it is a nice gesture from sun.
You seem to be confusing the changelog with a marketing tool, which is pretty much what microsoft just released. All of a sudden, the microsoft people announce that users may chose the default browsers, email software, media player (which they could already do before), and microsoft decides to release some of their code in open source, blablabla... They see the new thing that's starting to work and they want their piece of the pie... It seems logic enough to me. Also the kernel changelogs are made to be understood by developers, not end users. The end user that wants to be able to read a changelog and understand will read the major distributions' changelogs and will see something they can read like "Now brews your coffee every morning". This is the marvel of marketing my friend.
X-Force has verified that this issue is
exploitable on Apache for
Windows (Win32) version 1.3.24. Apache 1.x for
Unix contains the same
source code, but X-Force believes that
successful exploitation on most
Unix platforms is unlikely.
and
From Apache.org:
In Apache 1.3 the issue causes a stack overflow.
Due to the nature of the
overflow on 32-bit Unix platforms this will
cause a segmentation violation
and the child will terminate. However on 64-bit
platforms the overflow
can be controlled and so for platforms that
store return addresses on the
stack it is likely that it is further
exploitable. This could allow
arbitrary code to be run on the server as the
user the Apache children are
set to run as.
We have been made aware that Apache 1.3 on
Windows is exploitable in this
way.
Now, what were you saying about Windows vs. *nix?
--------
Well this at least shows that the feeling of
slashdot people about the people at ISS-XForce
posting "advisories" and "announcements" based on
half fiction was founded after all...
Also, system administrators of any platform,
especially 64Bit platforms have the option to
browse through the apache CVS code where the
security risk has been eliminated and patch
their own apache, or simply disable chunk
request responses, still in the source.
Once again, I really don't think you have this
option if you decide to run an IIS server, which
has bigger issues with the same problem (HTTP
requests fragmentation).