<?xml version="1.0" encoding="iso-8859-2"?>
<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/">
<channel>
<title>Mara's weblog</title>
<link>http://ksiezyc.net/blogen/</link>
<description>Comments, opinions, whatever...</description>
<dc:language>en-us</dc:language>
<dc:creator>Mara</dc:creator>
<dc:date>2007-07-22T20:35:46+02:00</dc:date>
<admin:generatorAgent rdf:resource="http://nanoblogger.sourceforge.net" />
<item>
<link>http://ksiezyc.net/blogen//archives/2007/07/22/T20_35_28/</link>
<title>Silent Linux adoption</title>
<dc:date>2007-07-22T20:35:28+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Science and technology</dc:subject>
<description>
<![CDATA[<p>With the desktop Linux adoption rate steady in the statistics and
flamewars (and sometimes discussions) about the reasons, the real rate
passes nearly unnoticed. What am I writing about? Embedded devices. A high
percentage (of not the majority) of consumer-range DVD players run Linux.
And what about small routers connected to the cable modems (or ones
including the cable modem functionality)? They're also running Linux. It's
not that rare to have two or more Linux devices at home. With or without
knowing.</p>
<p>How does it affect the Linux desktop market? It seems that it doesn't.
Directly, that's probably true. Indirectly, however, desktop Linux machines
often use the same elements embedded Linux devices do. It can mean drivers
available. Or, at least, specifications. I have already noticed that there
have been less and less driver-related Linux problems. A newbie usually can
find all drivers for his/her hardware. If it's not included by default, of
course. There are other reasons of the faster avalibility of different
drivers, but the rate of 'hidden' Linux devices plays its' role here.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2007/04/29/T21_29_07/</link>
<title>Economist on DRM; IP Criminal Measures directive</title>
<dc:date>2007-04-29T21:29:07+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Science and technology</dc:subject>
<description>
<![CDATA[<p> The Economist has a balanced editorial on <a
href="http://www.economist.com/daily/columns/techview/displaystory.cfm?story_id=9096421&fsrc=nwl">why
DRM doesn't work</a> from (mostly) consumer's point of view.</p>
<p>But, more or less at the same time we also have the <a
href="http://press.ffii.org/Press_releases/European_Parliament_Criminalises_Businesses%2C_Consumers%2C_Innovators">IP
Criminal Measures directive</a>. What has IP infringement with terrorism?
Hard to tell. In the meantime it makes 'commercial scale infringements' of IP rights a criminal
offence. FFII reports that many things are not clear at all.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2007/04/15/T17_40_32/</link>
<title>New Debian stable</title>
<dc:date>2007-04-15T17:40:32+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Software</dc:subject>
<description>
<![CDATA[<p>Etch is now <a
href="http://lists.debian.org/debian-announce/debian-announce-2007/msg00002.html">Debian
stable</a>. One of the most important additions is an official AMD64
support. The webpage is not up-to-data in certain parts, however, like the
port descriptions, for instance <a
href="http://www.us.debian.org/ports/arm/">ARM port</a> which is still about
plans for Etch...</p>
<p>Still, normal users (not server administrators) should rather choose
lenny/sid.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2007/03/18/T20_56_43/</link>
<title>Selling user data</title>
<dc:date>2007-03-18T20:56:43+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security</dc:subject>
<description>
<![CDATA[<p>It's not a secret that if you're an researcher, you can get ISP
traffic for your research. It is (or at least should be) anonymized,
however.</p>
<p>It has been revealed recently that <a
href="http://arstechnica.com/news.ars/post/20070315-your-isp-may-be-selling-your-web-clicks.html">data
about user traffic is also sold</a> (check also <a
href="http://internet.seekingalpha.com/article/29449">here</a>). It looks it
was about US market. Is it the same in EU? I guess the answer is yes.</p>
<p>Suprise? Rather not. What's more, the thing is rather not regulated in
most countries, there's also nothing about that when you subscribe for your
Net access. It seems logical. Website-based tools do not give very acurate
results, because you can deal with them using Adblock and such things. The
request that come from your machine... That's another source for analysis
and a very good one.</p>
<p>Then we come to EU data retention, which does look like a distant
subject, but it is not. What is the data to be stored under the retention
law? The same thing that I think is sold (probably in slightly more aggregated
form). That rises an concern about the use of the stored data. Having it on
the disks will make it much easier to sell in huge volumes and also run
certain data mining techniques and then sell the results. With or without
notifying the users. Legally or not. With such amount of data (in Poland the
project has 5 years of mandatory data storage, when EU max is 2 years) it's
easy to imagine that the data will leak. What we currently have may be just
a start of that.</p>
<p>Should the users be notified that their habbits, even websites they visit
are (or will be) monitored? I think they should. Clearly notified.</p>
<p>The defence is encryption. Unfortunately not so many sites support
it (banks and financial institutions are exceptions here). Also,
there are sites where passwords fly unencrypted, sometimes even clearly in
the URL line. Trying not to use sites without even basic security is quite
hard. Every unencrypted action (most of web browsing, many IM messages, emails etc)
just travel the Net in plaintext. Are you aware of that?</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2007/03/02/T22_39_56/</link>
<title>DRM: a few years earlier</title>
<dc:date>2007-03-02T22:39:56+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security, Software</dc:subject>
<description>
<![CDATA[<p>I trace the change of atmosphere around <a
href="http://en.wikipedia.org/wiki/Digital_Rights_Management">DRM</a> (and I
don't write about FLOSS-related websites here, they have <a
href="http://www.defectivebydesign.org/">unchanged opinion</a> since the
appearance of the whole thing). Not more than a year ago I thought that
DRM-like solutions will be finally implemented and the user would have no
choice different from not buying the equipment at all.</p>

<p>And now? Jobs writes <a
href="http://www.apple.com/hotnews/thoughtsonmusic/">against DRM</a>, in
fact. That caused <a
href="http://news.com.com/2100-1027_3-6162729.html?part=rss&amp;tag=2547-1_3-0-5&amp;subj=news">criticism</a>
from the media industry, of course. The question, about the costs and
benefits of DRM and if it makes sense to implement it at all, has appeared
in the places I have not expected. That's definitely positive.</p>

<p>The context of the media-related discussion is the ease to crack HD DVD
and Blu-Ray. That issue is a clear example of one major vulnerability the
systems have: key distribution. The ones leaked can be, theoretically,
blocked, but what if it happens in a case of popular hardware? Imagine
hardware sold in milions of copies (quite possible, in fact). Will the
producer risk unhappiness of the clients and the need to change at least a
part of firmware for all of them? It's also interesting to compare the costs
of development of those solutions and the time it took to break them. The
question is, was there a better way to spend all that money?</p>

<p>Another news is that there's now an OS with heavy DRM build-in. It will
show how much it affects usability. First reviews seem to be rather
negative...</p>

<p>On the other hand, the market of non-DRM books and music is quite well if
you only search for it. See, for instance <a
href="http://preview.baens-universe.com/articles/salvos6">Baens</a> and <a
href="http://www.jamendo.com/">Jamendo</a>.</p>

<p>So why the title 'DRM: a few years earlier'? The DRM issue is not yet
solved and it's flowing. I think that from the perspective of the next 10
years we will consider current times as the moment when the whole thing was
decided. Ans what will the decision be? I'm quite optimistic. I think that
some kind of DRM will survive, but only for limited uses, not the popular
market.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2006/12/31/T19_31_28/</link>
<title>Clock skews again</title>
<dc:date>2006-12-31T19:31:28+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security</dc:subject>
<description>
<![CDATA[<p>Wired reports <a
href="http://www.wired.com/news/technology/0,72375-0.html?tw=rss.technology">another
clock skew-based attack</a>. In fact, it's just an addition to <a
href="http://ksiezyc.net/blogen/archives/2005/03/14/T22_54_27/">another
attack presented in 2005</a>. This time clock akew is affected by the system
load (and temperature change).</p>
<p>I don't find this attack usable against servers with average (and higher)
load or those running more services, as it'd be very hard to be sure what
has changed the clock skew. On the other hand, as one of the methods, with
more different tests, it may be fine.</p>
<p>It should be noted that there are more and more attack agains
cryptographic systems (anonymity systems like Tor use cryptography heavily)
that are indirect, like all timing or cache attacks. It's quite an
interesting thing and it has a number of reasons: such attacks are easy to deploy,
but hard to defend against. And, probably the most importat thing: they use
features which are not taken into account when creating a cryptographic
protocol.</p>
<p>I think there are more such attacks comming. Who knows which one, and
using which feature, will be the easiest to use in practice.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2006/10/08/T19_29_00/</link>
<title>The story of 30 FF bugs</title>
<dc:date>2006-10-08T19:29:00+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security</dc:subject>
<description>
<![CDATA[<p>One of the main news of the last week was about <a
href="http://news.com.com/Hackers+claim+zero-day+flaw+in+Firefox/2100-1002_3-6121608.html">30
serious bugs found in Firefox</a>. Comments posted just after that are very
interesting and show some important thing: about people reactions, the way
such thing can cause FF vs IE flame-wars and so on.</p>
<p>Finally, it looks that <a
href="http://developer.mozilla.org/devnews/index.php/2006/10/02/update-possible-vulnerability-reported-at-toorcon/">it
was just a joke</a>. It's still worth it to think about an emergency plan
when something like that happens to your most important application. Or if it's
worth acting at all.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2006/08/19/T21_32_20/</link>
<title>German data retention doubts</title>
<dc:date>2006-08-19T21:32:20+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security</dc:subject>
<description>
<![CDATA[<p>I have thought that data retention is suse in the EU. It seems that it's
not the case. <a
href="http://www.heise.de/english/newsticker/news/76958">Heise.de is writing
about an report</a> for German parliment about the changes needed to
implement data retention directive. It concludes that it may be impossible
without getting into conflict with constitution-backed rights.</p>
<p>It's quite interesting as I have not seen many opinions stating that
storing detailed connection data breaks the right to privacy.</p>
<p>I'm not very optimist about this. I guess the directive will be finally
passed (with anonymous networks growing and new solutions beeing introduced),
but it's worth watching how the situation progresses.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2006/08/12/T17_25_44/</link>
<title>Privacy and secutity throughts</title>
<dc:date>2006-08-12T17:25:44+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>Security</dc:subject>
<description>
<![CDATA[<p>After the recent <a href="http://en.wikipedia.org/wiki/2006_transatlantic_aircraft_plot">London
events</a> I expect new privacy-related initiatives.</p>
<p>Biometric passports are (at least here in Europe) nearly certain. With
open questions about the data stored, methods of accessing the data and so
on. </p>
<p>In Poland, for example, biometric passports will be released from August
28, this year. The regulations are so general, that all you can learn about
the way the data is written is that 'it's on the chip'. There's <b>no single
word</b> about data security. I'd like to know, at least, if the data is
encrypted and how is it protected from unauthorized access. Also, there's
nothing about the way the data is stored in the databases (it's a good guess
that there's one) and who has access to it. And, well... what's exactly
stored? Ironically, the Ministry's site is stating that biometrics is used
to protect against identity theft.</p>
<p>I have also read a number of discussions about the recent events and
earlier, about privacy concerns. There's a very visible contrast in
attitues. Many people are ready to give up much of their freedem to have (an
illusion of?) security. What's more, it's not uncommon to read something
that has similar meaning to 'if you're not an terrorist, why are you against
police reading your emails?'.</p>]]>
</description>
</item>
<item>
<link>http://ksiezyc.net/blogen//archives/2006/08/01/T20_42_07/</link>
<title>Back to blogging</title>
<dc:date>2006-08-01T20:42:07+02:00</dc:date>
<dc:creator>Mara</dc:creator>
<dc:subject>General</dc:subject>
<description>
<![CDATA[<p>with new Nanoblogger (previous got deleted at some point), spam
removed...Just back to work.</p>
<p>Update 06.08: Move seems to be done. A number of things has changed between the versions.</p>]]>
</description>
</item>
</channel>
</rss>
