released: MISFIT for MFAKTx version 2.11.0 (31-Jan-2017)

[swl551]

Hi,



VERSION 2.11.0
1. Updated all mersenne.org urls to HTTPS
2. changed userAgent to MISFIT xx.xx.x where x is the version number string. This will allow web operators to block old versions if desired
3. removed password from GET when interacting FETCHING or REPORTING


Prior versions will become unusable in the future so you need to upgrade.
Prior versions will become unusable in the future so you need to upgrade.
Prior versions will become unusable in the future so you need to upgrade.
Prior versions will become unusable in the future so you need to upgrade.


Get it here https://1drv.ms/f/s!AlQSl010x-kTilHOi4X0ppszJaWW

[chalsall]

Originally Posted by swl551

Get it here https://1drv.ms/f/s!AlQSl010x-kTilHOi4X0ppszJaWW

Cool.

And this is a learning experience... Once you release code, it's on its own. A bit like children, or chickens, but different.

[potonono]

The topic title says 2.11.0, but the thread text says 2.11.1. It looks like 2.11.0 is the latest version on the linked page, so I assume that's the latest version.

Thanks for your work on this!

[swl551]

Originally Posted by potonono

The topic title says 2.11.0, but the thread text says 2.11.1. It looks like 2.11.0 is the latest version on the linked page, so I assume that's the latest version.

Thanks for your work on this!

Fixed the discrepancy. The version is 2.11.0

Thanks
Scott

[chalsall]

Originally Posted by swl551

Fixed the discrepancy. The version is 2.11.0

Thanks for playing along Scott.

As a young child I used to get the shit kicked out of me for trying to get things correct.

[Mini-Geek]

The rule is now in place to redirect everything to HTTPS. And it broke my MISFIT 2.10.0 (unsurprisingly). It's unfortunate that the built-in update feature was unaware of the new version, I assume this is related to the new hosting location.

For the older versions, is there a way to tell them "go here for the new one", and for the new version, is the auto-update looking in a new place?

[chalsall]

Originally Posted by Mini-Geek

The rule is now in place to redirect everything to HTTPS. And it broke my MISFIT 2.10.0 (unsurprisingly). It's unfortunate that the built-in update feature was unaware of the new version, I assume this is related to the new hosting location.

Just for the record, a MISFIT and GPU72 user just contacted me privately by way of email reporting the same issue.

Please give Scott and Aaron some time to fix this. Software is harder to get correct than most people think. Imagine trying to upgrade an airplane's wing in mid-flight....

[Mini-Geek]

Originally Posted by chalsall

Just for the record, a MISFIT and GPU72 user just contacted me privately by way of email reporting the same issue.

Please give Scott and Aaron some time to fix this. Software is harder to get correct than most people think. Imagine trying to upgrade an airplane's wing in mid-flight....

Okay, thanks! I write software myself, so I can appreciate the difficulties. I figured "nope" was a very possible answer to my inquiries.

[chalsall]

Originally Posted by Mini-Geek

I figured "nope" was a very possible answer to my inquiries.

Perhaps.

Are there any particular questions you are interested in?

[swl551]

Sometime last year I stopped putting my software out on the FTP site because I no longer want to push software over an unencrypted Channel. As you've noticed I'm hosting it on Microsoft OneDrive but I never upgraded the feature that checks for the software upgrade. If the Gimp FTP moves to SFTP or ftps I will, resume using it.

Does anyone know about moving to encrypted FTP?



Thanks Scott

[Mark Rose]

SFTP probably won't happen as that requires an account.

I would use HTTPS.