Internet of Things (IoT) devices are devices with embedded sensors or software. Their usage is becoming more prevalent. They are used for smart homes, traffic tracking, weather data and sensor networks. Often IoT devices communicate wirelessly using low-power protocols. A wireless connection provides an easy way to eavesdrop on personal data or even hijack connections. Thus security measures need to be taken. Our thesis looks at a specific IoT operating system, Contiki-NG, and describes the porting process of a Transportation Layer Protocol (TLS) protocol library, MbedTLS. The porting process consists of specific modules that need to be adapted to the Contiki-NG environment. After porting, example programs that send and receive datawere written to enable performance testing that includes execution time, runtime memory usage and code space. The results of the tests were analyzed and evaluated. The produced implementation from porting MbedTLS to Contiki-NG provides a secure connection between two hosts running the TLS protocol. The highly configurable nature of MbedTLS allows the implementation to be adapted to comply to the resource constraints of platforms supported by Contiki-NG. / Internet of Things (IoT)-enheter är enheter med inbyggda sensorer eller mjukvara. Deras användning blir allt vanligare. De används för smarta hem, trafikspårning, väderdata och sensornätverk. Ofta kommunicerar IoT-enheter trådlöst med protokoll med låg energiförbrukning. En trådlös anslutning ger ett enkelt sätt att avlyssna personuppgifter eller till och med att kapa anslutningar. Därför måste säkerhetsåtgärder vidtas. Vårt examensarbete täcker ett specifikt IoT-operativsystem Contiki-NG och beskriver en portningsprocess av ett TLS-protokollbibliotek (Transportation Layer Protocol), MbedTLS. Portningen består av specifika moduler som behöver anpassas till den ursprungliga Contiki-NG-miljön. Efter portningen skrevs exempelprogram som skickar och tar emot data för att möjliggöra prestandatestning som inkluderar exekveringstid, minnesanvändning och kodutrymme. Resultaten av testerna analyserades och utvärderades. Den framställda implementeringen från att överföra MbedTLS till Contiki- NG gav en säker anslutning mellan de två ändpunkterna som kommunicerar med TLS-protokollet. Den i hög grad konfigurerbara karaktären hos MbedTLS gjorde det möjligt att anpassa implementeringen för att följa resursbegränsningarna för plattformar som stöds av Contiki-NG.

<p>This report describes the work and the results found when comparing three different 3d modeler applications. The programs are 3ds Max, Maya and Cinema 4D. The comparisons focus on the possibilities/the amount of freedom these programs interface offer to its plugins. The comparisons are made from the point of view of a tool for creating animations developed as a plugin for these modelers. This plugins demands on the system it is loaded into have been analyzed and from the results of this analysis a template have been created. This template is to be used when porting the plugin to other modeler programs in order to be able to tell at an early stage if it’s possible, or not. This template is appended as an appendix. The plugin described above is in it self a system with a plugin architecture and is described on a higher level in the report.</p> / <p>Rapporten beskriver arbetet och resultatet funnet vid jämförelser mellan tre olika 3d modelleringsprogram. Programmen är 3ds Max, Maya och Cinema 4D. Jämförelserna fokuserar på de möjligheter/friheter dessa programs gränssnitt erbjuder sina plugins. Utgångspunkt i jämförelserna är ett animerings verktyg utvecklat som ett plugin till dessa modelleringsporgram. Detta plugins krav på systemet det laddas i har analyserats och utifrån dessa analyser har en mall skapats för att vid vidare portningar till andra modelleringsprogram på ett tidigt stadium kunna avgöra om det är möjligt eller inte. Denna mall finns med som en bilaga till rapporten. Pluginet som nämns ovan är i sin tur också det ett system med plugin arkitektur och beskrivs på en övergripande nivå i rapporten.</p>

XDtools is a plugin originally used in the NeOn Toolkit ontology editor. XDtools is used as a tool for the ontology engineer when designing new ontologies or to add new parts to existing ontologies. The XDtools plugin was partially ported to another ontology editor, Protégé. This thesis describes the implementation and design choices made during the work with porting the plugin. A description of the parts that have been ported can be found in the report. It also contains the result of the testing and user study made after the implementation. Conclusions of those results and proposed changes to the plugin are also found in the report.

