Which would mean, for the last several 2.6.x releases, that you are always using a version with a known root hole in it. Here's an idea: use your vendor's QA-tested kernel that they package for your distribution.
There is some confusion of terminology here. An X client is an application which uses the resources that are multiplexed by an X server. With these SunRays the X server is indeed on a centralised server. But the X clients can be anywhere on the network (and in practice they're usually on the same centralised server). The SunRays don't run an X client at all. What they run is a "remote video console", for want of a better term ("remote framebuffer" doesn't cut it because there are input devices as well, making it a console, not just a framebuffer).
The analogy to VNC is much closer, but even that is just an analogy: these things use a proprietary protocol.
If it looks like there is an XDM running, I'm pretty sure that that XDM is actually executing on the SunFire (or whatever server), not on the Sun Ray itself.
So it *is* like a VNC client. VNC is designed to be so simple that you can make a client with some very basic embedded hardware. These Sun Ray things have a 100MHz SPARC in them IRRC.
The outrageous thing is that these screenshots are still posted on the web. This guy obviously completely lacks any sense of ethics. If I posted screenshots of my boss's desktop on the public internet without his permission, I would expect to never work again.
VoIP has had a short and patchy history. In fact, it has been argued by some of the Internet's most respected architects that we may be better off without it altogether!
Remember,
VoIP requires H323 and other setuid scripts, potentially opening your network to crackers.
The internet was simply never designed for realtime interaction, and post-hoc hacks
won't make it realtime: instead the system would probably have to be redesigned from the ground up using realtime-XML.
VoIP completely bypasses the government's
anti-terrorist infrastructure, which depends on intercepting phone calls arbitrarily: it is estimated that each percentage point of calls which are transferred to VoIP will result in 600-800 American deaths per annum through terrorism
I hope people think about these fundamental issues before deploying this sort of technology on the networks they administer.
From a purely pragmatic viewpoint, I should point out that there hasn't been a release of djbdns for a little over twelve years. It is therefore extremely unlikely that the product will updated to support SPF+.
Unfortunately for all the DJB-acolytes, this means that djbdns, as well as being proprietary and insecure, will not have a place on the internet from Jan 1st 2005, the day SPF+ will be activated globally.
If we want to see this Operating System darting through the twenty-first century with a spring in its step, we had better hope that they continue with their emphasis on security. Accordingly, word on the street is that significant effort this hackathon will be put into fixing the first ever OpenBSD virus, before going on to harden their innovative XOR hardware systems.
I'm really surprised no one's mentioned SPF, the "spam permitted from" framework, or its successor SPF+.
The only reason scum like this are still at large is the complacency of our sysadmins in deploying SPF+ on today's systems. Remember, all SPF+ needs to work is our current DNS infrastructure, along with a TCL interpreter in the MUA.
Interestingly, it looks like SPF+ may be forked, as an attempt to escape the ludicrous shoehorning of XML into SPF2 by Microsoft.
Dan isn't the first one to suggest novel new applications for the DNS. Many will also be familiar with SPF, the "spam permitted from" framework for defining permitted email senders. Microsoft have recently taken over the standard process and are proposing for the sender permission rules to be sent in XML format over DNS!
The open source community's response so far has been SPF+, which is essentially a technique of encoding the rules in TCL, which is served over DNS and executed on the mailserver. For obvious reasons, SPF+ will probably define the future of spam control on the internet.
An HTTP URL takes the form:
http://<host>:<
port>/<path>?<searchpart>
where <host> and <port> are as described in Section 3.1. If:<port>
is omitted, the port defaults to 80. No user name or password is
allowed.
The financial offer is utterly bogus. Its existence does not imply any additional security. If you consider the hourly rate of pay of a professional code auditor, the DJB "reward" pales into insignificance. So why bother mentioning it?
Slashdot Mirror
Thanks for explaining the joke, fucktard.
Which would mean, for the last several 2.6.x releases, that you are always using a version with a known root hole in it. Here's an idea: use your vendor's QA-tested kernel that they package for your distribution.
If you're talking about distributions, then, no. The longest life I'm aware of is RHEL at 5 years.
For some reason, useless uses of cat really irritate me.
The analogy to VNC is much closer, but even that is just an analogy: these things use a proprietary protocol.
If it looks like there is an XDM running, I'm pretty sure that that XDM is actually executing on the SunFire (or whatever server), not on the Sun Ray itself.
I would be fascinated to be proved wrong, though.
So it *is* like a VNC client. VNC is designed to be so simple that you can make a client with some very basic embedded hardware. These Sun Ray things have a 100MHz SPARC in them IRRC.
The outrageous thing is that these screenshots are still posted on the web. This guy obviously completely lacks any sense of ethics. If I posted screenshots of my boss's desktop on the public internet without his permission, I would expect to never work again.
# fstat -f / | ipsecadm - - | tcpdump -i - | less
Thanks for your contribution to my state of the art, nacturnation (do you mind if I call nacty?)
Remember,
- VoIP requires H323 and other setuid scripts, potentially opening your network to crackers.
- The internet was simply never designed for realtime interaction, and post-hoc hacks
won't make it realtime: instead the system would probably have to be redesigned from the ground up using realtime-XML.
- VoIP completely bypasses the government's
anti-terrorist infrastructure, which depends on intercepting phone calls arbitrarily: it is estimated that each percentage point of calls which are transferred to VoIP will result in 600-800 American deaths per annum through terrorism
I hope people think about these fundamental issues before deploying this sort of technology on the networks they administer.Unfortunately for all the DJB-acolytes, this means that djbdns, as well as being proprietary and insecure, will not have a place on the internet from Jan 1st 2005, the day SPF+ will be activated globally.
Other plans include replacing BIND with djbdns, and integrating SPF+ with sendmail.
Aww, missed it. Don't suppose anyone's got another one of them?
Interestingly, it looks like SPF+ may be forked, as an attempt to escape the ludicrous shoehorning of XML into SPF2 by Microsoft.
WARNING: Parent post advocates proprietary DJB software! Please disregard the parent post for all the usual reasons. Thank you.
The open source community's response so far has been SPF+, which is essentially a technique of encoding the rules in TCL, which is served over DNS and executed on the mailserver. For obvious reasons, SPF+ will probably define the future of spam control on the internet.
The rfc you just linked to says:
Or are you the troll?
sh: !/bin/rm: event not found
(csh gives a similar error).
Maybe not, fuckface.
Actually I've been manually checked many times on the Underground over the last couple of years. Euston seems to be the most frequent for this.
The metric system is indeed decimal. The USD currency is also decimal. That does not imply that the USD currency is metric.
My car is blue. The sky is blue. Therefore the sky is a car.
WTF? My own government? Talk about making assumptions. Oh, look what GISGEOLOGYGEEK's government is up to at the moment!
You seem to be conflating "decimal" with "metric".
The financial offer is utterly bogus. Its existence does not imply any additional security. If you consider the hourly rate of pay of a professional code auditor, the DJB "reward" pales into insignificance. So why bother mentioning it?
Theo won their massive flamewar tho. (see link in sig)
Please do not go near the software advertised in the parent post.