Dreez wrote:
the certificate is outdated (which really shouln't have an effect), however the connection actually is encrypted
Outdated means it is vulnerable to attack... Which is why browsers state it not being secure by crossing out https. One simple Google Search gave me the below as top result.
http://thehackernews.com/2014/12/SSL-Po ... ttack.htmlThere is other vulnerabilities TLS 1.2 have on the same simple search. (Heartbleed comes to mind)
Edit: Pottu please don't follow suit in thinking outdated security protocols are secure. There is reasons they are updated. Main reason security protocols are updated are to fix holes, like the one described in the link and also the one I remember that affected a lot of SQL databases and some TLS encryptions.
Edit 2: If it was using the POODLE exploit, they would have gotten a hash signature of your login and depending on your password security (check page 3 of this thread) a hash check can take a max of 3 days for a password as short as 8 characters, doesn't matter how secure it is to hack without even having the password to begin with, just the hash stolen from the POODLE attack, if it would be possible to brute force poodle (that requires rehashing and I am sure Tuleap has a prevention against brute force) they could get it as sooon as 4000 attempts on the site as said in the linked article. If the bot only logged hashes though and you had a password 8 characters or shorter (doesn't matter complexity with hash cracking) then you're account would have been hacked within 3 days time on a potato PC.