This report describes the work and the results found when comparing three different 3d modeler applications. The programs are 3ds Max, Maya and Cinema 4D. The comparisons focus on the possibilities/the amount of freedom these programs interface offer to its plugins. The comparisons are made from the point of view of a tool for creating animations developed as a plugin for these modelers. This plugins demands on the system it is loaded into have been analyzed and from the results of this analysis a template have been created. This template is to be used when porting the plugin to other modeler programs in order to be able to tell at an early stage if it’s possible, or not. This template is appended as an appendix. The plugin described above is in it self a system with a plugin architecture and is described on a higher level in the report. / Rapporten beskriver arbetet och resultatet funnet vid jämförelser mellan tre olika 3d modelleringsprogram. Programmen är 3ds Max, Maya och Cinema 4D. Jämförelserna fokuserar på de möjligheter/friheter dessa programs gränssnitt erbjuder sina plugins. Utgångspunkt i jämförelserna är ett animerings verktyg utvecklat som ett plugin till dessa modelleringsporgram. Detta plugins krav på systemet det laddas i har analyserats och utifrån dessa analyser har en mall skapats för att vid vidare portningar till andra modelleringsprogram på ett tidigt stadium kunna avgöra om det är möjligt eller inte. Denna mall finns med som en bilaga till rapporten. Pluginet som nämns ovan är i sin tur också det ett system med plugin arkitektur och beskrivs på en övergripande nivå i rapporten.

No description available.

No description available.

Barrelfish operating system is an experimental instance of multikernel structure which exhibits good features such as hardware heterogeneity, scalability, dynamicity, etc. Barrelfish is in progress and lacks applications. Therefore, there is a need to investigate the efficiency of applications running in Barrelfish and one of candidates is a shared-memory application. To conduct an empirical study, Cilk is chosen inasmuch as its runtime library is designed for shared-memory architectures and it has been known to expose good performance. This thesis focuses on making Cilk run on top of Barrelfish in order to reach two goals: portability which is described to be supported by Barrelfish, and good speed afterwards. The porting involves compiling Cilk runtime source code by replacing its pthread subroutines with set of APIs in Barrelfish and then changing the way Cilk scheduler spawns worker thread on multiple cores. However, the main point of the porting is to make different cores access to the same virtual address space. Luckily, Barrelfish provides a notion of domain which specifies the number of cores in an application so that these cores can share the same memory space. This thesis also has carried out benchmarks on some Cilk programs and found that Cilk does not perform as well as it is expected. In addition measurements on parallel workers shows that Cilk on Barrelfish takes more cycles to perform computation. Although Cilk still maintains work-first principle, it cannot achieve the time bound. The spanning domain cost is proportional to the number of cores, but it will matter if applications take small time to complete.

This research investigates the effectiveness of the forward-porting approach employed in the Magma framework as a fault injection technique for evaluating fuzzers. The study aims to assess the use of Proof-of-Concepts in reproducing crashes in CVEs and evaluate the feasibility of forward-porting vulnerabilities into later software versions. An experiment was conducted using three selected open-source libraries to explore whether vulnerabilities could be triggered or reached in the latest versions through the forward-porting approach. The findings suggest that the forward-porting approach may not be the most effective method for injecting vulnerabilities into software systems. Out of the 22 chosen CVEs for analysis, only one could be triggered and two could be reached using the forward-porting approach. This indicates that many of the injected vulnerabilities become obsolete or have unsatisfiable trigger conditions in later versions. Additionally, manual verification of these vulnerabilities have been found to be time-consuming and challenging. Further research is necessary to provide a comprehensive evaluation of the effectiveness of the forward-porting approach in vulnerability injection.

