[Looking for Charlie's main web site?]

Understanding the 9.0.2 release of ColdFusion, a FAQ for those who missed the news last year

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
So perhaps you're currently running CF 9.0 or CF 9.0.1, and you may have noticed that there is a CF 9.0.2. Have you wondered what it's about? And have you noticed that it's not something you can just update to from 9.0 or 9.0.1? It's a complete installer, meaning you need to uninstall CF 9.0 or 9.0.1 before you can move up to it.

Should you? What do you gain? what do you lose? what are some gotchas? That's what this blog entry is about, answering the following questions:

  • First, what is ColdFusion 9.0.2? Why did Adobe create it?
  • What about the 9.0.1 updater? Can we still get that? Yes.
  • So what all does 9.0.2 add and remove?
  • If I download CF 9 today, what do I get?
  • "But if I download 9.0.2 today, I get the latest version of it available, right? I don't need to add hotfixes, do I?" Wrong.
  • Warning: DO NOT install 9.0.1 atop 9.0.2 (nothing will stop you)
  • If I am on 9.0 or 9.0.1, how can I get to 9.0.2?
  • Why might I want to get to 9.0.2 from 9.0 or 9.0.1?
  • How did i miss this? Was 9.0.2 discussed? Yes it was.

[....Continue Reading....]

Tracking ColdFusion sessions within FusionReactor, by way of FREC logging

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Someone asked on the FusionReactor mailing list (a Google Group) whether FusionReactor tracked CF sessions. I started to write a reply, with the good news/bad news in answer to that, and as sometimes happens, it became long enough that I thought it might be better suited as a blog entry that I could point to from the list instead, and which may also help those not on the list (which is a great resource, as a low-volume list with a high signal to noise ratio.)

Anyway, here is the answer I wanted to offer to that question...

[....Continue Reading....]

ColdFusion 10 WACK book contributors (myself included) now listed at Amazon

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
By now most should know that a new CF10 version of the classic Web Application Construction Kit (or WACK) series was released some months ago:

Adobe ColdFusion Web Application Construction Kit: ColdFusion 10 Enhancements and Improvements

But some may not have known who the contributors were, because since its release the Amazon site for the book had listed only Ben (Forta). Doh! :-)

Ben is indeed the series editor and a fellow contributor--and truly the glue that has held the project together since the first edition for CF3 in 1997.

But as with each edition since the first, there are indeed multiple contributors.

Amazon book page now lists all the contributors

And now the Amazon page does list all the co-authors:

Charlie Arehart, Rob Brooks-Bilson, Raymond Camden, Ken Fricklas, Hemanth Khandelwal, and Chandan Kumar.

Of course, we were indeed properly listed on the front cover, for those who may have looked--and in that same alphabetical order, whereas the Amazon site order is a bit random. Anyway, it's just nice to see this issue fixed.

Problems like that just happen sometimes, and I'd only I noticed it this week and raised it to Amazon. To their credit they were quick to update it.

And I thought some of my co-authors and perhaps others in the community might want to know about it.

Glad to mention the book

Indeed, I've been meaning simply to announce the book and my involvement here myself but got behind on many such news items, as I've just been busy (with my ColdFusion troubleshooting consulting services). Busy is good, of course!

So this was a good chance both to share the above news of the correction for any who'd noticed the issue, and to mention my involvement with the book, in case that and news of the book itself may interest some of my readers. (FWIW, I was a contributor to all 3 vols for CF 8 and 9 also, and I do thank Ben for including me in these works.)

A bit about the book

For those who hadn't noticed the book yet, it's unique in the series in that we decided to go with just a single book, just about the updates. In the past, we instead updated all 3 books throughout. There are pros and cons to either choice, of course, but I do agree that the single book was the way to go.

FWIW, I did chapters 8, 10, and 19.

I was especially delighted to get in a chapter at the end on "hidden gems", as I have loved doing (as article or talks) for each release starting with my first CFDJ article on CF 4.0. The editors chose for Chapter 19 the more sedate name of "Miscellaneous Enhancements", but I'm just thrilled we got to add the chapter at all. :-)

You can learn more about (and buy, and review) the book here:

"Use UUID for cftoken" in ColdFusion Admin does always not block use of 8-digit cftokens

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
This topic came up on a discussion list, in the context of a larger thread, and I wanted to share here what I said there.

As an update since I first wrote this, it turns out this issue may or may not affect you depending on a couple of variables, which I will discuss, with a prefix of "update:" below. But don't dismiss this thinking you are not affected. I would propose that still far more CF servers may be exposed than not, as I will explain.

The CF Admin has (for several releases) offered an option called, "Use UUID for cftoken" (in the "Settings" section), and it's been intended as a security measure. Its purpose is to cause CF to use a UUID value (a long, complex string of numbers and letters) for the CFTOKEN cookie (and session variable) that CF generates, versus what used to be a simple, 8-digit value. This cookie, along with the simpler and incrementing CFID, is used to connect users to the session and/or client scope values created for that user in CF code.

Some may be surprised to learn, though, that while this setting DOES cause CF to *create* such UUID-formatted CFTOKEN values for requests that do not already present a CFTOKEN cookie, it does NOT necessarily cause CF to block any continued use of such simple, 8-digit cftoken cookies.

