InsaneJournal Announcements

Site certificate error

InsaneJournal Announcements

Site certificate error

Previous Entry Add to Memories Tell a Friend Next Entry
Sorry about the expired certificate. Your data is still safe. We will have this resolved shortly

Edit: The site security issues should now be solved. Once again, sorry for the confusion.
  • I had the Your connection is not secure. I had to bypass this crap. lol Thanks for addressing this.
  • Thank you for fixing it!
  • Thank you for the fix and addressing it. Appreciate the open communication each and every time. This is why you rock :)
  • Yesss!

    What shiki said. :)
  • Squeaky, I'm having a problem with comments in my journal. I'll post a comment, but then I get this:

    Error running style: Died in S2::run_code running EntryPage::print(): Excessive recursion detected and stopped.

    I'm using generator style, and friends of mine who are commenting my stuff are having trouble commenting as well.
  • I think the expired certificate is happening again. I keep getting the red "not secure" warning in my URL bar when I post a comment or when I post an update.
    • We have not yet been able to implement SSL on every page on the site. So some pages such as comments don't have SSL on them. Some browsers are putting warnings on any page with a form that does not have SSL.
  • same boat as charlie_otto. the only time i don't get told 'not secure' is at the https://www.insanejournal.com page, any other page on the site always displays 'not secure'
    • We have not yet been able to implement SSL on every page on the site. So some pages such as comments don't have SSL on them. Some browsers are putting warnings on any page with a form that does not have SSL.
  • SQL injection exploit

    just in case wanted to tell you that my antivirus flagged this site when i was commenting with this message and blocked me from commenting because of an "SQL injection exploit" with the explanation:

    SQL injection is a code injection technique, used to attack data-driven applications, in which nefarious SQL statements are inserted into an entry field for execution (e.g. to dump the database contents to the attacker). SQL injection must exploit a security vulnerability in an application’s software, for example, when user input is either incorrectly filtered for string literal escape characters embedded in SQL statements or user input is not strongly typed and unexpectedly executed.

    Since an SQL Injection vulnerability could possibly affect any website or web application that makes use of an SQL-based database, the vulnerability is one of the oldest, most prevalent and most dangerous of web application vulnerabilities.

    In order to run malicious SQL queries against a database server, an attacker must first find an input within the web application that is included inside of an SQL query.

    In order for an SQL Injection attack to take place, the vulnerable website needs to directly include user input within an SQL statement. An attacker can then insert a payload that will be included as part of the SQL query and run against the database server.
Powered by InsaneJournal