This thesis was submitted to the faculty of Innovation, Design and Technology, IDT, at Mälardalen university in Västerås, Sweden as a partial fulfillment of the requirements to obtain the M.Sc. in computer science, specializing in embedded systems. The work presented was carried out in the months January to June in 2014 partially in Volvo Construction Equipment, Volvo CE, Eskilstuna, and partially at Mälardalen university in Västerås. Federated Resilient Embedded Systems Technology for AUTOSAR, FRESTA, is a collaborative project between Volvo and the Swedish Institute of Computer Science, SICS, that aims to make it possible to add third party applications to vehicle’s computer systems without compromising system security and robustness. The mechanism is developed by SICS for AUTOSAR, AUTomotive Open System ARchitecture, an open standardized automotive software architecture for vehicles. The following report documents the efforts to study and port the FRESTA mechanism to the Volvo CE platform, and develop a Java application to test the porting. The investigation will aspire to determine if it is feasible to introduce Java based third party applications to resource constrained embedded systems, without causing a deterioration in the predictability and security of the system. / Avhandlingen lades fram för fakulteten för innovation, design och teknik, IDT, vid Mälardalens högskola i Västerås som en del av kraven för att erhålla M.Sc. i datavetenskap med inriktning mot inbyggda system. Arbetet genomfördes under månaderna januari till juni 2014 delvis i Volvo Construction Equipment, Volvo CE, Eskilstuna, och delvis vid Mälardalens högskola i Västerås. Federated Resilient Embedded Systems Technology for AUTOSAR, FRESTA, är ett samarbetsprojekt mellan Volvo och Svenska Institutet för datavetenskap, SICS, som syftar till att göra det möjligt att lägga tredjepartsapplikationer till fordonets datorsystem utan att äventyra systemets säkerhet och robusthet. Mekanismen är utvecklat av SICS för AUTOSAR, Automotive Open System Architecture, en öppen standardiserad fordons programvaruarkitektur för fordon. Följande rapport dokumenterar arbetet med att studera Fresta mekanismen till Volvo CE-plattformen, och utveckla ett Java-program för att testa portning. Undersökningen kommer att sträva efter att avgöra om det är genomförbart att införa en Java-baserad tredje part för att resursbegränsa inbyggda system, utan att orsaka en försämring av förutsägbarhet och säkerhet i systemet.

Software forking---creating a variant product by copying and modifying an existing project---is often considered an ad hoc, low cost alternative to principled product line development. To maintain forked projects, developers need to manually port existing features or bug-fixes from one project to another. Such manual porting is not only tedious but also error-prone. When the contexts of the ported code vary, developers often have to adapt the ported code to fit its surroundings. Faulty adaptations or inconsistent updates of the ported code could potentially introduce subtle inconsistencies in the codebase. To build a deeper understanding to cross-system porting and porting related errors, this dissertation investigates: (1) How can we identify ported code from software version histories? (2) What is the overhead of cross-system porting required to maintain forked projects? (3) What is the extent and characteristics of porting errors that occur in practice? and (4) How can we detect and characterize potential porting errors? As a first step towards assessing the overhead of cross-system porting, we implement REPERTOIRE, a tool to analyze repeated work of cross-system porting across peer projects. REPERTOIRE can detect ported edits between program patches with high accuracy of 94% precision and 84% recall. Using REPERTOIRE, we study the temporal, spatial, and developer dimensions of cross-system porting using 18 years of parallel evolution history of the BSD product family. Our study finds that cross-system porting happens periodically and the porting rate does not necessarily decrease over time. The upkeep work of porting changes from peer projects is significant and currently, porting practice seems to heavily depend on developers doing their porting job on time. Analyzing version histories of Linux and FreeBSD, we derive five categories of porting errors, including incorrect control- and data-flow, code redundancy, and inconsistent identifier and token renamings. Leveraging this categorization, we design a static control- and data-dependence analysis technique, SPA, to detect and characterize porting inconsistencies. SPA detects porting inconsistencies with 65% to 73% precision and 90% recall, and identify inconsistency types with 58% to 63% precision and 92% recall on average. In a comparison with two existing error detection tools, SPA outperforms them with 14% to 17% better precision. / text