The FutureSmart 4.7.2 firmware release changed the default availability of TLS protocol versions. The updated security profile for FutureSmart version 4.7.2 defaults to:
TLS 1.2 – Enabled
TLS 1.0 & TLS 1.1 – Disabled
The new TLS protocol defaults are applied in the following circumstances:
Devices purchased with FutureSmart bundle 4.7.3 and later
Use the new TLS defaults (TLS 1.0 / 1.1 disabled)
Devices updated to FutureSmart bundle 4.7.2 or later from FutureSmart 3 bundles or FutureSmart 4 bundles before version 4.7.2
TLS settings are not updated to the new defaults and maintain their current setting.
Performing the following device resets on FutureSmart 4.7.2 or later devices update the TLS settings to the new defaults, overwriting any previously configured setting
Important Note: HP and 3rd party solution software may have a TLS 1.0 dependency requiring TLS 1.0 to be enabled / re-enabled for installation or to function properly after installation. Details on how to do that can be found in the document here.
Important Note: FutureSmart bundle 4.7.2 is an interim firmware release only available from HP Support.
The following devices will ship with FutureSmart bundle 4.7.3 which have the new TLS defaults.
Thanks to all those who were able to attend this month's Partner Tech Talk. For those who were not able to attend, the topics were OXPd 1.8 and a preview of some upcoming changes in Embedded Solutions and OXPd.
Slides from the presentation can be found here. Note that we've added a final slide which answers all of the questions that were asked during the Tech Talk.
Finally, we want your feedback on the forum so that we can make any changes to better meet your needs. Please take the quick survey here. Or, if it's easier for you, just send an email to email@example.com.
As communicated at the Partner Conference in May and the Partner Tech Talk in July, the Pagewide P-Series class of printers are designed as lower cost, lower feature offerings that support limited extensibility. As a reminder, Pagewide P-Series products include the A3 devices released last spring: HP Pagewide Managed Color MFP P77440 and P77940/50/60 and HP Pagewide Managed Color P75250.
As a result of this strategy, Pagewide P-series products will not support OXPd solutions. OXPd solutions will continue to be compatible with our PageWide Enterprise class of products. Consistent with prior communication, starting with FutureSmart 4.7, OXPd solutions that may have worked initially on Pagewide P-Series products will no longer be supported. HP wants to ensure you are alerted to this coming change.
October’s Tech Talk was well attended! Topics were:
FutureSmart Release Plans and Performance Improvements
SDK and OPS Extensibility
JetAdvantage Link Update
If you want to refresh your memory on what was covered (or if you missed it), you can find the slides presented here and a link to the recording here. Watch for upcoming “Dev Talks” that will provide more detailed technical content.
As part of Hewlett-Packard’s constant investment in industry-leading security, we are modifying our FutureSmart device firmware to require zip file signing on all embedded solutions. This means that your embedded solution will require an additional signing process to successfully install on LaserJet products. The whitepaper that explains how to complete this process is posted at https://jetadvantage.zendesk.com/hc/en-us/articles/360011195913-Requirem....
1) Current device firmware will ignore the new signature, so you can begin using this process immediately.
2) If FutureSmart device firmware is upgraded on devices with your solution already installed, your current revision solution will not be impacted, since the signature check occurs only at BDL install time.
3) Updated FutureSmart firmware will be available to your customers as early as mid-December. Embedded solution installs made after this change to FutureSmart device firmware will fail unless the zip is signed, per the attached process. Therefore, we recommend that you begin using this new signing process as soon as possible to avoid customer issues.
Note that this does not change the previously communicated plan to deprecate the embedded SKD in the near future. We recommend that all embedded solutions be migrated to other interfaces as soon as possible.
If you have questions that are not answered on the Developer's Portal, please contact Steve Townsley.