how about https functionality for the opensuse forums and website for those that wish to use it ?
idshark wrote:
>
> how about https functionality for the opensuse forums and website for
> those that wish to use it ?
>
>
Thats a nice idea. SSL could be enabled for the NNTP too.
On 2008-06-22, idshark <idshark@no-mx.forums.opensuse.org> wrote:
> how about https functionality for the opensuse forums and website for
> those that wish to use it ?
Why ?
–
The sand remembers once there was beach and sunshine
but chip is warm too
– haiku from Effector Online, Volume 1, Number 6
because not everyone likes to send some things unencrypted over teh tubes
The problem with https is that it causes overhead for already a relatively high volume website.
On 06/23/2008 idshark wrote:
> because not everyone likes to send some things unencrypted over teh
> tubes
The Novell login is encrypted, and the messages here are quite public anyways, huh?
Uwe
Its not about the content per say but the transmission when you have things like this going on I think you tend to think twice about security:
The Local - ‘Orwellian law must be stopped’
On 2008-06-23, idshark <idshark@no-mx.forums.opensuse.org> wrote:
>> > how about https functionality for the opensuse forums and website
>> > for those that wish to use it ?
>> Why ?
> because not everyone likes to send some things unencrypted over teh
> tubes
But what you’re sending it to a public forum, where everyone can see int
anyway…
–
The sand remembers once there was beach and sunshine
but chip is warm too
– haiku from Effector Online, Volume 1, Number 6
ffs it was just a suggestion , like I said before its not about the end content but the transmission of that content.
There are a lot of easier ways to read what you post here, a LAN trace is rather inconvenient 
Really, I’m the first to put on my tinfoil hat, but this is one of the cases where I think it is getting paranoid. Can you elaborate, please?
Uwe
sorry Ive had a bad day , but it was just an idea.
just an example
work:
where even from a administrative point of view, you never know when a auditor or who else is watching, tracing, etc, they can use this as under the free time clause etc etc.
like I said before less about the end content more about the actual transmission of data
idshark,
To answer your question, we haven’t given it any consideration and to tell
you the truth, we’re not likely to because as was said in another message 1
- the password information is already encrypted and 2 - the rest of the
stuff here is open to the world so we have no reason to put any resources
into securing it.
thats cool like I said just a suggestion , maybe you could give the nntp guy some love ?
idshark,
> maybe you could give the nntp
> guy some love
Done.
Not to beat in on you as I do get what you mean idshark.
The other side of if, as stated by Uwe, is that the login is secure.
If people want to (hack and) track the site’s content for whatever reason, SSL won’t block this as there would be many other potential doors for this.
Logging is one thing that’s getting laid down by a law more and more, having many reasons for it - You can try to avoid it but I guess it’s something that usually just comes with the game.
Next to the overhead of encrypting, one of the things that goes with an open structure like we have here is, well, ‘openness’.
One step further, as this is internet I would suggest to always try to be thoughtful of what you are doing and how you react to others. I don’t mean this in a ‘Big Brother’ kind of way, but just the fact that you are dealing with many people…
I’m sure I’m going way over how you meant your question & my small glass of wine can have something to do with that… 
Cheers,
Wj
ps. Just to add - you are not having a bad day! We just hit a topic we seem to like to talk about
What??? We can’t do LAN traces here? … and now you tell me!! Gezzzz… 
Oh, yeah? The site register seems to say otherwise!
On 06/26/2008 keyhive wrote:
> ‘Security Problem w/ openSUSE Site Register [says Firefox3]’
> (http://tinyurl.com/5fzhbq)
<shrug> I cannot reproduce it here (FF3 on Opensuse 11), so it isn’t a general problem.
Uwe
The images aren’t encrypted via SSL and are refered by non-SSL connections thus causing the error.
Big Whoop™.