(archive)mfaktXapp 1.4 - Page 8

Stef42 · 2012-10-26, 14:56

Quote:

Originally Posted by swl551

Did the SMTP emailer work OK for you?

I haven't tested that functionality, as I'm only using the MfaktXapp for simple stats and distribution work.

swl551 · 2012-10-26, 14:59

Quote:

Originally Posted by Stef42

I haven't tested that functionality, as I'm only using the MfaktXapp for simple stats and distribution work.

You mean you WERE using it!!!

swl551 · 2012-10-26, 15:21

Quote:

Originally Posted by Stef42

I haven't tested that functionality, as I'm only using the MfaktXapp for simple stats and distribution work.

You mention the newest version doesn't work on Win8. do you know of a previous version that worked? If so what was the version number.

thx

kracker · 2012-10-26, 16:05

Quote:

Originally Posted by Stef42

I can run Prime95 fine, I fact it's running right now on some P-1 assignments.

Yeah, P95 worked great on Win8, I think I had to fiddle a bit for mfakto to work, but nothing major.

swl551 · 2012-10-26, 16:09

Quote:

Originally Posted by kracker

Yeah, P95 worked great on Win8, I think I had to fiddle a bit for mfakto to work, but nothing major.

Kracker do you have mfaktXapp working with Win8?

kracker · 2012-10-26, 16:14

Quote:

Originally Posted by swl551

Kracker do you have mfaktXapp working with Win8?

Unfortunately, I don't have Win8 atm, but if I can remember, mfactXapp worked with the exception of send ctrl+c and work distribution (i think)

This was a while ago though.

flashjh · 2012-10-26, 17:11

Quote:

Originally Posted by kracker

Unfortunately, I don't have Win8 atm, but if I can remember, mfactXapp worked with the exception of send ctrl+c and work distribution (i think)

This was a while ago though.

I'll test Win 8 tonight. P95 works fine.

flashjh · 2012-10-27, 05:14

I tested everything that I could in Win8 for the latest version. I did not test the auto scheduling open/close. Everything else worked great. Balancing, work distribution, editing, etc.

Email test is successful on TSL prt 587 for gmail. I could not get SSL to work on 465.

gmail settings I tested:
smtp.gmail.com
Use Authentication: Yes
Port for TLS/STARTTLS: 587
Port for SSL: 465

swl551 · 2012-10-27, 11:29

Quote:

Originally Posted by flashjh

I tested everything that I could in Win8 for the latest version. I did not test the auto scheduling open/close. Everything else worked great. Balancing, work distribution, editing, etc.

Email test is successful on TSL prt 587 for gmail. I could not get SSL to work on 465.

gmail settings I tested:
smtp.gmail.com
Use Authentication: Yes
Port for TLS/STARTTLS: 587
Port for SSL: 465

The .NET smtp client does not handle direct SSL so no surprise it did not work, but TLS did.

Thanks for your time checking Win8 and SMTP.

swl551 · 2012-10-28, 14:45

I have implemented full password encryption of the GIMPS password and the Email password and that part of the 1.6 build is ready for some testing.

1.6 includes
1. Full saving of SMTP information. (GOOGLE to find your email providers SMTP server info)
2. Encryption of passwords.

The next release will have the actual "Stalled Process Detection" system in it which will use SMTP emailer to email you of when stalled processes are detected.

Here are the notes on encryption: (which are also viewable in the app).

Encryption Notes:
Encryption of passwords is done using the .NET System.Security.Cryptography classes.
My implementation uses Rijndael (AES) with 256 bit key length and 128 bit block size.
Being encryption, the process requires a password to encrypt and decrypt, and a SALT to further increase the security.

I created a non-portable password and SALT from items that are part of the logged in user and computer. If any one of these items changes after encryption the decryption will fail. Even having access to the source code could not reverse the encryption due to the usage of a 128 bit GUID that is unique to each user.

Of course after the encrypted data is decrypted it is stored in memory and an attacker that has access to your computer's memory could find the information.

So how safe is it? Very, but not perfect. Perfect would be not storing the information at all, and require you to type the passwords in every time you start mfaktXapp.

For SMTP/Email: If feel that my implementation of encryption is beyond your risk tolerance then please consider setting up a another email account dedicated to nothing other than mfaktXapp.

If you have a GIMPS password already configured you'll get a "cannot decrypt" message on startup. This is because mfaktXapp assumes that string is encrypted. This is by design.

Get from SkyDrive http://sdrv.ms/QsaP9Y

kracker · 2012-10-28, 22:16

This may sound silly, but...

Minimize to tray possible?

2012-10-28, 14:45	#87
swl551 Aug 2012 New Hampshire 2³·101 Posts	1.6 PROTO 2 (Password Encryption) I have implemented full password encryption of the GIMPS password and the Email password and that part of the 1.6 build is ready for some testing. 1.6 includes 1. Full saving of SMTP information. (GOOGLE to find your email providers SMTP server info) 2. Encryption of passwords. The next release will have the actual "Stalled Process Detection" system in it which will use SMTP emailer to email you of when stalled processes are detected. Here are the notes on encryption: (which are also viewable in the app). Encryption Notes: Encryption of passwords is done using the .NET System.Security.Cryptography classes. My implementation uses Rijndael (AES) with 256 bit key length and 128 bit block size. Being encryption, the process requires a password to encrypt and decrypt, and a SALT to further increase the security. I created a non-portable password and SALT from items that are part of the logged in user and computer. If any one of these items changes after encryption the decryption will fail. Even having access to the source code could not reverse the encryption due to the usage of a 128 bit GUID that is unique to each user. Of course after the encrypted data is decrypted it is stored in memory and an attacker that has access to your computer's memory could find the information. So how safe is it? Very, but not perfect. Perfect would be not storing the information at all, and require you to type the passwords in every time you start mfaktXapp. For SMTP/Email: If feel that my implementation of encryption is beyond your risk tolerance then please consider setting up a another email account dedicated to nothing other than mfaktXapp. If you have a GIMPS password already configured you'll get a "cannot decrypt" message on startup. This is because mfaktXapp assumes that string is encrypted. This is by design. Get from SkyDrive http://sdrv.ms/QsaP9Y Attached Thumbnails Last fiddled with by swl551 on 2012-10-28 at 15:13

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
(archive)MISFIT	swl551	MISFIT	584	2013-03-19 20:13
(archive)mfaktXapp 1.1.4 released	swl551	MISFIT	64	2012-09-15 22:08
Archive 2 for Other results (>155)	em99010pepe	Octoproth Search	161	2007-06-08 21:31
Archive 1 for Other results (>155)	ValerieVonck	Octoproth Search	90	2007-03-21 01:01
The Archive...	Xyzzy	Lounge	11	2003-03-31 20:42

2012-10-27, 05:14	#85
flashjh "Jerry" Nov 2011 Vancouver, WA 1,123 Posts	I tested everything that I could in Win8 for the latest version. I did not test the auto scheduling open/close. Everything else worked great. Balancing, work distribution, editing, etc. Email test is successful on TSL prt 587 for gmail. I could not get SSL to work on 465. gmail settings I tested: smtp.gmail.com Use Authentication: Yes Port for TLS/STARTTLS: 587 Port for SSL: 465

2012-10-28, 22:16	#88
kracker "Mr. Meeseeks" Jan 2012 California, USA 878₁₆ Posts	This may sound silly, but... Minimize to tray possible?