-
Notifications
You must be signed in to change notification settings - Fork 1
ssl for trac #3914
Comments
Author: TomH Please stick to one issue per ticket. For the record, trac and www already use SSL for sensitive data so no changes are planned there. If you wish to raise a new ticket for the wiki login to be put under SSL then please feel free to do so. |
Author: skyper Replying to [comment:1 TomH]:
Then you and me would have to comment at least three tickets but if you prefere that. I thought this is one case for all.
Yes, if you say that the password is the only sensitive data. The username is later transmitted from the server if you are logged in or did I get something wrong. What I meant is a general possibility to use https instead of http at least at all "edit" pages but I would prefer it for all pages.
Thanks, I did not notice that cause I trimmed script blocker. I opened [ticket/#3919] |
Author: TomH There are very good reasons for not putting the whole of www under https - it would be very expensive from a CPU point of view. If you think your username is "sensitive" then you are clearly confused, as it can be seen by anybody that wishes to browse your edits, diary entries etc and is included in every planet dump we publish. |
Author: skyper Replying to [comment:3 TomH]:
Ok, how about trac and wiki ?
There is only a connection between the username and a IP while logged in or commiting data. Would be nice if at least this information is secure transmitted (I know the api has no ssl, too). |
Author: skyper Ooohps The wiki is working with https. I drop it for www but support for trac would be nice |
Author: skyper trac has ssl support for some time now. There are solution with loopback proxies to cache internal and still transmit with ssl support. E.g. even for www it would be possible to offer ssl support. |
Reporter: skyper
[Submitted to the original trac issue database at 12.40pm, Tuesday, 19th July 2011]
Please, provide ssl.
I do not like to browse and submit data unsecured.
Thanks a lot.
The text was updated successfully, but these errors were encountered: