May be a bit more complex - as the reverse lookups shown in the traceroute have subtle differences (including case). One would wonder if there is also some split DNS as well.
Dw.
.. feedback loop allows TCP [to run][ congestion avoidance: If acks return at a slower rate than the data was sent out,
that indicates that there is little bandwidth available, and the source throttles...
which does seem to be a far cry from TCP. While common lore (and the modern buffer bloated internet) has it that high RTT means little available bandwidth (and it sure does play havoc with the bandwidth product - giving rise to that lore fairly) - the design calls for packet drop rather than delay to indicate a link being overloaded. And while the source slows down - it does not actually throttles; it just awaits the ack - it wont slow down the next packets. It is just that the window won't grow further. So makes one think of the observations in RFC-2488.
And there is also the expectation of "But the IETF document still plays a subordinate role to that source code.'' in the original article.
However one interesting expectation or requirement of IETF standards is that one expects at least one, ideally two, independent implementations based on the written spec. This would alleviate the concerns that the VP8 case is too leading - as one has now an example of an independently derived code base - which has taken the written spec as its lead - and secondly it would also give the community a very fair idea as to any residual IPR issues, by Google or by others.
Thanks,
Dw.
Most modern (even the low end) registers allow for saving the transactions to a memory card, or can be polled (or can act as a 'stupid termina' when wired up -- but that requires a lot more software).
The low end units typically store the output as ascii; very akin to the format you find on the paper tape; i.e. as would be written to the printer (at the end of the day, or as a carbon copy).
Some, e.g. Sharp, have a more readily parsed format, basically CSV, which is easier to handle - or can even do html!. Keywords to search for (with the latter vendor) are SDW; or in general 'in-line' support.
At the very extreme end - consider a POS application (or perhaps even http://www.checkoutapp.com/) with just a cash-drawer, a printer and no till at all. These are generally 'unlocked' easily and a lot of have a simple printerport connection to which you can send an 'esc' 'O' command -- akin to the old EPSON FX-80 era world.
Dw.
Check out Wireless Leiden; an all volunteer, all community, all donation based free (as in beer) wireless network; covering an area with some 500.000 inhabitants; its FreeBSD based, under a BSD-ish licensen and both code and config tools can be checked out of SVN right away.
So - all of you; stop talking, grab the code and compete who is next !
:-)
Dw.
I love the backdoor in MacOS X - it has its use
on
No Backdoor in Vista
·
· Score: 4, Informative
MacOS X, with filefault*, creates a backdoor by means of a certificate. If you then safe the RSA key pair from your Keychain on a separate machine - you yourself or corperate IT can then be easily ensured access in case of some-one beeing hit by a bus; or in case of a total OS crash.
Dw.
Ad *) Or manually
# on a safe machine openssl req -new -x509 -out backup.cer -outform DER -nodes cp privkey.pem backup.cer/safeplace srm privkey.pem # copy public cert to laptop or wherever.. hdiutil create -encryption -type SPARSE -fs HFS+ -volname secure -size 5G -certificate backup.cer sec
Skype's encryption is closed source and prone to man-in-the-middle attacks. true - one has no cyptographic assurance that there is no MITM with Skype
Note that this report addresses that specifically and has been discussed at length at the various crypto mailing lists:
This evaluation report (PGP signature file) provides a detailed review of the security framework that is incorporated into Skype products. Skype provides its users with protections against a wide range of possible attacks, such as impersonation, eavesdropping and modification of data while in transit. This report describes the protective mechanisms that are in use throughout the Skype infrastructure as well as the general security policy that defines the basis for all designs within Skype's operational framework.
So if one is willing to a) trust Tom Berson and b) willing to trust Skype that they actually ship and do what they showed to Tom Berson - then you have some level of assurance.
If you have a few spare minutes; browsing the code is actually worth your time.
Compared to similar code in, say, FreeBSD, (take the USB code or the BT) it is interesting how much more detail and perfection is possible when the author of the code has 100% insight in the actual hardware. Gone are all the fiddles and the magic '#defines' - instead it actually tells you the why. Imagine a ethernet vendor or wifi card vendor doing the same!
But here's a question for you. If you're required to give "any other recipients of the Work or Derivative Works a copy of this License", does that mean that the extended work has to be under this license? Or does it just mean you have to give the license to them, even though it isn't applicable.
It means exactly what it says (see the original; the above suffers from crcual typo's) - you must pass on the license (which include the important disclaimers) along and as it pertains to the agrement under which you got the apache code under - but that does not mean that it applies in a contaminating sense to your own code, code you have added, nor does it mean you have to provide soure or certain licenses pertaining your own work along as wel further downstream.
This is not the same as making a contribution back to the ASF, which is what most of the license is about; and in that case it gets a bit more complex; and you specifically need to take patents into account as well.
his complains are actually about the LSB test suit
And simply working to gether to fix that testsuite may be a more pragmatic way of fixing things. The LSB organisation has been open to feedback, is fixing things and is, like all these organisation, resource contrainted. Exactly the sort of thing open source volunteers are so excelent at helping overcome. Especially those employed by companies, like Ulrich his employer, who really want LSB certification.
And linux desperately needs LSB. At the very least. And in in my daily job I am clamouring for more!
Right now we are seeing binary packag installers check for stdint.h so they it can guess that the right version of some libraries is in a different place - just so it works across RHES, Fedora, Suse and Debian. Not nice.
While I can see the fear, uncertainty and doubt with respect how big-evil co would use this - think about it from a technology perspective for a moment.
What we're getting here is an on board tamperproof(ish) crypto processor.
Exactly the thing you always wanted to safely put your ssh keys into, to have your X509 cert tied to, to lock your own VPN's into. And because it is not some separate chip card - and relatively fast compared to that - it propably can be used in much more secure modes; voiding the need to have things like passwords or unencrypted private keys in memory.
And one worry less for when things get stolen or taken over.
Given a few bright hackers won't be long before openssl, firefox and what get augmented with this chip as their storage areas.
And the result is rather the opposite; a long list of companies emerged as a direct result of that: AnyWi, Gandalf, Wido and half a dozen others. Making Leiden and the direct region something of a WiFi focal point.
I would not call that effect "stiffling"... the only few people stiffed may be some big incumbents which where to slow to move.
But again - like the last vote - the parliament stops short of ordering the cabinet; it merely request nicely that should things be brough up for the agenda it should abstain from supporting the item. Althouhg this time the parliament is equesting such - last time round, a few months ago, it merely asked. So some improvement:-)
But this is still a far cry from a parliament which tells it minister to vote no (and promises to kick the cabinet out if they does otherwise). And given the past (and the voting lines) one could well imagine some politicians voting yes to be polular - while working behind the scene to make clear to the cabinet that should they sail a different line - they have the coalitions suport anyway.
Yes it was - see the
Derby project in the Incubator.
Beeing in the incubator does not yet mean it is a full blown ASF project - but that the ASF is in the process of ensuring that there is a healthy community around it, that all the legal paperwork, trademakrs, grants, copyrights and other interlectual rights are sorted out, that commiter license agreements are on file for each developer, etc, etc..
Once that is all in place (and getting a healthy long term community is hardest - the rest is just endless grunt work and digging through code and legal paperwork dotting i's and crossing t's) it'll leave the incubator and be a full blown process.
Just hop on a plane to LasVegas - We're having the ApacheCon (http://www.apachecon.com) this week - with at least half a dozen tail on that topic (in the httpd, java, perl and php fields). Though the more hands on oriented tutorials will already start today -:-)
A good alternative is the book by OReilly - Web Performance Tuning (http://www.website-owner.com/books/servers/webtun ing.asp).
http://www.wirelessleiden.nl/english/ is well in the lead with over 50 nodes (not just hotspots) on churches, schools, offices and other tall buildings:-) And all open source to boot (fetch yours at http://wleiden.webweaving.org:8080/svn/node-config ) or persue the configuration http://www.wleiden.net/cgi-bin/g_list.pl and actual status: http://uuu.wirelessleiden.nl/nodemap.jpg.
Well - As you can see on the map it covers not just the City of Leiden - but has also spawned copy cat initiatives which are building out in the adjacent villages - all the way till the sea.
Dw.
Apache group is so adamant about dismissing user-submitted patches
I'd hate to dispell the lore - but the web server is in fact largely build from quality checked and polished versions of those submitted patches. Sure - a patch which fixes 1 thing and breaks 3 others; or optimizes for one rare case at the expense for 2 common cases may need some work - but over those 8 years very few patches and suggestions have gone to waste. If they where good they typically pop up at some point later if they where too radical at the time of first posting.
Soo keep them coming !
Dw.
Re:Germany has a sense of humor
on
Germany Muzzles SCO
·
· Score: 5, Informative
It is a bit more subtle; going back to the german version it says that as "Univention" essentially represent all, -except- for those with whom SCO has a direct relationship, the ruling affects all but those. So SCO can do with its -own- customer what it wants; it just should not mess with "Univentions" their customers.
Note that it is not just sue - but "Strafverfolgung"; i.e. a criminal offence reported to the "attorney general" which the "people' bring on, rather than a civil law case.
Slashdot Mirror
May be a bit more complex - as the reverse lookups shown in the traceroute have subtle differences (including case). One would wonder if there is also some split DNS as well. Dw.
which does seem to be a far cry from TCP. While common lore (and the modern buffer bloated internet) has it that high RTT means little available bandwidth (and it sure does play havoc with the bandwidth product - giving rise to that lore fairly) - the design calls for packet drop rather than delay to indicate a link being overloaded. And while the source slows down - it does not actually throttles; it just awaits the ack - it wont slow down the next packets. It is just that the window won't grow further. So makes one think of the observations in RFC-2488.
And there is also the expectation of "But the IETF document still plays a subordinate role to that source code.'' in the original article. However one interesting expectation or requirement of IETF standards is that one expects at least one, ideally two, independent implementations based on the written spec. This would alleviate the concerns that the VP8 case is too leading - as one has now an example of an independently derived code base - which has taken the written spec as its lead - and secondly it would also give the community a very fair idea as to any residual IPR issues, by Google or by others. Thanks, Dw.
Most modern (even the low end) registers allow for saving the transactions to a memory card, or can be polled (or can act as a 'stupid termina' when wired up -- but that requires a lot more software). The low end units typically store the output as ascii; very akin to the format you find on the paper tape; i.e. as would be written to the printer (at the end of the day, or as a carbon copy). Some, e.g. Sharp, have a more readily parsed format, basically CSV, which is easier to handle - or can even do html!. Keywords to search for (with the latter vendor) are SDW; or in general 'in-line' support. At the very extreme end - consider a POS application (or perhaps even http://www.checkoutapp.com/) with just a cash-drawer, a printer and no till at all. These are generally 'unlocked' easily and a lot of have a simple printerport connection to which you can send an 'esc' 'O' command -- akin to the old EPSON FX-80 era world. Dw.
Works swimmingly well on an EDVO modem stuck into an IBM ThinkPad in New York City. Dw.
Another reason why you really really need svn obliterate !
Dw
So - all of you; stop talking, grab the code and compete who is next !
Dw.
Dw.
Ad *) Or manually
So if one is willing to a) trust Tom Berson and b) willing to trust Skype that they actually ship and do what they showed to Tom Berson - then you have some level of assurance.
Dw.
Compared to similar code in, say, FreeBSD, (take the USB code or the BT) it is interesting how much more detail and perfection is possible when the author of the code has 100% insight in the actual hardware. Gone are all the fiddles and the magic '#defines' - instead it actually tells you the why. Imagine a ethernet vendor or wifi card vendor doing the same!
Dw
And linux desperately needs LSB. At the very least. And in in my daily job I am clamouring for more!
Right now we are seeing binary packag installers check for stdint.h so they it can guess that the right version of some libraries is in a different place - just so it works across RHES, Fedora, Suse and Debian. Not nice.
Dw
3 Dollar a gallon -- how about 3 euro a Litre !
Dw
What we're getting here is an on board tamperproof(ish) crypto processor.
Exactly the thing you always wanted to safely put your ssh keys into, to have your X509 cert tied to, to lock your own VPN's into. And because it is not some separate chip card - and relatively fast compared to that - it propably can be used in much more secure modes; voiding the need to have things like passwords or unencrypted private keys in memory.
And one worry less for when things get stolen or taken over.
Given a few bright hackers won't be long before openssl, firefox and what get augmented with this chip as their storage areas.
Dw
This machine is indeed a heavy duty HP/red-hat linux server used for ensuring good support on that platform.
Dw.
And the result is rather the opposite; a long list of companies emerged as a direct result of that: AnyWi, Gandalf, Wido and half a dozen others. Making Leiden and the direct region something of a WiFi focal point.
I would not call that effect "stiffling"... the only few people stiffed may be some big incumbents which where to slow to move.
Dw
But again - like the last vote - the parliament stops short of ordering the cabinet; it merely request nicely that should things be brough up for the agenda it should abstain from supporting the item. Althouhg this time the parliament is equesting such - last time round, a few months ago, it merely asked. So some improvement :-)
But this is still a far cry from a parliament which tells it minister to vote no (and promises to kick the cabinet out if they does otherwise). And given the past (and the voting lines) one could well imagine some politicians voting yes to be polular - while working behind the scene to make clear to the cabinet that should they sail a different line - they have the coalitions suport anyway.
Shame,
Dw.
Beeing in the incubator does not yet mean it is a full blown ASF project - but that the ASF is in the process of ensuring that there is a healthy community around it, that all the legal paperwork, trademakrs, grants, copyrights and other interlectual rights are sorted out, that commiter license agreements are on file for each developer, etc, etc..
Once that is all in place (and getting a healthy long term community is hardest - the rest is just endless grunt work and digging through code and legal paperwork dotting i's and crossing t's) it'll leave the incubator and be a full blown process.
Feel invited to join and make this happen ;-)
Dw.
In the print versions sold locally (e..g in the HCC magazine) it is even more obvious as you see the whole machine.
Dw.
A good alternative is the book by OReilly - Web Performance Tuning (http://www.website-owner.com/books/servers/webtun ing.asp).
Dw.
Right - but that is just the standard which described the card; not the actual card itself.
http://www.wirelessleiden.nl/english/ is well in the lead with over 50 nodes (not just hotspots) on churches, schools, offices and other tall buildings :-) And all open source to boot (fetch yours at http://wleiden.webweaving.org:8080/svn/node-config ) or persue the configuration http://www.wleiden.net/cgi-bin/g_list.pl and actual status: http://uuu.wirelessleiden.nl/nodemap.jpg.
Dw.
Well - As you can see on the map it covers not just the City of Leiden - but has also spawned copy cat initiatives which are building out in the adjacent villages - all the way till the sea. Dw.
I'd hate to dispell the lore - but the web server is in fact largely build from quality checked and polished versions of those submitted patches. Sure - a patch which fixes 1 thing and breaks 3 others; or optimizes for one rare case at the expense for 2 common cases may need some work - but over those 8 years very few patches and suggestions have gone to waste. If they where good they typically pop up at some point later if they where too radical at the time of first posting.
Soo keep them coming !
Dw.
It is a bit more subtle; going back to the german version it says that as "Univention" essentially represent all, -except- for those with whom SCO has a direct relationship, the ruling affects all but those. So SCO can do with its -own- customer what it wants; it just should not mess with "Univentions" their customers.
Note that it is not just sue - but "Strafverfolgung"; i.e. a criminal offence reported to the "attorney general" which the "people' bring on, rather than a civil law case.
Dw