Ma dai - who cares.. except for the fact as a proofpoint about it being well engineered - and that I care about. Feast for the eyes, feast for the hands: tool-less disassembly; the inner box slides out of its enclosure (forget those crappy folding'arm' things which always snip at your cables) - tool-less idiot proof swapping of most components. And virtually impossible to mount things upside down or otherwise wrong. That is where the good looks come in.
Good Design - a joy to work with;-)
And somehow that translates in a better bottom line for the buyer.
See for example www.opentap.org. Since August 2000 internet providers had to comply. The original standard JTS ( Justitiële Tap Standaard) was outdated; the ETSI standard (which oasis does build on) back then does not meet the requiremetns of the netherlands (google 'RapportageTWRT' if you can read dutch); a temporary system was instated for the time being (see SC/28/02/2000; again, in dutch only). What is interesting is that this is a mix between intelligence (which generally does not get to be used (or is usable) in a court against anyone) and the more real information gaterhed by the police authoritys for further criminal actions.
Dw
Re:The write-up is misleading
on
Cross-Site-TRACE
·
· Score: 3, Informative
Or in more detail; TRACE simply echos back wath the client send to the server; i.e. what the client fundamentally already *knows*. The server reveals nothing to the client than what it already knows; namely the request it just send.
It is just that on the client, to prevent cross side scripting, there is some sandboxing; which is now violated.
That is called cross site scripting.
bollocks - just another (IE) cross site vulnerabil
on
Cross-Site-TRACE
·
· Score: 3, Informative
That web server is just doing what it is supposed to do; it is the client which allows for the cross site vulnerability.
Alias/Foo/Music
<Directory/Users/Foo/Music>
allow from all ....
</Directory>
mod_rendezvous and apache; it is all in the config
on
Apple Smacks Down iCommune
·
· Score: 5, Insightful
Note that iCommune essentially used no code; it was just somethin which generated a few lines of apache config which would make the Music directory shared:
Alias/Foo/Music
Al.ow from all...
Along with a small perl/python script which took your playlist and turned it into a.pls file. I.e. the type you normally click on.
That is all. Any one who can handle vi can do it manually.
However, combine this with Eric his mod_rendevous and then it gets interesting... http://homepage.mac.com/macdomeeu/dev/current/mod_ rendezvous/
As that will dynamically announce your web server to the local network.
In Safari; just go to bookmarks, rendezvous - and here we go. Sharing as it should be.
While traveling in Europe I've never lost a message; though had them delayed for 2-15 minutes. And if you switch it on, in the phone, you reliable get delivered/non-delivered messages. The latter is useful if you have send an SMS with a 5 minute livetime and the person was on a plane or something.
Though I do admit that in San Francisco I've had regularly SMS messages not being delivered (and the sender getting a bounce); or delivered a day later when the phone switched provider.
An issue may be with outside contributions; such as a crucial bug fix. These are typically made on the GPL-ed version. Consequentely, and barring any AUP notices, the contributor may insist that these are made under those GPL terms. This may prohibit the entity which did the dual licensing to include that change in their second branch; which hat proprietary IP. And they they have though choise to deceide whether to open up that IP or not (assuming they can; often it is licensed from a third party). In mye experience that is where dual licencing runs afoul.
The mark was owned by DeerSoft, the license has nothing to do with that; nor does grant something like ownership of that mark to some community at large. Also note that the software up to this point has always been dual licensed; under the GPL and under the Perl Artistic License. The latter allows for considerable more freedom.
All reports seem to agree on the rough amounth of explosives which went up in smoke. The numbers are not insanely far off the actual amounth of explosives available in the ships, trains and on the pier.
Adding a 10+ kiloton nuclear device to the list would imply that there was a lot less conventional explosives present, at least a third. Which is hard to account for. Or that the conventional explosives did not give as big a bang due to burning first or other mitigational effects. Something well understood and accounted for at the time of the enquiries.
And giving me all the speed I need in pine. Which is the app I spend most of my time in.
On the TiBook things like a find / are noticable slow (like on any other laptop I have had) and are much more bearable on a desktop G4.
Command line apps are speedy. Servers, such as apache and in particular Java/Tomcat/Cocoon or Forrest are incredible speedy; and outperforms a Netra T1 with ease.
And yes; if you run word, powerpoint, iTunes, 15 terminals, OmniWeb, Internet Exploder, 2 instant messengers and what not - the screen gets to be a little sluggish. But then again - it does not throw a wobbly, and actually lets me use that much, unlike my W2k machine.
In fact - I'll usually stay up without a reboot for months (until I do something silly; like changing the battery without putting the machine in sleep mode).
If you check out: http://www.microsoft.com/technet/treeview/default. asp?url=/technet/security/issues/W2kCCUG/default.a sp and specifically the section 3.3; you'll see that its only a tad better than NT's orange book scam (which was certified as secure but only if not connected and in a locked room). This time - all the machines on the LAN need to be under the same security constraints; and that LAN of course stays in a locked down building. Or, since the days of NT, we've now gone from a locked room with one PC to a slightly larger locked room of PC's. Geez. Progress.
Ok, some Sparc Binaries and Libs crept in - but all and all - following the release notes; you'll have apache, tomcat, jdbc and a full Oracle 9i up and running inside the hour.
You are going to end up having bought both of them anyway. Just admit it; they are after your money, they know your weak spot and they are smarter than you are when it comes to hacking wallets.
Having considered the applicable law and the undisputed facts presented herein, he court concludes that paragraphs 3, 5, and 6 of the Inspection Procedures conflict with section 6334 and Art. V, 21 of the Bylaws by unreasonably restricting directors' access to corporate records and depriving directors of inspection rights afforded them by law.
Furthermore, Lynn's 10/5/01 letter violates both section 6334 and Bylaws Article V, Section 21 because it deprives Auerbach of the inspection rights he has under law and imposes such unreasonable requirements as having to sign a confidentiality agreement and having to pursue burdensome review in any effort to enforce his inspection rights.
Additionally, the Inspection Procedures here apparently have not even been adopted by the ICANN Board of Directors, but were promulgated by an ad hoc group of functionaries consisting of the Audit Committee, Louis Touton, Diane Schroeder, and Lynn (Auerbach Dec. Ex. 17, 18, 21).
Based on the undisputed facts, there is no triable issue as to any material fact and Petitioner Auerbach is entitled to judgment as a matter of law granting his Petition for Writ of Mandate.
The translations are lacking some crucial points. Essentially the judge is saying:
Hyperlinks are not illegal by them selves
But this information is ordered already
as out of bound. And the comments point
to them directly (hyperlink and verbal
explanation to get further).
The owner of site specifically reserved the
right to edit content.
So they where not
able to claim they had no control over
comments uploaded.
Thus they are told to do what they where
expected and are proven able to do with
reasonable cost.
Thus they are convicted of paying all costs.
The middle point is important - they reserved the right to edit themselves - and did so - so they cannot maintain they could not comply with the second point. N
Dw
If you are happy with any unix; both BSDi and SCO have long supported such things commercially.
Open source wise: I've found that a fair share of the printers are either normal postscript or basically accept old fashioned Epson FX80, MX80 or RX80 escape sequences. Some more modern printers do HP Deskjet.
In my experience they virtually ALL support some form of templating; whcih you set up once. And from thereon you pipe message to the printer like 'Name\nAddress\n' which are filled out in the right places. This also applies for the hard mag strip.
I've used the first method with LPR and ghostscript. The latter method is 'harder' - though LPR does support a lot of templating; I've always found it easier to write some custom code to directly send the raw data to LPR.
Dw
..and traditionally the only environment with legal resources adequate to deal with such liability has been the megalithic corporate one."
I'd challenge this a little; think of normal civil engineers (who often work on a consulting basis for small, even one person, shops), electrical engineers, steel construction engineers and a whole range of technical/craft jobs; such as carpenting, electrical wiring, etc - for which a license of sort is often required (profession examples taken from the US, the Netherlands, Italy and Germany and with the caveat that the word 'engineer' sometimes translates to different things,).
Free Speach or Free Beer
on
Debian And WineX
·
· Score: 3, Insightful
What is free ? Or rather who has that freedome ?
The ability to do -anything- with the code; whenever you want it; however you want it. Or in other words you and your actions are the thing that is free.
Or the ability of the code to distribute itself to wherever the code wants to go; and protection for the code to insure it does not get hidden away in obscure places.
BSD chooses the first as being important - at the expense of freedom of the code.
The GPL chooses the latter - at the expense of freedom for you.
And as with all things in live - reality is a compromize; one cannot have both. Companies and people who want their code to be used in the widest possible way generally pick the BSD code - and people who want their creations to have a robust live of their own - for eternity to come - and out of reach of commercialization - pick the GPL.
I added support for MacOS-X and FreeBSD - see http://webcam-osx.sourceforge.net to macam - using a generic CPiA as a basis. It is not quite trivial to get results comparable to the intel tool - but very doable: thanks to this document on the webcam source force page:
http://webcam.sourceforge.net/docs/qx3_cmd.pdf
Dw
One thing to clarify: your employer does not own everything you do by law - only by the contract you may have signed. Brief rant below.
Is not as applicable to most of Europe as it is to the US - where the law may actually stipulate a number of things which can not be overridden by an agreement. And this implies that in a lot of EU countries a company owns all your output/braincycles, be it at home, during your holidays or elsehwere, while full time employed - as soon as there is some overlap with your task at work.
After entering the US on a work permit - I got a Social Security Card. With it came a stern letter - which said that the card is for govt. use only - and not to be used for any but official purposes.
Just to make sure I got the point - it had the same thing stamped across the card in RED.
Sofar, so good - having lived in the Netherlands and Italy - where there is a similar SocialFicscal number or Codifice-Fiscale - I thoughd I understood.
Step 2 - rent a house, get a phone,... - Housing appartment: "Can we have your Social Security Number please ?". Me - eh - are you allowed to have that ? - it says on the card in read bold "for official use only".... quickly one finds out that it is not so much the governement but private industry which (ab)uses those numbers - and denies access to those who refuse or are unable to give it.
Interestingly enough - when asked by Govt. officials to provide the number - it turns out that this is not nearly as mandadatory - and that each and every circumstance, up to and including, that of employment, allows for the use of a one time ITTN or tax payer ID or other identification.
Comparing this with Europe and Asia - I see two big differences:
Private industry in the US (ab)uses those
numbers widely - and there is a strong incentive for consumers to comply. Europe and Asia have the opposite - non govt. entities are banned from using such indicators and from sharing them.
The governement seems to be able to do without when needed. Europe is the opposite.
There is no data act or other overall protection at all.
So when worrying about those ID cards - I'd ignore the US govt. - and I'd worry about the Abuse by the likes of D&B, credit-agencies etc. And I'd worry about the lack of legislation - and I'd rather ask for lots of legislation !
"..Infosecurity czar Richard Clarke said in his speech at RSA that Nimda cost US companies an estimated $2 billion."..
What he also did, which struck me as more interesting thant the dollar value, was draw a parallel with the early days of aviation.
And how the FAA stepped in as the authority to make things safe. Reluctantly perhaps at first - but much needed as the industry had made itselfs a mess.
Which is more than just a parallel - and might well be the much needed shot in front of the bow and Lima-Lima call this industry needs.
You can be averse of govt. regulation - and if you see the pain and stiffling the FAA imposes on the Aerospace industry - you will even more so. But they will, and are supposed (or at least expected by the people) to step in if things are not fixed and society as a whole is harmed. And that last part is hard to deny.
Perhaps the first sign of a stick. A stick which is much harder to dodge than, say, the DCMA or SCSS.
"Microsoft is granting the world a royalty-free, non-exclusive license to implement their Kerberos extension."
Hurray! But... It is jus the license and doc's for half of their extensions: the part which does group enumeration. Which was already understood anyway.
The real beef - i.e. the domain controller specifics - are still as closed as ever. And according to the presentation at the RSA conference last week - are going to remain so.
Congrat's to slashdot for picking it up just as the spinmeisters intended:-)
Slashdot Mirror
Good Design - a joy to work with ;-)
And somehow that translates in a better bottom line for the buyer.
Dw
It is just that on the client, to prevent cross side scripting, there is some sandboxing; which is now violated.
That is called cross site scripting.
http://www.apacheweek.com/issues/03-01-24
http://online.securityfocus.com/archive/1/30816
Have more details.
Alias
<Directory
allow from all
</Directory>
Note that iCommune essentially used no code; it was just somethin which generated a few lines of apache config which would make the Music directory shared:
/Foo/Music
...
.pls file. I.e. the type you normally click on.
_ rendezvous/
Alias
Al.ow from all
Along with a small perl/python script which took your playlist and turned it into a
That is all. Any one who can handle vi can do it manually.
However, combine this with Eric his mod_rendevous and then it gets interesting... http://homepage.mac.com/macdomeeu/dev/current/mod
As that will dynamically announce your web server to the local network.
In Safari; just go to bookmarks, rendezvous - and here we go. Sharing as it should be.
Dw.
Though I do admit that in San Francisco I've had regularly SMS messages not being delivered (and the sender getting a bounce); or delivered a day later when the phone switched provider.
An issue may be with outside contributions; such as a crucial bug fix. These are typically made on the GPL-ed version. Consequentely, and barring any AUP notices, the contributor may insist that these are made under those GPL terms. This may prohibit the entity which did the dual licensing to include that change in their second branch; which hat proprietary IP. And they they have though choise to deceide whether to open up that IP or not (assuming they can; often it is licensed from a third party). In mye experience that is where dual licencing runs afoul.
The mark was owned by DeerSoft, the license has nothing to do with that; nor does grant something like ownership of that mark to some community at large. Also note that the software up to this point has always been dual licensed; under the GPL and under the Perl Artistic License. The latter allows for considerable more freedom.
Adding a 10+ kiloton nuclear device to the list would imply that there was a lot less conventional explosives present, at least a third. Which is hard to account for. Or that the conventional explosives did not give as big a bang due to burning first or other mitigational effects. Something well understood and accounted for at the time of the enquiries.
Not a strong case.
On the TiBook things like a find / are noticable slow (like on any other laptop I have had) and are much more bearable on a desktop G4.
Command line apps are speedy. Servers, such as apache and in particular Java/Tomcat/Cocoon or Forrest are incredible speedy; and outperforms a Netra T1 with ease.
And yes; if you run word, powerpoint, iTunes, 15 terminals, OmniWeb, Internet Exploder, 2 instant messengers and what not - the screen gets to be a little sluggish. But then again - it does not throw a wobbly, and actually lets me use that much, unlike my W2k machine.
In fact - I'll usually stay up without a reboot for months (until I do something silly; like changing the battery without putting the machine in sleep mode).
If you check out: http://www.microsoft.com/technet/treeview/default. asp?url=/technet/security/issues/W2kCCUG/default.a sp and specifically the section 3.3; you'll see that its only a tad better than NT's orange book scam (which was certified as secure but only if not connected and in a locked room). This time - all the machines on the LAN need to be under the same security constraints; and that LAN of course stays in a locked down building. Or, since the days of NT, we've now gone from a locked room with one PC to a slightly larger locked room of PC's. Geez. Progress.
Best oracle Beta I've seen in a long time.
It just works !
both of them anyway. Just admit it; they
are after your money, they know your weak spot and they are smarter than you are when it comes to hacking wallets.
Dw
- Having considered the applicable law and the undisputed facts presented herein, he court concludes that paragraphs 3, 5, and 6 of the Inspection Procedures conflict with section 6334 and Art. V, 21 of the Bylaws by unreasonably restricting directors' access to corporate records and depriving directors of inspection rights afforded them by law.
- Furthermore, Lynn's 10/5/01 letter violates both section 6334 and Bylaws Article V, Section 21 because it deprives Auerbach of the inspection rights he has under law and imposes such unreasonable requirements as having to sign a confidentiality agreement and having to pursue burdensome review in any effort to enforce his inspection rights.
- Additionally, the Inspection Procedures here apparently have not even been adopted by the ICANN Board of Directors, but were promulgated by an ad hoc group of functionaries consisting of the Audit Committee, Louis Touton, Diane Schroeder, and Lynn (Auerbach Dec. Ex. 17, 18, 21).
- Based on the undisputed facts, there is no triable issue as to any material fact and Petitioner Auerbach is entitled to judgment as a matter of law granting his Petition for Writ of Mandate.
I'd say - that is clear.- Hyperlinks are not illegal by them selves
- But this information is ordered already
as out of bound. And the comments point
to them directly (hyperlink and verbal
explanation to get further).
- The owner of site specifically reserved the
right to edit content.
- So they where not
able to claim they had no control over
comments uploaded.
- Thus they are told to do what they where
expected and are proven able to do with
reasonable cost.
- Thus they are convicted of paying all costs.
The middle point is important - they reserved the right to edit themselves - and did so - so they cannot maintain they could not comply with the second point. N DwIf you are happy with any unix; both BSDi and SCO have long supported such things commercially. Open source wise: I've found that a fair share of the printers are either normal postscript or basically accept old fashioned Epson FX80, MX80 or RX80 escape sequences. Some more modern printers do HP Deskjet. In my experience they virtually ALL support some form of templating; whcih you set up once. And from thereon you pipe message to the printer like 'Name\nAddress\n' which are filled out in the right places. This also applies for the hard mag strip. I've used the first method with LPR and ghostscript. The latter method is 'harder' - though LPR does support a lot of templating; I've always found it easier to write some custom code to directly send the raw data to LPR. Dw
The ability to do -anything- with the code; whenever you want it; however you want it. Or in other words you and your actions are the thing that is free.
Or the ability of the code to distribute itself to wherever the code wants to go; and protection for the code to insure it does not get hidden away in obscure places.
BSD chooses the first as being important - at the expense of freedom of the code.
The GPL chooses the latter - at the expense of freedom for you.
And as with all things in live - reality is a compromize; one cannot have both. Companies and people who want their code to be used in the widest possible way generally pick the BSD code - and people who want their creations to have a robust live of their own - for eternity to come - and out of reach of commercialization - pick the GPL.
Dw.
I added support for MacOS-X and FreeBSD - see http://webcam-osx.sourceforge.net to macam - using a generic CPiA as a basis. It is not quite trivial to get results comparable to the intel tool - but very doable: thanks to this document on the webcam source force page: http://webcam.sourceforge.net/docs/qx3_cmd.pdf Dw
Use the stuff you use to remove scratches from a CD, cellphone screen. It is basically a gentle polish.
Just to make sure I got the point - it had the same thing stamped across the card in RED.
Sofar, so good - having lived in the Netherlands and Italy - where there is a similar SocialFicscal number or Codifice-Fiscale - I thoughd I understood.
Step 2 - rent a house, get a phone, ... - Housing appartment: "Can we have your Social Security Number please ?". Me - eh - are you allowed to have that ? - it says on the card in read bold "for official use only".... quickly one finds out that it is not so much the governement but private industry which (ab)uses those numbers - and denies access to those who refuse or are unable to give it.
Interestingly enough - when asked by Govt. officials to provide the number - it turns out that this is not nearly as mandadatory - and that each and every circumstance, up to and including, that of employment, allows for the use of a one time ITTN or tax payer ID or other identification.
Comparing this with Europe and Asia - I see two big differences:
- Private industry in the US (ab)uses those
numbers widely - and there is a strong incentive for consumers to comply. Europe and Asia have the opposite - non govt. entities are banned from using such indicators and from sharing them.
- The governement seems to be able to do without when needed. Europe is the opposite.
- There is no data act or other overall protection at all.
So when worrying about those ID cards - I'd ignore the US govt. - and I'd worry about the Abuse by the likes of D&B, credit-agencies etc. And I'd worry about the lack of legislation - and I'd rather ask for lots of legislation !What he also did, which struck me as more interesting thant the dollar value, was draw a parallel with the early days of aviation.
And how the FAA stepped in as the authority to make things safe. Reluctantly perhaps at first - but much needed as the industry had made itselfs a mess.
Which is more than just a parallel - and might well be the much needed shot in front of the bow and Lima-Lima call this industry needs.
You can be averse of govt. regulation - and if you see the pain and stiffling the FAA imposes on the Aerospace industry - you will even more so. But they will, and are supposed (or at least expected by the people) to step in if things are not fixed and society as a whole is harmed. And that last part is hard to deny.
Perhaps the first sign of a stick. A stick which is much harder to dodge than, say, the DCMA or SCSS.
Hurray! But... It is jus the license and doc's for half of their extensions: the part which does group enumeration. Which was already understood anyway.
The real beef - i.e. the domain controller specifics - are still as closed as ever. And according to the presentation at the RSA conference last week - are going to remain so.
Congrat's to slashdot for picking it up just as the spinmeisters intended :-)
Dw.