<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mauczka, Andreas</style></author><author><style face="normal" font="default" size="100%">Schanes, Christian</style></author><author><style face="normal" font="default" size="100%">Fankhauser, Florian</style></author><author><style face="normal" font="default" size="100%">Bernhart, Mario</style></author><author><style face="normal" font="default" size="100%">Grechenig, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining security changes in FreeBSD</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">security</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">90 - 93</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Current research on historical project data is rarely touching on the subject of security related information. Learning how security is treated in projects and which parts of a software are historically security relevant or prone to security changes can enhance the security strategy of a software project. We present a mining methodology for security related changes by modifying an existing method of software repository analysis. We use the gathered security changes to find out more about the nature of security in the FreeBSD project and we try to establish a link between the identified security changes and a tracker for security issues (security advisories). We give insights how security is presented in the FreeBSD project and show how the mined data and known security problems are connected.</style></abstract></record></records></xml>