In other words, browsers which had visited your site before you turned on "use uuid for cftoken" would still send the 8 character cftoken they already had, not a uuid, and that could be accepted as valid by CF, even with that setting on, under certain conditions. (And the user will not be sent any new cftoken cookie in a UUID format, in CF's response, in those conditions.)

There's good and bad news related to this fact, which I will elaborate on below.

Update: Since writing this entry, I learned of a couple of factors that influence if and when this is a problem.

  1. It turns out that if you are using CF10, or CF9 or 8 with the "session fixation" hotfix (APSB11-04), then the problem only happens until you restart CF. The Admin does not currently warn you of this, so beware that you will have the exposure below until you do restart. (If you have added one of the later security hotfixes or cumulative hotfixes that came out since then, then you have gotten the fix.) This fix causes CF to create a new UUID-based CFTOKEN, if you turn on this feature at least (and after a restart) when a browser presents a previously created 8-digit cftoken.
  2. On the other hand, even if you are running CF 10, or running 8 or 9 and HAVE applied that hotfix, note that if you TURN OFF that fixation protection (by adding the -Dcoldfusion.session.protectfixation=false value to your jvm.config, as discussed in that technote), then you are back to the state that I discuss below.
  3. And of course, if you are on CF 8 or 9 and have NOT yet applied that APSB11-04 hotfix (or a later cumulative one that includes it), then you are indeed still vulnerable.

So that leaves still many people who could be affected by this. Even if it seems you may not be, you may want to continue reading this entry to understand what the issue is about, for you and others who may be impacted by it.

[....Continue Reading....]

How to create a "new file" in ColdFusion Builder without use of a project

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
A newcomer to ColdFusion Builder (coming from Dreamweaver) expressed frustration on the Adobe CFBuilder forum about the challenge of doing something as simple as creating a new file--without having to name it first, and when not using "projects".

I offered a reply, both explaining why CFB has a project-oriented nature (being an Eclipse-based product) and also how they could be seen akin to DW "sites". Still, I appreciate the difference and the challenge to newcomers.

But most important, I explained how the Aptana plug-in built-into CFB does indeed offer a solution for him, in its "Untitled Files" feature, easily accessed from the File>New dialog. This would let him create a new file without need of either naming the file first or picking a project (whether when creating the new page or when saving it).

It's not an obvious solution, but I show how it can be made to be easily accessible with a single keystroke.

Rather than repeat myself here, I'll just point interested readers to the forum thread, "Creating a new file". Perhaps others will share more insights after mine, and feel free to leave comments here or there as you see fit.

Speaking at Atlanta ColdFusion User Group tonight on 2 important topics

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Just wanted to note that I'll be speaking tonight at the Atlanta CFUG on two important topics:

For more details on the talks, or to get the slides once I post them (likely right after the meeting), please see the links for the two sessions above.

And if you may want to attend, please RSVP.

I may offer these later on the Online ColdFusion Meetup or perhaps one of the remaining CF conferences this year, if I may be selected to speak.

Java now has a built-in expiration date. What that's about (not obvious at first)

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
If you may have looked at the release notes for the latest (as of this writing) JVM update (Java 1.7 update 21), you may have noticed that it refers to an "expiration date" for this version of the JVM. What's that about, you may wonder?

[....Continue Reading....]

Getting around "Invalid screen name or password" error adding comments to Adobe ColdFusion docs

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Hopefully folks know that one can add comments to the documentation on the Adobe ColdFusion docs pages (like that for the the CF9 Developer guide or the CF10, by clicking the "discuss" link at the bottom of any documentation page. You'll be asked to login with a valid Adobe id.

But have you ever found that when you tried that, you get:

Invalid screen name or password. Please try again.

...even though you KNOW that you're entering the right id? Indeed, one that has been used before?

Perhaps it also happens on other Adobe site properties, and the trick I propose may work for you, also.

[....Continue Reading....]

CF911: New Adobe document about ColdFusion security hotfixes: required reading, I'd say

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Here's a new document from Adobe (new as of last week, it seems) that you may have missed, but which I would argue is REQUIRED READING for all CF admins and developers:

Important hotfix-related notes for ColdFusion 9 and ColdFusion 10

What is this about? and why is it important? Read on below, as the document itself and current links from Adobe don't quite convey its significance, I think. For more perspective, I discuss below both what has happened to many folks after applying ColdFusion security hotfixes in recent years, and how this document helps.

[....Continue Reading....]

Solving seeming ColdFusion / MySQL 5.6 incompatibility, by updating CF's MySQL driver

Note: This blog post is from 2013. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
If you're running ColdFusion 10 (and perhaps also CF 9 or earlier), you will find that if you update your MySQL installation to version 5.6, you'll get the following error from any SQL you try to run from CFQUERY (and perhaps other CF querying tags, like CFSTOREDPROC):

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT'

Summary: There is a reasonable explanation and a rather simple solution: update the MySQL driver that CF is using to at least version 5.1.22 of the driver, the first to support MySQL 5.6, because the one built into CF 10 (driver version 5.1.17) not only does not. More important, that older driver uses something that causes the failure above in 5.6.

That explanation of the "solution" may be enough for some to take the ball and run with it (and if not, I will offer more details on how to do that), though it should be noted that updating the driver is not formally supported, nor is MySQL 5.6 technically supported at all in CF10 (or 9). But for those who will press on knowing that risk, you now know what you need to do.

But as often, there's much more to this than meets the eye, so I hope you will follow along to learn more. I have broken this into two parts:

  • the problem (with what I hope is helpful explanation of what the real root of the problem is),
  • who's to blame (not Adobe, I will argue)
  • and the solution (with some caveats that even experienced folks, or those who don't care about "the problem", should still read.

And again, while I discuss this in the context of CF10, where I've seen the problem happen, it could apply also to CF9 (and it seems reasonable that it would), so all the information still applies, it would seem.

[....Continue Reading....]

More Entries

Copyright ©2024 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting