The admin page won't open any more
Current browsers refuse the old encryption, and the Java applets, Flash or ActiveX controls the interface was built on no longer run anywhere.
Firmware & software reconstruction
When a vendor discontinues a device, the hardware keeps working but the software around it falls behind. The admin page stops opening in current browsers, the encryption is years out of date, and nobody ships security fixes. We rebuild the firmware and software from scratch, so the equipment stays secure, reachable and on the network it already belongs to.
Platforms we've brought back
The problem
Industrial and professional hardware is built to run for twenty years. Vendor software support rarely lasts half that.
Current browsers refuse the old encryption, and the Java applets, Flash or ActiveX controls the interface was built on no longer run anywhere.
Cleartext Telnet and FTP, shared factory passwords and a kernel from the 2000s. A forgotten controller is an easy way into a building or plant network.
It was written for Windows XP, needs an unsigned driver, or phones home to an activation server that was switched off years ago.
Swapping a controller that sits on a field bus means rewiring, recommissioning and downtime. New firmware for the box you already have is usually cheaper and safer.
Security
Every rebuild gets current cryptography, a minimal attack surface and a way to keep receiving updates. Below is what we typically find on a discontinued controller, and what we replace it with.
| Area | Vendor firmware, as shipped | After Unsunset |
|---|---|---|
| Protocol | SSL 3.0, TLS 1.0 | TLS 1.3, with TLS 1.2 (AEAD suites only) for older clients |
| Ciphers | RC4, 3DES-CBC, static RSA key exchange | AES-256-GCM, ChaCha20-Poly1305, X25519 forward secrecy |
| Certificate | RSA-1024 with SHA-1, self-signed, often expired | ECDSA P-256 from your own CA, or renewed automatically over ACME |
| Remote admin | Telnet and FTP, passwords sent in cleartext | SSH with Ed25519 keys and SFTP. Cleartext services off by default |
| Credentials | One factory password shared by every unit | Unique per unit, changed at first login, optional LDAP or RADIUS |
| Operating system | RTOS or kernel from the 2000s, no patches | Long-term-support Linux kernel on a published patch schedule |
| Updates | Unsigned images, no way back if a flash fails | Signed images, A/B install, automatic fallback to the last good version |
A default-deny firewall. Only the ports the device actually needs are open, and management can be bound to a separate VLAN or interface.
Authentication, configuration changes and faults are sent over syslog to your SIEM, so the device stops being a blind spot.
Some devices are too small for modern cryptography. We put a hardened gateway in front that speaks TLS 1.3 to your network and the old protocol on an isolated link.
Every release is scanned for weak protocols, open ports and known vulnerabilities before it ships. You receive the report with the image.
We document the security controls on each device against IEC 62443-4-2, which helps with NIS2 and Cyber Resilience Act obligations.
Support plans include kernel and library patches, certificate renewal and advisories when a vulnerability affects your devices.
Modern browsers
Since 2020, Chrome, Firefox, Safari and Edge have refused TLS 1.0 and 1.1. Java applets, Flash and ActiveX are gone completely. For many older devices that means the admin page shows a security error or a blank frame.
ilon-boilerhouse.plant.local uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Drop-in
We change the software inside the box and nothing around it. Addresses, wiring, field-bus bindings and the systems that talk to the device carry over unchanged.
Your BMS, SCADA or back office keeps the same endpoints and data points.
Same IP address, hostname, VLAN and firewall rules.
Same hardware and mounting. Configuration is imported from the running unit.
LonWorks, Modbus or serial addresses, bindings and wiring stay as they are.
Reversible. Wherever the hardware allows it we keep the original boot loader, so a unit can go back to the vendor firmware.
Rolled out unit by unit. One device at a time, during normal maintenance windows, with a rollback plan written down for each one.
Selected work
Each project starts with hardware the vendor no longer supports and ends with software you can run, read and maintain.
Building automation · Firmware
These LonWorks/IP servers still run heating, ventilation and lighting in many buildings, on an operating system that has been out of support for over a decade. We ported a current long-term-support Linux kernel to the original MIPS hardware and reconstructed the driver for the LonWorks chip from the vendor firmware.
Embroidery · PC software
The Futura machines needed Windows-only software and a USB driver that no longer loads. We recovered the USB protocol and wrote a new app that runs in Chrome or Edge over WebUSB, including on a Chromebook.
Building automation · Server
Maintenance for controllers whose vendor support has ended. That means security patches, certificate renewal, and integration with current BMS and IoT platforms.
Fuel retail & payments
IFSF dispenser protocol simulators, card-reader SDK research, and ports of discontinued vendor software to current ARM boards such as Raspberry Pi and Rockchip.
Services
New boot chains, kernels and root filesystems for discontinued hardware, built reproducibly with Yocto and Buildroot.
Modern, cross-platform software for machines tied to dead operating systems, including browser apps over WebUSB and WebSerial.
Modern TLS, key-based admin access, a closed attack surface and signed updates for devices that have to stay on the network.
USB, serial, field-bus and network protocols captured, decoded and written up as specifications you can build against.
QEMU-based device models, so firmware is tested automatically before it is flashed to scarce real units.
Maintenance measured in years, with a clear update channel and an engineer who answers when a unit misbehaves.
Process
We review the device, scan it for security problems, and agree what a good outcome looks like. You get a written report and a fixed-scope proposal.
Flash dumps, bus captures and binary analysis. We document how the device behaves before we change anything.
New firmware or software written from the recovered specification. It is original code, structured so others can maintain it.
Automated tests in emulation, then on real hardware, plus a security scan of every release candidate.
Rollout unit by unit, full documentation and source handover, and optional long-term maintenance.
Working with us
Every engagement is fixed price, agreed before work starts.
Assessment
For when you need to know where you stand.
Rebuild
New firmware or software for a device family.
Support plan
For devices that have to stay safe for years.
Principles
Reverse engineering for interoperability is lawful in most jurisdictions, and we work strictly within those limits.
Toolbox
In the EU and the US, reverse engineering to make independent software work with hardware you own is permitted under specific conditions (EU Software Directive 2009/24/EC, Article 6, and 17 U.S.C. §1201(f)). We check each project against those conditions and never redistribute vendor code. This is not legal advice, and we're happy to work with your own counsel.
Wherever the hardware allows it, yes. We keep the original boot loader and give you a documented way back. If a device can't be made reversible, we tell you during the assessment, before any work starts.
No. The device keeps its IP address, hostname and field-bus configuration, and the systems that talk to it keep working. You can optionally move management to a separate VLAN.
Some processors and memory sizes can't run TLS 1.3 at a usable speed. We then put a small hardened gateway next to the device that handles encryption towards your network and talks to the device over an isolated link.
Usually one or two sample units for the reconstruction work, which we return. Any firmware images, manuals and captures you already have make the work faster.
You do. You receive the source code, the build system and the specifications. We can keep maintaining it under a support plan, but you are never dependent on us.
An assessment usually takes about two weeks. The assessment report gives a timeline and a fixed price for the rebuild, which depend on the device and on how much of it needs to change.
Contact
Tell us what it is and what stopped working. We reply within two working days with an initial assessment, at no cost.