- cypherpunks-legacy - lists.cpunks.org

Thank you so much for your questions and response.
by offshore＠offshore-auction-info.com 26 Jun '02

26 Jun '02

1 0

$US$ Financial Termination, Implications?
by Wilfred L. Guerin 25 Jun '02

25 Jun '02

Here is the treasury info: http://www.fms.treas.gov/dts/index.html DATA: [day# \t value, in millions $$ us] 128 5903323 129 5908064 130 5919484 133 5919899 134 5921164 135 5947373 136 5949975 137 5949975 138 5949975 139 5949975 ... ... 175 5949975 176 5949975 [now] The mandatory debt cap is 5,950,000. This is OBVIOUSLY not a legitimate numerical representation. Standard derivative increase is expected. (Reality) Upon breach of this value, federal govt shuts down, and a bunch of problems ensue... Anyone with knowledge on the topic care to explain? What actually is SUPPOSED to happen? What WILL happen? As elucidated also here: http://www.etherzone.com/2002/henr070202.shtml -Wilfred L. Guerin -- The Unfortionately Slightly Enlightened Sheep. Wilfred(a)Cryogen.com

1 0

Mail delivery failed: returning message to sender
by Mail Delivery System 25 Jun '02

25 Jun '02

This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: jmace(a)flash.net SMTP error from remote mailer after RCPT TO:<jmace(a)flash.net>: host vm6-ext.prodigy.net [207.115.63.80]: 550 5.1.1 <jmace(a)flash.net>... Addressee unknown ann1112(a)juno.com SMTP error from remote mailer after RCPT TO:<ann1112(a)juno.com>: host mx.boston.juno.com [64.136.25.17]: 550 ann1112(a)juno.com Account Inactive jmace(a)hushmail.com SMTP error from remote mailer after RCPT TO:<jmace(a)hushmail.com>: host smtp.hushmail.com [64.40.111.34]: 550 <jmace(a)hushmail.com>: User unknown jahangiri(a)att.net SMTP error from remote mailer after RCPT TO:<jahangiri(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <jahangiri(a)att.net> kat11182(a)att.net SMTP error from remote mailer after RCPT TO:<kat11182(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <kat11182(a)att.net> jmace86965(a)att.net SMTP error from remote mailer after RCPT TO:<jmace86965(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <jmace86965(a)att.net> jmace999(a)att.net SMTP error from remote mailer after RCPT TO:<jmace999(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <jmace999(a)att.net> jmace77181(a)att.net SMTP error from remote mailer after RCPT TO:<jmace77181(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <jmace77181(a)att.net> kat1118(a)att.net SMTP error from remote mailer after RCPT TO:<kat1118(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <kat1118(a)att.net> kat1118630(a)att.net SMTP error from remote mailer after RCPT TO:<kat1118630(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <kat1118630(a)att.net> laairman(a)att.net SMTP error from remote mailer after RCPT TO:<laairman(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <laairman(a)att.net> kat1118150(a)att.net SMTP error from remote mailer after RCPT TO:<kat1118150(a)att.net>: host gateway1.att.net [204.127.134.23]: 550 Invalid recipient: <kat1118150(a)att.net> ------ This is a copy of the message, including all the headers. ------

1 0

Re: Ross's TCPA paper
by Ross Anderson 25 Jun '02

25 Jun '02

> It's an interesting claim, but there is only one small problem. > Neither Ross Anderson nor Lucky Green offers any evidence that the TCPA > (http://www.trustedcomputing.org) is being designed for the support of > digital rights management (DRM) applications. Microsoft admits it: http://www.msnbc.com/news/770511.asp Intel admitted it to me to. They said that the reason for TCPA was that their company makes most of its money from the PC microprocessor; they have most of the market; so to grow the company they need to grow the overall market for PCs; that means making sure the PC is the hub of the future home network; and if entertainment's the killer app, and DRM is the key technology for entertainment, then the PC must do DRM. Now here's another aspect of TCPA. You can use it to defeat the GPL. During my investigations into TCPA, I learned that HP has started a development program to produce a TCPA-compliant version of GNU/linux. I couldn't figure out how they planned to make money out of this. On Thursday, at the Open Source Software Economics conference, I figured out how they might. Making a TCPA-compliant version of GNU/linux (or Apache, or whatever) will mean tidying up the code and removing whatever features conflict with the TCPA security policy. The company will then submit the pruned code to an evaluator, together with a mass of documentation for the work that's been done, including a whole lot of analyses showing, for example, that you can't get root by a buffer overflow. The business model, I believe, is this. HP will not dispute that the resulting `pruned code' is covered by the GPL. You will be able to download it, compile it, check it against the binary, and do what you like with it. However, to make it into TCPA-linux, to run it on a TCPA-enabled machine in privileged mode, you need more than the code. You need a valid signature on the binary, plus a cert to use the TCPA PKI. That will cost you money (if not at first, then eventually). Anyone will be free to make modifications to the pruned code, but in the absence of a signature the resulting O/S won't enable users to access TCPA features. It will of course be open to competitors to try to re-do the evaluation effort for enhanced versions of the pruned code, but that will cost money; six figures at least. There will likely be little motive for commercial competitors to do it, as HP will have the first mover advantages and will be able to undercut them on price. There will also be little incentive for philanthropists to do it, as the resulting product would not really be a GPL version of a TCPA operating system, but a proprietary operating system that the philanthropist could give away free. (There are still issues about who would pay for use of the PKI that hands out user certs.) The need to go through evaluation with each change is completely incompatible with the business model of free and open source software. People believed that the GPL made it impossible for a company to come along and steal code that was the result of community effort. That may have been the case so long as the processor was open, and anyone could access supervisor mode. But TCPA changes that completely. Once the majority of PCs on the market are TCPA-enabled, the GPL won't work as intended any more. There has never been anything to stop people selling complementary products and services to GPL'ed code; once the functioning of these products can be tied to a signature on the binary, the model breaks. Can anyone from HP comment on whether this is actually their plan? Ross

4 3

Life Insurance Price Wars
by Mariana Patel 25 Jun '02

25 Jun '02

1 0

Re: Fwd: Re: Fwd: Book Review: Peter Wayner's "Translucent Databases"
by R. A. Hettinga 25 Jun '02

25 Jun '02

At 7:52 PM -0700 on 6/24/02, Somebody wrote: > Uh, come on, Bob. If the original message is sent to a certain list, there > is no reason to forward it without comment to that same certain list. Damn. Got cryptography confused with cypherpunks. My mistake. Sorry about that. Cheers, RAH -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0

Penis Growth
by Diane Balfour 25 Jun '02

25 Jun '02

1 0

Norway Public Announcement (fwd)
by Jim Choate 25 Jun '02

25 Jun '02

---------- Forwarded message ---------- Date: Tue, 25 Jun 2002 07:44:10 -0400 From: PA List Manager <statelists(a)STATE.GOV> To: DOSTRAVEL(a)LISTS.STATE.GOV Subject: Norway Public Announcement Norway Public Announcement U.S. DEPARTMENT OF STATE Office of the Spokesman June 21, 2002 This Public Announcement is being issued to alert Americans traveling and resident in Norway of the potential for disruptions caused by demonstrations planned to coincide with the World Bank Conference to be held in Oslo from June 24-26, 2002. This Public Announcement will expire on June 30, 2002. The World Bank's Annual Bank Conference on Development Economics - Europe (ABCDE-Europe) is scheduled to take place in Oslo, Norway from June 24-26, 2002. Tight security will be in place in and around the venue for the conference (Holmenkollen area of Oslo). Previous summits in other capitals have drawn "anti-globalization" and other activists from around the world, and U.S. citizens should bear in mind that anti-globalization demonstrations in other European cities have sometimes turned violent. Demonstrations and protest marches are expected in downtown Oslo from June 22 through June 26. Travelers are advised to follow news and traffic reports, avoid crowds and demonstrations and to exercise caution. Travelers should be aware of heightened security and potential delays in entering Norway during this period and should always carry proof of identity and citizenship. Police intend to temporarily close access to some downtown train stations in connection with approved demonstrations and will forbid parking in the city center throughout the summit period. In addition, public transportation schedules may be altered. These temporary actions will be posted through the local media. The U.S. Embassy is located at Drammensveien 18, Oslo. The Embassy may be contacted 24 hours a day at telephone (47) 2244-8550 in connection with emergencies such as arrest, serious injury or death of a U.S. citizen. The American Citizen Services Unit is open for routine, non-emergency matters from 9:00 a.m. - 12:00 noon, Monday through Friday. For more information on travel to Norway, please consult the latest Department of State Consular Information Sheet for Norway at http:\\travel.state.gov. Americans traveling and residing abroad should monitor this web site closely, particularly the Department's Worldwide Caution-Public Announcement of March 17, 2002. This Public Announcement will expire on June 30, 2002. *********************************************************** See http://travel.state.gov/travel_warnings.html for State Department Travel Warnings ************************************************************ To change your subscription, go to http://www.state.gov/www/listservs_cms.html

1 0

Protection du littoral
by Daniel Lollichon 25 Jun '02

25 Jun '02

Bonjour, Je me permet de vous adresser cette e-mail en raison de votre intérêt pour nos côtes. Aujourdhui notre littoral est en danger. Je vous invite à soutenir sa protection en vous rendant sur le site : <http://perso.wanadoo.fr/protection_littoral> Davance merci Cordialement, Estelle

1 0

STOP Muscle & Joint Pain NOW!
by thermoflownow.com 25 Jun '02

25 Jun '02

1 0