Securing update download for private beta?
Asked by
pygar
Hi,
I'm wondering the best approach for updates within a private beta stage.
Currently the update package can be downloaded by anyone with the URL stored within the appcast.
Could Sparkle present a user and password thus enabling a secure 'app' folder on server?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Sparkle Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask pygar for more information if necessary.
To post a message you must log in.