Jun 13, 2019 03:24 PM
(This post was last modified: Jun 13, 2019 11:32 PM by devvariety.)
This is a project I'm currently working for the fun of it. I still have to rewrite some parts of it since it was a project sitting in the back burner for a while now.
github.com/developervariety/secureapp
Check it out if you're ever in need of a licensing system that could be self-hosted.
Constructive criticism is accepted. I want to improve this project to the best of its ability.
I'm working on moving to a factory design instead of the poor coding state it's in right now.
DO NOT DEAL WITH THIS MEMBER
I would probably use udp for this
(Jun 13, 2019 04:54 PM)gigajew Wrote: I would probably use udp for this
Could you explain why?
I'm open to all suggestions.
It’s faster, connectionless and pretty easy to work with
(Jun 13, 2019 08:50 PM)gigajew Wrote: It’s faster, connectionless and pretty easy to work with
Why would anyone use a connectionless protocol like UDP for a licensing system where reliable data transfer is a must?
I guess if you like building your own TCP stack equivalent with retransmissions, error correction, duplicate removal and encryption layers on top, go for it. I'd much rather not reinvent that wheel to be honest for a variety of reasons.
(Jun 14, 2019 12:17 AM)Washi Wrote: Why would anyone use a connectionless protocol like UDP for a licensing system where reliable data transfer is a must?
I guess if you like building your own TCP stack equivalent with retransmissions, error correction, duplicate removal and encryption layers on top, go for it. I'd much rather not reinvent that wheel to be honest for a variety of reasons.
Your signature, its beautiful. 🤣
DO NOT DEAL WITH THIS MEMBER
(Jun 14, 2019 12:17 AM)Washi Wrote: Why would anyone use a connectionless protocol like UDP for a licensing system where reliable data transfer is a must?
Lol this + sig 🤣
(Jun 13, 2019 08:50 PM)gigajew Wrote: It’s faster, connectionless and pretty easy to work with
Yeah - because UDP is definitely going to be a lot more secure than TCP for a licensing system. 🤨 Let's just broadcast all the data out to anyone who wants to receive it, and allow any recipient to respond...
Jun 15, 2019 02:47 PM
(This post was last modified: Jun 16, 2019 01:12 AM by devvariety.)
I have been doing some changes to the design until I feel satisfied with it. I want it to be readable, and clean as possible. Any suggestions truly do help me.
I will be working on the panel any day now, just been busy with work and other projects. This project is coming out great though, love the support. Thank you everyone, enjoy your day.
Pushed changes for the license key design.
You could read more on it here, github.com/developervariety/secureapp/wiki/License-Keys.
An example from the demo found on the repository.
Code NM1O9-7E3B6-B8X6UW-CMHS5-H8UTO
This license key is valid.
AppId: 926cd2aa03cd4a44851aead91e43162c
Tier: Bronze
Edition: Professional
Expiration date: 7/16/2019 3:41 AM
Good day!
If anyone is interested on helping me decide which way to go on about this issue, github.com/developervariety/secureapp/issues/3.
I'm debating on whether creating a RESTful API with Slim Framework or creating a WinForms app with a plugin system.
Why yours when there are dozen of licensing system available ? Is a question you may ask yourself
Assert failure(PID 10704 [0x000029d0], Thread: 10960 [0x2ad0]): pBuffer != NULL
Jun 16, 2019 09:16 AM
(This post was last modified: Jun 16, 2019 09:27 AM by devvariety.)
(Jun 16, 2019 02:41 AM)Aristocles Wrote: Why yours when there are dozen of licensing system available ? Is a question you may ask yourself
There are multiple solutions available, you're correct but they all consist of the same features. None show you how secure they are nor customizable to your likings. You're supposed to take the developer of the solution word for it without any proof.
I'm not trying to replace all solutions and say hey, use this one, this is much better. My end goal is to create a solution that is good, secure, and customizable to the developers likings.
SecureApp is something different from others in my opinion. It shows you that it's a true secure licensing system and no bloated bullshit just to sell you out. Nor does it cost anything, completely free and open sourced. The community can fix bugs or add more features faster than a private solution (depends on the team and size).
Jun 18, 2019 04:48 PM
(This post was last modified: Jun 18, 2019 04:51 PM by devvariety.)
I have implemented a plugin system for the server side. Developers now don't have to go deep into the project to internally change anything, just create a plugin and pop, works just the way you want it to.
The only con, which is what I'm trying to figure out is dependencies. When a plugin has a dependency, it has to be in the same directory as the executable.. which is silly and annoying to do. If anyone could create a PR to improve that it would help or any suggestions.
Good day, thank you!
Been pushing some changes to the repository. So far everything is going smooth, let me not jinx it. I have started to work on the panel since then I have decided to add/remove some features. The list below is the current list of features that will be implemented or already implemented. The list can change.
- Application auto-updater
- Assembly verification
- Remote functions
- Remote variables
- Plugin framework
- Short cryptographically generated keys
- Announcements (news system)
- Exception logging
- Hardware fingerprint locked
- Webhook events
- Secure and compressed communication
- Web panel
Any suggestions are welcome, thank you.
DO NOT DEAL WITH THIS MEMBER
Jun 22, 2019 03:54 PM
(This post was last modified: Jun 22, 2019 03:55 PM by NYANxCAT.)
(Jun 22, 2019 03:26 PM)devvariety Wrote: Been pushing some changes to the repository. So far everything is going smooth, let me not jinx it. I have started to work on the panel since then I have decided to add/remove some features. The list below is the current list of features that will be implemented or already implemented. The list can change.
- Application auto-updater
- Assembly verification
- Remote functions
- Remote variables
- Plugin framework
- Short cryptographically generated keys
- Announcements (news system)
- Exception logging
- Hardware fingerprint locked
- Webhook events
- Secure and compressed communication
- Web panel
Any suggestions are welcome, thank you.
Excellent job. this kind of projects will keep the C# forum active and alive.
I hope many HF legit sellers will use this and give feedback.
suggestions:-
for now, I don't have any, but maybe add some kind of panel captcha protection or a challenge to prevent brute force attack.
EDIT: haven't seen the project yet. I will check it out soon.
|