Location: NJ, USA
Born: 27 January 1989
Do NOT PM me for support on this board. Please use the proper forums, thanks!
Test: No Information
Last Seen: Today at 12:07 am
Local Time: Mar 25 2017, 04:37 AM
36935 posts (9.4 per day)
( 17.51% of total forum posts )
Mar 16 2017, 11:27 AM
Timeline (all times in EDT)
- March 16, 2017 at 6:20AM we experienced a service interruption.
- March 16, 2017 at 8:48 AM we became aware of the downtime
- March 16, 2017 at 8:50 AM we identified the problem as an issue with our network server at Level3 Communications and not the server with the board data.
- March 16, 2017 at 9:04 AM we were in contact over the phone with Level3 and techs were already working on the issue to find the root cause
- March 16, 2017 at 11:00 AM a data-center based outage was confirmed; our systems were not specifically problematic in any way.
- March 16, 2017 at 11:52 AM Service was restored.
- March 16, 2017 at 12:11 PM we received notice that "there was an outage in the LA datacenter and a failed PDU had to be replaced. [...] and should be back to normal now."
We apologize for the inconvenience and thank for your patience. We also apologize for the slightly delayed response; and will look into why our notifications did not fire more than once for this incident.
We will be monitoring the server closely throughout the day to ensure it is OK. Let us know if you have any further questions or concerns.
Mar 10 2017, 10:26 PM
Jcink Forum Hosting is now offering HTTPS "BETA" to all free and premium users via the *.jcink.net subdomain.
If you use HTTPS, this means all traffic between your browser and the server will be encrypted and cannot be monitored by a 3rd party. While this is not
so important for browsing from your home internet connection, it is essential to be secure if you are using public wifi or a similar public internet connection.
You can start browsing our forums and site by accessing:https://forum.jcink.nethttps://jcink.com
A full article on HTTPS has been posted here:https://jcink.com/main/wiki/https-encrypted-browsingHTTPS is a "BETA" feature within our service and is under development.
Comments, questions, and development news regarding this feature will be posted in our dev forum topic here:https://forum.jcink.com/index.php?showtopic=27295
Thank your for your patience and we're looking forward to serving you with HTTPS
Feb 11 2017, 09:28 PM
This is an "under the hood" update that's been in the works for a while, and will, for the most part, be uneventful. However it does deserve to be mentioned because I want people to use it when it's finally openly available. For some time I have been working to change the password encryption scheme used on JFH to be more modern.
Presently, we use something called MD5
, which is a 32-character
hash of your password. The upgrade I have installed changes the system to bcrypt
-- a 60-character hash
, that is more future proof and its strength can be dynamically adjusted. In short: bcrypt is much better for us/your board.
This change, however, is not automatic. The upgrade must be done on a per-board basis. I'll make this as easy as clicking a button in the Admin CP that says "upgrade me" or something like that in the future, but at the moment this is in testing phase.
To start, it's been enabled on the support board, so this topic is for feedback regarding that. I would like to hear about any incidents where you were unable to login to here. There should not be any, and I have already noticed that users logging in are having their hashes changed to the stronger system without even realizing it / knowing it (that's good!)
This topic will also be for questions regarding this update as well. Should the support board trial continue to go well, I would like to find some other boards to upgrade as well. Let me know here if you'd be interested.
Once again, this update is extremely transparent. If you've logged out and logged in here recently, you are using a bcrypt-password and don't even notice it.
Feb 7 2017, 09:15 PM
Google Chrome has recently rolled out Chrome v56. The significance of this release is as follows:Starting January 2017, Chrome 56 will label HTTP pages with password or credit card form fields as 'not secure,' given their particularly sensitive nature
Therefore, the Admin CP and and anywhere on your forum that might include a password form (such as the log-in page, quick login) will display a "Not Secure" notice in the address bar.
This does NOT
- Your board can be "hacked" or exploited at the software level.
- Your credit card details will be stolen (we don't even store or process credit cards - not even for Premium!).
- Your password will, most certainly, be stolen by the Boogie man or Troll who lives under the bridge.
What it does
mean is that if you don't trust the connection between yourself and your internet provider, you should exercise caution about logging in. This has always
been the case in the past 10+ years the service has been around. Generally speaking, if you're not using sleazy public wifi, you are going to be just fine as you always have been.
HTTPS (secure) support is
on our list of priorities, however, as it would still add a good benefit to the forums to encrypt everything. Unfortunately, it will not likely be fully ready this year. We have thousands of forums, and will have to do proper testing and implementation -- domain owners will absolutely not be able to take advantage of it right away either, since each domain name will require its own individual certificate. So, SSL is not just a "switch" that we can turn on and off with ease. The internet, is indeed being 'pushed' toward all-SSL whether the data on the website is required to be confidential or not. We are aware, it is in the works, it will just take time.
We hope this helps to clarify this message that some of you are seeing, and as always, thanks for your continued support.
Active: Yesterday at 10:13 am
Active: Mar 17 2017, 04:01 PM
Active: Nov 27 2015, 09:23 PM
Active: Feb 9 2014, 09:31 PM
Active: May 27 2013, 06:47 AM