Feature #371
Support for both http and https
| Status: | Closed | Start date: | 05/03/2010 | |
|---|---|---|---|---|
| Priority: | (P3) Normal | Due date: | ||
| Assignee: | Michael Troß | % Done: | 100% |
|
| Category: | dSS | |||
| Target version: | Sprint 08 | |||
| Severity: | Normal | |||
| Story points | 1 | |||
| Velocity based estimate | - |
Description
Users should choose which protocol requirements they have. If content encryption is required, it's the users responsibility of installing an appropriate certificate.
Currently we could additionally enable ssl encoding if a valid certificate is present. Later the configuration frontend should have a function to disable the http or https usage, same for the soap interface, and to manage the dSS server certificate.
Related issues
Associated revisions
add compile option to use http additionally
refs #371
History
Updated by Miguel Rodriguez over 1 year ago
- Status changed from New to Assigned
- Assignee set to Patrick Stählin
- Target version set to 0.9.0-alpha1
Updated by Patrick Stählin over 1 year ago
- Status changed from Assigned to Feedback
- Assignee changed from Patrick Stählin to Michael Troß
As we're implementing the security features on the dSS, being able to turn the encryption off undermines that goal. I don't see a use-case for an end-user to turn the encryption off. That said if you have a use-case that shows that we really need to turn the encryption off, I'd make it a compile-time option.
Updated by Miguel Rodriguez over 1 year ago
- Target version changed from 0.9.0-alpha1 to 0.9.0-alpha3
Updated by Miguel Rodriguez over 1 year ago
- Status changed from Feedback to Assigned
- Assignee changed from Michael Troß to Patrick Stählin
- Target version changed from 0.9.0-alpha3 to 0.9.0-alpha4
Your suggestion has been accepted
Updated by Christoph Hofmann over 1 year ago
I suggest to have 2 simultaneous ports for http and https. E.g. port 8080 for https, port 8081 for http. So the user (or a client) can decide which port he wants to use. If router port forwarding is needed, the secure port should be used.
With ssl only it is VERY difficult to use our json API because many clients do not support ssl. Examples: Embedded controllers with small CPUs, wget on our own dSS and so on...
Updated by Miguel Rodriguez about 1 year ago
- Assignee changed from Patrick Stählin to Michael Troß
- Target version changed from 0.9.0-alpha4 to 1.0
Updated by Patrick Stählin about 1 year ago
We'll be using stunnel in an upcoming release so it might be better to document how to setup stunnel to listen on external interfaces than building this into the dSS.
Updated by Miguel Rodriguez about 1 year ago
- Status changed from Assigned to Resolved
- Target version changed from 1.0 to 0.9.0-rc1
Updated by Michael Troß 10 months ago
- Status changed from Resolved to Feedback
- Assignee changed from Michael Troß to Miguel Rodriguez
The agreed solution - to have a compile tim option for http support - is still not in mainline, the merge request
http://gitorious.digitalstrom.org/dss/dss-mainline/merge_requests/210
is neither processed nor rejected.
Updated by Miguel Rodriguez 9 months ago
- Status changed from Feedback to New
- Assignee deleted (
Miguel Rodriguez) - Target version deleted (
0.9.0-rc1)
Updated by Miguel Rodriguez 8 months ago
- Status changed from New to Assigned
- Assignee set to Patrick Stählin
- Target version set to 1.0.3
If not in agreement to merge please comment.
Updated by Sergey Bostandzhyan 7 months ago
- Assignee changed from Patrick Stählin to Sergey Bostandzhyan
Updated by Miguel Rodriguez 7 months ago
- Target version changed from 1.0.3 to Backlog longterm
Updated by Michael Troß 3 months ago
- Target version changed from Backlog longterm to Sprint 08
Updated by Michael Troß 3 months ago
- Story points set to 1
Updated by Sergey Bostandzhyan 3 months ago
- Category set to dSS
- Status changed from Assigned to Resolved
- Assignee changed from Sergey Bostandzhyan to Michael Troß
- % Done changed from 0 to 100
Merged into mainline.
Updated by Michael Troß 15 days ago
- Status changed from Resolved to Closed