SSL enabled on the forge. https://scm.joomla.org works!

[rhuk]

Ok, to most this is not a big deal, but to me this is a huge step in the right direction.  I've been working with the good folks at VA to get this setup for the source repository and it's been a bumpy ride with a couple of false starts, but we are now in business.  Thanks to Colin for donating the SSL cert and thanks to Doug for working with me to get everything sorted out.

Anyway, now you can use SVN with the comfort and security of SSL encryption by using https://scm.joomla.org instead of http://scm.joomla.org.

Cheers,

[brian]

For the ignorant among us (myself included) what is the advantage of this

BRian

[rhuk]

Well, the short answer is traffic is encrypted so your data including your login information is not 'sniffable'.  But more importantly for some is that you can retain some annonimity and security while behind a corporate firewall.

[brian]

Well, the short answer is traffic is encrypted so your data including your login information is not 'sniffable'.

In an open source project wouldnt the only point of "sniffing" login info be so that the sniffer could for example upload malicios code into joomla whilst pretending to be Jinx for example?

If so then unless access is only https nothing changes.

[rhuk]

as long as people with commit access use https, things are hunky doray.

[brian]

I think that is what I was trying to say just not very well. Thanks for clarifying