![]() |
|
Feedback and Suggestions We want to hear your thoughts and ideas! |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
Why no encryption on this site?
![]() |
|
|||
![]()
Probably not, but it would still be preferable to encrypt the log in process/cookie data.
__________________
May the source be with you! |
|
|||
![]()
Most attacks rely on some kind of scripting on the client's side. Disable JavaScript on all websites that don't require it to function and you'll avoid most attacks.
Encryption of any kind is resource-intensive, which is why I suggested only the log in process and cookie data be encrypted. Most of the content is text-only and I doubt anyone will bother MITM'ing our threads. The only code you'll find around here is in source code, not binary, form. In any case, Daemon Forums is a free service that we - its users - don't own, so we shouldn't normally get any say in the final decision. </My humble opinion, naturally.>
__________________
May the source be with you! |
|
|||
![]()
It seems to me that https involves two distinct mechanisms. Please correct me:
1- The stream is (asymetrically) encrypted so no 3rd party can read or inject content. 2- You are garanteed to be visiting the right website through the use of "trusted" certificates. Each domain has his own certificate delivered by organizations. With those 2 features combined, you should end up with a secure connexion to the legitimate website. The problem is, we (internet users) are trusting a handful of organizations to be competent in doing the right things: provide certificates to the right people. So far symantec and trustico have comfirmed that, again, this is prone to failure. The stream is encrypted but maybe not secure if the certificate is compromised. To conclude, I am all for encrypted stream where it is needed. Regarding this forum, I am not sure. Is the login/password encrypted or plain text? My password is disposable after all. Steal it all you want I don't care and will just generate a new one. Certificate OTOH is a false sense of secutiy IMO. I like @tedu approach with his website: https with his own untrusted certificate that you have to accept once. |
|
|||
![]()
This, at the very least. We're not talking about vast quantities of data here, it wouldn't be that much more resource intensive to just encrypt everything. Yes, proc and network usage will go up -- slightly. On reasonably modern hardware, that doesn't particularly strike me as a reason not to do it.
|
|
|||
![]() Quote:
![]() |
|
||||
![]()
The simple reason is that when I started this site in 2008, I didn't have a lot of money, and paying for the domain and hosting was already comparatively expensive at the time, so a SSL cert was a bit too much.
From memory, I think I set up some CACert stuff back in the day. Or maybe I did eventually get a mainstream certificate. I don't recall. I handed stuff over a few years ago, and haven't been very active since. I'm not even sure who manages things now. I'm not sure if it's really worth setting up, given the low level of activity these days.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
DaemonForums and https? | hitest | Off-Topic | 11 | 24th August 2017 04:34 AM |
Relayd as a HTTPS client | e1-531g | OpenBSD Security | 4 | 11th January 2016 07:11 PM |
snownews to support https | daemonfowl | OpenBSD Packages and Ports | 9 | 26th October 2013 06:13 PM |
https ports on PF | mug23 | OpenBSD Security | 5 | 4th March 2011 10:11 PM |