Thanks! For my part, I will continue messing with the passphrase until I get something that is KDE-kompatible (ha ha ;-). Then if I can go back over 100 characters in the future, I will. I still have to sort out my password security scheme in full, anyway. It's a bit of a mess right now.
I've often wondered how much good extra long/perceived complexity actually does from an algorithmic perspective, seeing as there might be truncated feedback rounds or salts or what have you. So if it ends up that 100+ is silly at any rate, then I'd rather just pick something effectual. Curtis On Thu March 25 2004 12:50, Aaron J. Seigo wrote: > On March 25, 2004 09:15, Curtis Sloan wrote: > > On Wed March 24 2004 10:11, Aaron J. Seigo wrote: > > > On March 24, 2004 09:29, Curtis Sloan wrote: > > > > <snip> > > > > > > 1) My passphrase contains plenty of extended ASCII characters (~, |, > > > > <, etc.) and is quite long (over 100 characters). Could be related > > > > to the passphrase. > > > > > > probably is. if this set up worked with a previous version, then the > > > problem is in KMail somewhere and i'd be happy to troubleshoot it in > > > the sourcecode. if not, does your passphrase work from the command line > > > or from other PGP tools such as KGpg (also comes with 3.2)? > > > > Tested KGpg last night, it doesn't work either. :-( Is there any way to > > escape the offending characters? > > you said it's over 100 characters? well.. i know why it isn't working: > > const int KPasswordEdit::PassLen = 100; > > anything over 100 characters gets discarded... i'll deal with this shortly > ... _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
