#go build limiter
10 messages · Page 1 of 1 (latest)
date wont do it. you can change date on the computer.
This is not a feature which comes standard in any compiler I am aware of -- Go or otherwise.
May I ask why you want to do this?
Oh. I misunderstood. You'd like to make the binary unusable after that time?
Hrm. This isn't quite what you want but it gets part way there. Maybe you can build on it.
- Build your binary.
- Encrypt it.
go:embedthe encrypted binary into the binary which you will distribute.- Host a server which provides a server-side decryption mechanism. Buy or rent a static IP for the allotted time. The server, when contacted, will decrypt the binary and return it to the client.
- Host the binary in memory and run it as Go code... somehow 🤷. Don't write it to disk or you'll leak your binary.
Maybe there isn't a solution... If anyone can improve on this or knows a way to run a Go binary from in memory (maybe via an in-memory file system)... That ought to do it. A cracker could swipe the contents from memory but that's... Always possible.
Exactly
Well your idea is pretty cool actually but can i maybe link that binary to an api and control it with the api to make it easyier? 🤔🤔🤔
there is not a good way to do this at all
the real solution is just don’t give them the binary
This is true. If you can build a client which talks to a server where you run your code -- that's the only way to have actual security