- #Peter upfold dfontsplitter install
- #Peter upfold dfontsplitter update
- #Peter upfold dfontsplitter full
- #Peter upfold dfontsplitter software
Unfortunately, because the automatic update feature is new, previous users of DfontSplitter 0.2 are not going to be notified automatically about this new release.
#Peter upfold dfontsplitter software
This makes my development of the software easier, as I can release smaller feature releases more frequently, rather than large releases that must have a longer lifespan. Like the Mac version, which uses the excellent Sparkle Framework, users of DfontSplitter for Windows can now keep the application up-to-date without having to manually check the website. The main change here is a brand new automatic update notification system. I have just released a new version of DfontSplitter for Windows, version 0.3. FontForge is one option for this.Īs always, you can always get the latest and greatest version of DfontSplitter by downloading it from the the DfontSplitter project page. Some fonts still require further conversion after DfontSplitter has created the TrueType font file.More fonts should now convert correctly without requiring further intervention. Uses a new method to decrease the incidence of ‘invalid font file’ errors on Windows.Here are the official release notes: New Features and Bugfixes This means users will less frequently have to go through a secondary hoop to get Windows to play nicely with DfontSplitter’s outputs. For some unknown reason, sometimes Windows simply will refuse to work with the original fondu output file, but if simply DfontSplitter makes a duplicate of the file, it will happily see it as a TrueType font! It is very odd behaviour, and this fix only works in some cases, but it should reduce the incidence of ‘corrupt font files’ being output from DfontSplitter for Windows. This version includes a single fix, introducing a new method of avoiding the dreaded ‘corrupt font file’ error. Hot on the heels of yesterday’s auto-update-capable release, is DfontSplitter for Windows 0.3.1. “What? I thought you updated this yesterday?” Once I figure out a cipher suite configuration that I am happy with, and understand, in Pound (my reverse proxy acting as the TLS terminus), I will update the app again to require forward secrecy.
The astute among you may note that in the ist for this update, I explicitly disable the OS X 10.11 SDK’s check for HTTPS forward secrecy in the HTTPS communications to the update server. I had somehow missed the original reporting of the vulnerability, so I particularly appreciate Kevin bringing this to my timely attention. Thanks to Kevin Chen for pointing out the existence of the issue with Sparkle and that it affected DfontSplitter.
#Peter upfold dfontsplitter install
The automatic updates feature within DfontSplitter should detect the update, but you can also download and install it manually. Due to new build requirements in Xcode 7.2, the application now requires at least OS X Snow Leopard (10.6) and a 64-bit Intel processor. This update fixes the Sparkle-related security issue by updating Sparkle and requiring HTTPS for all future DfontSplitter app update communications.
#Peter upfold dfontsplitter full
More details and a full breakdown are at the post on Vulnerable Security. Due to the context that the WebView runs in, the app could then be convinced to run local files, expose local files to a remote server and even execute arbitrary code. The vulnerability means that in a scenario where an attacker could launch a man-in-the-middle attack during a Sparkle-enabled app’s update detection process, arbitrary JavaScript could execute in the WebView hosting the release notes. (It was more than five years ago when the last release was made!) As of 0.4.2, the update pages are now, naturally, served over HTTPS. This is a critical security update that fixes an issue relating to the Sparkle software update framework when the update pages are served over HTTP.
Today I release DfontSplitter 0.4.2 for Mac.
0 kommentar(er)
