I think there is one more good thing about it. Java source from Sun depends on Motif and now it can be compiled agains The Real Thing. Not that it was not possible with LessTiff, but it might give some warm fuzzies.
Ok, so publishers are paid by the number of ad's pulled from ad sites as the result of viewing publisher's pages. Here's how I can support those publishers and keep my sanity: the browser will pull the ads but WON'T display them. How 'bout that? Looks like a decent proposition if you don't care much about wasted bandwidth.
If group 0 (normally ``wheel'') has users listed then only those users can su to ``root''.
So, if you want GNUish behavoir, just remove root from that group. And everybody will be allowed to su. The reason it's the way it is -- 'secure by default'.
And why is it better than having an ip filter on the resource server allowing only the webserver contact the resource server? Resource server will only be available to the web server in both cases. But you won't have the headache of running two different network protocols on the webserver.
Many of you have been posting your questions and concerns in reference to the proposed Usenet Death Penalty (UDP) which would block the @Home Network from posting to USENET. I have attached our official response to the Usenet community and the press here but wanted to bring attention to a couple of points that are raised here:
- This afternoon we began a network wide scan targeting open proxy servers.
- If an open server is identified, the customer associated will be blocked from posting to Usenet until such time we are assured that the proxy software is secured.
------------------------------ To the USENET community:
In response to the recent UDP call for @Home Network to be removed from interacting on the USENET, we are submitting an official response with a proposal of short term and long term news spam prevention initiatives. Excite@Home is very committed to participating respectfully on the Internet, and we have taken previous requests for action seriously.
We have found that the primary source of our excessive USENET posting history comes from subscribers who have installed proxy software incorrectly. Unbeknownst to the customer, this mis-configuration has allowed outside access to the @Home news servers, and has resulted in our subscribers becoming spam relays. Because these various IP addresses create holes in our network, spammers have taken advantage of this mis-configuration, and have posted thousands of newsgroup messages through our news machines.
As of today, we are stepping up our involvement and taking more aggressive action by performing frequent network wide scans of our customer base to target proxy servers. Once these customers are identified, we are suspending their news service immediately. Re-enabling will not occur until we are assured that their machines are secure. We feel that this proactive effort will dramatically decrease the amount of extraneous news traffic originating from home.com.
We are committed to promoting better Excite@Home participation on the USENET, and we are in the process of modifying our current news product and news architecture. We are also implementing more user education as a parallel initiative.
With these new tactics in place, we are asking for an extension to our USENET access beyond the 18th of January and we are confident that the USENET community will see positive news statistics coming in the next few days.
David Jackson Manager, Network Policy Management Excite@Home
And where the encryption/decryption will take place? If the answer is not "in your browser, dummy!" it is does not make much sense to implement the thing...
(Even for the Swing toolkit, which being new, you'd have thought Sun would standardise between 1.1 and 1.2... no way! It's in javax for one and java.swing in the other. During the betas, it's also been in java.awt.swing.)
How could that many factual errors be done in that few sentences? Let me guess, you used this strange Symantec product called Visual Cafe?
Swing was in com.sun.java.swing for some time. And now, since release 1.1something, it is always under javax.swing on both 1.1 and 1.2, and it has been this way for more than a year already.
Slashdot Mirror
You're probably talking about Freenet here. Freenet doesn't depend on dns at all, so no WIPO can take your domain away from you.
http://freenet.sourceforge.net
Now if somebody could completely remove reliance on dns for e-mail, I would say to hell with dns.
I think there is one more good thing about it. Java source from Sun depends on Motif and now it can be compiled agains The Real Thing. Not that it was not possible with LessTiff, but it might give some warm fuzzies.
Ok, so publishers are paid by the number of ad's
pulled from ad sites as the result of viewing publisher's pages. Here's how I can support those publishers and keep my sanity: the browser will pull the ads but WON'T display them. How 'bout that? Looks like a decent proposition if you don't care much about wasted bandwidth.
Quoting OpenBSD man su:
If group 0 (normally ``wheel'') has users listed then only those users can su to ``root''.
So, if you want GNUish behavoir, just remove root from that group. And everybody will be allowed to su. The reason it's the way it is -- 'secure by default'.
And why is it better than having an ip filter on the resource server allowing only the webserver contact the resource server? Resource server will only be available to the web server in both cases. But you won't have the headache of running two different network protocols on the webserver.
Of course you reported you problems to bugzilla.mozilla.org, didn't you? Mozilla guys are pretty responsive especially to crashes.
From: Newsgroup Policy Specialiste .discussion-secur\
Subject: Usenet UDP - Excite@Home Response
Newsgroups: athome.announce,athome.discussion-athomesvc,athom
ity,athome.discussion-general
Date: Thu, 13 Jan 2000 01:31:26 GMT
Organization: @Home Network
Reply-To: athome-news@corp.home.net
Many of you have been posting your questions and concerns
in reference to the proposed Usenet Death Penalty (UDP) which
would block the @Home Network from posting to USENET. I have attached
our official response to the Usenet community and the press here but
wanted to bring attention to a couple of points that are raised here:
- This afternoon we began a network wide scan targeting open proxy
servers.
- If an open server is identified, the customer associated will be
blocked from posting to Usenet until such time we are assured that
the proxy software is secured.
------------------------------
To the USENET community:
In response to the recent UDP call for @Home Network to be removed
from interacting on the USENET, we are submitting an official response
with a proposal of short term and long term news spam prevention
initiatives. Excite@Home is very committed to participating
respectfully on the Internet, and we have taken previous requests for
action seriously.
We have found that the primary source of our excessive USENET posting
history comes from subscribers who have installed proxy software
incorrectly. Unbeknownst to the customer, this mis-configuration has
allowed outside access to the @Home news servers, and has resulted in
our subscribers becoming spam relays. Because these various IP
addresses create holes in our network, spammers have taken advantage
of this mis-configuration, and have posted thousands of newsgroup
messages through our news machines.
As of today, we are stepping up our involvement and taking more
aggressive action by performing frequent network wide scans of our
customer base to target proxy servers. Once these customers are
identified, we are suspending their news service immediately.
Re-enabling will not occur until we are assured that their machines
are secure. We feel that this proactive effort will dramatically
decrease the amount of extraneous news traffic originating from
home.com.
We are committed to promoting better Excite@Home participation on the
USENET, and we are in the process of modifying our current news
product and news architecture. We are also implementing more user
education as a parallel initiative.
With these new tactics in place, we are asking for an extension to our
USENET access beyond the 18th of January and we are confident that the
USENET community will see positive news statistics coming in the next
few days.
David Jackson
Manager, Network Policy Management
Excite@Home
Carol
Newsgroup Policy Specialist
Excite@Home
And where the encryption/decryption will take place? If the answer is not "in your browser, dummy!" it is does not make much sense to implement the thing...
(Even for the Swing toolkit, which being new, you'd have thought Sun would standardise between 1.1 and 1.2... no way! It's in javax for one and java.swing in the other. During the betas, it's also been in java.awt.swing.)
How could that many factual errors be done in that few sentences? Let me guess, you used this strange Symantec product called Visual Cafe?
Swing was in com.sun.java.swing for some time. And now, since release 1.1something, it is always under javax.swing on both 1.1 and 1.2, and it has been this way for more than a year already.
In case you don't feel like going thru registration hassles, just grab it from /linux/815ship.tgz. It is legal, ain't it?
ftp://ftp.oracle.com/pub/www/otn