# Offline use on the Glowforge is it technically possible?

**URL:** https://community.openglow.org/t/offline-use-on-the-glowforge-is-it-technically-possible/34
**Category:** General Discussions
**Created:** [March 12, 2018, 12:20pm UTC](https://community.openglow.org/t/offline-use-on-the-glowforge-is-it-technically-possible/34 "2018-03-12T12:20:06Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![ScottW514](https://community.openglow.org/user_avatar/community.openglow.org/scottw514/32/5_2.png) [@ScottW514](https://community.openglow.org/u/ScottW514)
#### Post date: [June 6, 2018, 4:37pm UTC](https://community.openglow.org/t/offline-use-on-the-glowforge-is-it-technically-possible/34/5 "2018-06-06T16:37:25Z")

</div>

The only issue is that the factory firmware validates the server’s TLS certificate by comparing it’s fingerprint with hard-coded values.

This can be overridden by modifying a configuration file (/data/glowforge.conf) on the device, as can the server addresses that the device connects to.

So, as long as you can still get access to the device’s [console port](https://github.com/ScottW514/GF-Hardware/wiki/AA_Appendix-A:-Console-Access) (which may be an issue on later production models), you’d be good to go.

> [@adebaumann](#):
>
> I assume the communication between the GF and the cloud is reverse-engineerable enough

Already [done](https://community.openglow.org/t/communicating-with-the-cloud/78)! Also see [Glowforge Utilities](https://github.com/ScottW514/Glowforge-Utilities) and usage [here](https://community.openglow.org/t/glowforge-emulator-initialization-and-connection-to-the-service/96).

---

_[View the full topic](https://community.openglow.org/t/offline-use-on-the-glowforge-is-it-technically-possible/34)._