Looking forward to see IPS4 Chat with SSL. We also modified our url structure in PublicOutput.php to make the chat work via http:// and many other pages via https:// Please notice if you make your forum work via a secure connection (https://) that visitors in most cases will get mixed content warnings in their browser because many external elements such as added images by the members are hosted at third parties who don't support SSL.
It seems that the changes in core.php in IPB 3.3.x break embedded videos from YouTube, Vimeo, etc... The iframe part seems to break all embedded media video's when you edit a post with a media video. if ( $fixScript )
$txt = preg_replace( '#<(\s+?)?s(\s+?)?c(\s+?)?r(\s+?)?i(\s+?)?p(\s+?)?t#is' , "<script" , $txt );
$txt = preg_replace( '#<(\s+?)?/(\s+?)?s(\s+?)?c(\s+?)?r(\s+?)?i(\s+?)?p(\s+?)?t#is', "</script", $txt );
$txt = preg_replace( '#<(\s+?)?i(\s+?)?f(\s+?)?r(\s+?)?a(\s+?)?m(\s+?)?e#is' , "<iframe" , $txt );
$txt = preg_replace( '#<(\s+?)?/(\s+?)?i(\s+?)?f(\s+?)?r(\s+?)?a(\s+?)?m(\s+?)?e#is', "</iframe", $txt );
} Please notice that a check for script is always good and a script should never be embedded in a user post.
Some issues with the new classPost.php and classPostForms.php on IPB 3.3.4. I get white pages and are not able to post. I compared the files and just applied some fixes I felt necessary. Most webservers also check for exploits and XSS when making use of mod_security, Suhosin and other security additions.
Great to hear that the community forum is the biggest test for IPS4. Even with cache disabled everything seems to work fine and fast from the Netherlands. So I'm really looking forward to experience the new software at full speed with more optimizations and caching enabled.
Why do I need to change my password to login via the forget password procedure and why do I have to add 'security' questions? This almost seems there has been a leak. Is there something IPS is not telling me?
If you guys really value security you should look at Two-step Authentication (eg. Google Authenticator) . It is very easy to integrate in your website and it is actually an extra layer of security because somone actually has to fysical steal a device from you such as your phone or token generator and have to know your password to login. This is very unlikely.
What is likely someone guessing or just Google'ing or check your Facebook for the 'security' answers. It is really easy to find stuff as which movie I like (is on my Facebook) and what my mothers name is. That's why I use fake questions and fake answers and just write them on a piece of paper (also not that secure).
I hope IPS really take a second look at the security. All those horror stories about peoples there Apple/Paypal or Twitter account being hacked has been done thanks to social engineering and just simply Google'ing the answers to security questions. I really think security questions give a false sense of security!
Sorry for the bump. But I think the following works. I'm currently testing it.
ips_password=the password you set for the bot
As far I understand the auth_key is always 880ea6a14ea49e853634fbdc5015a024 for guests.
Don't think this is the right solution. We switched to IP.Chat because it is more reliable and better integrated in Invision Power Board than our previous chat solution.
That won't actually help. Our website already works 100% via SSL including the chat page. BUT the actual chat requests to for example http://server07.ips-chat-service.com/ are still unencrypted.
I would love to see the chat service encrypted. If it was possible to host IP.chat completely on our own servers it would have been available via encrypted connection for a long time.
Thanks for the positive reply. I understand that IP.Chat is a relatively new service. A lot of the software of Invision Power Board has changed.
But also a lot on the Internet and the world has changed. Now you can get free unencrypted WiFi at buses, trains, pubs, etc...
Also more and more companies and government agencies are interested in data for data mining purposes. Of course we can discuss if it is a good or bad thing that everybody can listen to what we are saying in a private chat, but than we can just keep talking about all kind of Orwellian stories.
The point is that it is rather easy to integrate SSL security in such a great service. So it would be great to hear some kind of ETA. I would rather want to see this within a few months than within a few years.