The trojaning of mICQ
Furthermore, as it is actually quite common in actual kinship studies to focus on international adoption or reproductive technologies, these issues were rarely linked to a long term perspective. The ethics of "trojaning" vs. To recover your User ID Procedure.
To set up recovery information for your User ID
As kinship is an over-determined category, it produces ambiguous results. Smith examined the passionate discourses about good and bad corruption that his Nigerian interlocutors mentioned. In a highly paradoxical move, workers who were made redundant by capitalist restructuring and downsizing of their life long work places, attributed moral superiority to the individualizing and ostensibly meritocratic capitalist values of entrepreneurialism which they counterpoised favourably to the apparently corrupting values of community and kinship.
Lentz suggested that in narrative analyses, the role of the media should be scrutinized. Thus, mediation emerged once more as a core methodological problem in understanding the kinship-politics-relation.
All the presenters aimed at positioning their case studies within the given framework, a fact that guaranteed a high originality of the presented papers. The participants sometimes wondered about up to date discussions of the kinship or politics approaches to their subjects of interests. The atmosphere of the workshop resulted in fruitful discussions and inspiring views on same objectives through different lenses. Moral economies and kinship patterns can be important to understand corruption in politics, the question of personal and social trust, as well as questions of procedural reliability.
Connecting to the question whether kinship is inclusive or exclusive legalistic perspective would be fruitful. Furthermore, as it is actually quite common in actual kinship studies to focus on international adoption or reproductive technologies, these issues were rarely linked to a long term perspective. The different lenses of politics and kinship should be integrated on a theoretical scale, in research questions, as well as on the level of the academic gender divide.
A more explicitly historicizing dimension to the recurrent and changing interactions between politics and kinships over time would aid in tackling the related ontological and epistemological questions. From anarchy, to oligarchy to democratic absolutism: Inside and outside the language of kinship: Un doing kinship in a public maternity hospital. State policies and adoption practices in Greece. Ambiguities in celebrating children: How does participation in resistance interact with the construction of family relations?
Modernity and the Persistent Life of Kinship. Oil and Neoliberalism in Argentina. Goody, Parenthood and social reproduction: Doing Politics — Making Kinship: Back towards a future Anthropology of Social Organisation and Belonging. Corruption as political incest Panel 1: Natural politics — substance, kinship, worldview Panel 2: State practices and the re making of kinship. Back towards a future Anthropology of Social Organisation and Belonging, But perhaps the distros should be quite a bit more careful with accepting code from small projects with little accountability.
My point is that large programs are not safer is the lead developers cannot be trusted. It's easier to hide bad things in large projects. Eventually, in all software, trust must stop somewhere. However, it would be far better if multiple barriers had to be broken instead of a single person. Posted Feb 21, This is probably an unpopular opinion, but as far as I'm concerned, the developer can do whatever he damn well pleases with his code, and anyone who complains can just write their own damn programs.
This developer had very reasonable complaints about how his code was being handled by Debian. Perhaps he could have found another way to respond, but Debians' response to his solution was at least as extreme. Debian was very much in the wrong on removing his name from the copyright file, but it seems developers are at the mercy of distributions in such matters.
It is aken to telling programmers, once they have offered their code to the world, to shut up and go away. How their code is presented to the world is at least as important as its functionality, some allowances should be made for that. Furthermore, printing a message and exiting is not a trojan horse, a denial of service attack, an easter egg or anything of the sort. Debian got called on to the carpet with their developer abuse and cried foul, but they have no legitimate reason to. Debian and other distributors would do well to remember that licenses can change, and they can be changed to prohibit them from using such programs at all, or in ways much more to the developers liking.
Angering the foundation on which your distribution is based is not a good idea. In my not so humble opinion, Debian owes Mr.
Kuhlmann an apology and should take steps to correct their mistakes. Posted Feb 22, 0: When Opera developers were upset about MSN serving broken pages, they released the "Bork" edition, but they were open about the changes they made.
It's not like "borkifying" MSN was an undocumented feature of an official release. Kuhlmann was upset about Debian distributing old versions of micq, he should have encourage the Debian maintainer to upgrade.
Mining the new version to protest against distributing old versions is preposterous. The result of his actions is that the future maintainer will be pretty much discouraged from grabbing the next version without doing a very careful audit of the changes. Posted Feb 22, 2: You cannot justify Debians' actions just because you don't agree with the developer.
It would have been better perhaps if he had found some other way to get his point across, but I don't believe for a minute that he hadn't already exhausted most "diplomatic" methods before doing this. Don't forget that he would be helpless to stop the debian maintainer from removing his bitch message, which was the whole point of obfuscating it and waiting for a specific date in which to appear.
He did that precisely because the Debian maintainer has the power to shut him up as it were. Remember that the Debian maintainer was roundly criticized for effectively failing to do so.
Regardless of his so called "childishness", Debian made the greater error in removing his name from the copyright file. That is not excusable, and his later actions do not change the fact that Debian owes him an apology. And I stand by that assertion. Posted Feb 22, If they do not like his features, they should not use his software.
It is their choice. The removal of the name from the copyright is the big issue here. That is expressley prohibited under copyright law and illegal in countries that have signed international copyright agreements. The maintainer should be severely chastised for this, even more so since he is ostensibly a supported of software libre. As far as this being some tip of the iceberg situation as the original LWN editor suggested, please, enough with the scare mongering.
There is nothing new here save perhaps people had their assumptions challenged. Using software, commercial or open source is a calculated risk.
There are no guarantees. However I would suspect that we have much more to fear from incompetence than malice when it comes to software. The ethics of "trojaning" vs. Posted Feb 24, 2: Posted Feb 23, I agree up to the point of fraud, which is what we had here. The author intentionally misled the Debian project into shipping something different -- something of clearly less value -- from what it thought it was shipping.
Had the author been open about what was in the program, I would have no problem with it. Posted May 20, Log in to post comments. Loschwitz see the trojan code when he diff'd the old version against the update, to see what had changed? He was upbraided by other maintainers for this. The offending message was coded in base64 iirc, the reference used to hide the message from appearing on the system of the Debian maintainer was set up to use his specific ICQ name, hardcoded a letter at a time rather than a more obvious string, and even the reference to Debian was chopped into substrings to not stand out.
However, the main developer gradually can redesign the program in such way that the trojan cannot be detected. For example, the "anti-Debian" text could be hidden in a table used for encryption of for calculating checksums.