Towards secure IoT programming in Haskell

Valliappan, Nachiappan; Krook, Robert; Russo, Alejandro; Claessen, Koen

doi:10.1145/3406088.3409027

Cited by 9 publications

(9 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Hailstorm [64], and Haski [80]. None of these languages are tierless IoT languages as they have no automatic integration with the server.…”

Section: Functional Reactivementioning

confidence: 99%

“…Another example are programming language technologies for controlling information low, and these can be used to improve security. For example Haski uses them to improve the security of IoT systems [80].…”

Section: Securitymentioning

confidence: 99%

“…As another example program analyses can be applied, and Section 3.3 and [82] outline some of the analyses could be, and in some cases have been, used to improve IoT systems. Examples include automatic tier splitting [56], and controlling information low to enhance security [80].…”

Section: Reflectionsmentioning

confidence: 99%

See 2 more Smart Citations

Could Tierless Languages Reduce IoT Development Grief?

Lubbers

Koopman

Ramsingh

et al. 2023

ACM Trans. Internet Things

View full text Add to dashboard Cite

Internet of Things (IoT) software is notoriously complex, conventionally comprising multiple tiers. Traditionally an IoT developer must use multiple programming languages and ensure that the components interoperate correctly. A novel alternative is to use a single tierless language with a compiler that generates the code for each component and ensures their correct interoperation. We report a systematic comparative evaluation of two tierless language technologies for IoT stacks: one for resource-rich sensor nodes (Clean with iTask), and one for resource-constrained sensor nodes (Clean with iTask and mTask). The evaluation is based on four implementations of a typical smart campus application: two tierless and two Python-based tiered. (1) We show that tierless languages have the potential to significantly reduce the development effort for IoT systems, requiring 70% less code than the tiered implementations. Careful analysis attributes this code reduction to reduced interoperation (e.g. two embedded domain-specific languages (DSLs) and one paradigm versus seven languages and two paradigms), automatically generated distributed communication, and powerful IoT programming abstractions. (2) We show that tierless languages have the potential to significantly improve the reliability of IoT systems, describing how Clean iTask/mTask maintains type safety, provides higher order failure management, and simplifies maintainability. (3) We report the first comparison of a tierless IoT codebase for resource-rich sensor nodes with one for resource-constrained sensor nodes. The comparison shows that they have similar code size (within 7%), and functional structure. (4) We present the first comparison of two tierless IoT languages, one for resource-rich sensor nodes, and the other for resource-constrained sensor nodes.

show abstract

“…Hailstorm [64], and Haski [80]. None of these languages are tierless IoT languages as they have no automatic integration with the server.…”

Section: Functional Reactivementioning

confidence: 99%

Section: Securitymentioning

confidence: 99%

See 1 more Smart Citation

Could Tierless Languages Reduce IoT Development Grief?

Lubbers

Koopman

Ramsingh

et al. 2023

ACM Trans. Internet Things

View full text Add to dashboard Cite

show abstract

“…However, in contrast to in mTask, the tasks are not interpreted and there is no automated communication with a server. Other examples are CFRP (Suzuki et al, 2017), XFRP (Shibanai and Watanabe, 2018), Juniper (Helbling and Guyer, 2016), Hailstorm (Sarkar and Sheeran, 2020), Haski (Valliappan et al, 2020), arduino-copilot (Hess, 2020).…”

Section: Functional Reactive Programmingmentioning

confidence: 99%

Orchestrating the Internet of Things with Task-Oriented Programming

Lubbers

2023

View full text Add to dashboard Cite

The development of reliable software for the internet of things (IoT) is difficult because IoT systems are dynamic, interactive, distributed, collaborative, multi-tiered, and multitasking in nature. The complexity is increased further by semantic friction that arises through different hardware and software characteristics between tiers. Many computers that operate in IoT systems are edge devices that interact with the environment using sensors and actuators. Edge devices are often powered by low-cost microcontrollers designed for embedded applications. They have little memory, unhurried processors, and are slow in communication but are also small and energy efficient. Task-oriented programming (TOP) can cope with the challenges of IoT programming. In TOP, the main building blocks are tasks, an abstract representation of work. During execution, the current value of the task is observable, and other tasks can act upon it. Collaboration patterns can be modelled by combining and transforming tasks into compound tasks. Programming edge devices benefits from TOP as well, but running such a system within the limitations of resource-constrained microcontrollers is not straightforward. This dissertation demonstrates how to include edge devices in TOP systems using domain-specific languages (DSLs). With these techniques, all tiers and their interoperation of an IoT system are specified in a single high-level source, language, paradigm, high abstraction level, and type system. First, I present advanced DSL embedding techniques. Then mTask is shown, a TOP DSL for IoT edge devices, embedded in iTask. Tasks are constructed and compiled at run time in order to allow tasks to be tailored to the current work requirements. The task is then sent to the device for interpretation. A device is programmed once with a lightweight domain-specific OS to be used in an mTask system. This OS executes tasks in an energy-efficient way and automates all communications and data sharing. All aspects of the mTask system are shown: example applications, language design, implementation details, integration with iTask, and green computing facilities such as automatic sleeping. Finally, tierless IoT programming is compared to traditional tiered programming. In tierless programming frameworks, the size of the code and the number of required programming languages is reduced significantly. By using a single paradigm and a system-wide type system, tierless programming reduces problems such as semantic friction; maintainability and robustness issues; and interoperation safety.

show abstract

“…We later extend it further with array and sum types (Section 4), exception and state effects (Section 5), and other uninterpreted primitives (Section 6). These features have been chosen to illustrate the practical applicability, extensibility, and customizability of NbE to a class of functional eDSLs like Feldspar [6], Haski [42], and others [4,40] found in eDSL literature. Function and product types.…”

Section: Nbe For An Edsl Corementioning

confidence: 99%

Practical normalization by evaluation for EDSLs

Valliappan

Russo

Lindley

2021

Proceedings of the 14th ACM SIGPLAN International Symposium on Haskell

Self Cite

View full text Add to dashboard Cite

Embedded domain-specific languages (eDSLs) are typically implemented in a rich host language, such as Haskell, using a combination of deep and shallow embedding techniques. While such a combination enables programmers to exploit the execution mechanism of Haskell to build and specialize eDSL programs, it blurs the distinction between the host language and the eDSL. As a consequence, extension with features such as sums and effects requires a significant amount of ingenuity from the eDSL designer. In this paper, we demonstrate that Normalization by Evaluation (NbE) provides a principled framework for building, extending, and customizing eDSLs. We present a comprehensive treatment of NbE for deeply embedded eDSLs in Haskell that involves a rich set of features such as sums, arrays, exceptions and state, while addressing practical concerns about normalization such as code expansion and the addition of domain-specific features.CCS Concepts: • Software and its engineering → Functional languages.

show abstract

Towards secure IoT programming in Haskell

Cited by 9 publications

References 22 publications

Could Tierless Languages Reduce IoT Development Grief?

Could Tierless Languages Reduce IoT Development Grief?

Orchestrating the Internet of Things with Task-Oriented Programming

Practical normalization by evaluation for EDSLs

Contact Info

Product

Resources

About