Jump to content
Storyist Forums

Search the Community

Showing results for tags 'encryption'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Storyist for Mac
    • Announcements
    • Using Storyist
    • Feature Requests
    • Troubleshooting
    • Sharing
  • Storyist for iPad
    • Announcements
    • Using Storyist for iPad
    • Feature Requests
    • Troubleshooting
  • Community
    • Novel Writing
    • Screenwriting
    • Writing Resources
    • General Topics
    • Member Introductions and News
    • Writers' Lounge
    • NaNoWriMo 2007
    • NaNoWriMo 2008
    • NaNoWriMo 2009
    • Script Frenzy 2010
    • NaNoWriMo 2010
    • Script Frenzy 2011

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Resurrecting a feature request from 2008 (!) here: http://storyist.invisionzone.com/index.php/topic/413-password-protection-for-storyist-files/ Since we have an iOS flavor of Storyist now, and since it is conceivable (via Dropbox integration) that Storyist file contents could be illicitly accessed by third parties, I'd like to see a setting that lets users activate encryption on their files. There are stacks and heaps of good encryption algorithms out there; a nice strong one might be Blowfish, and I believe that OSX/XCode have Blowfish algorithms built in. The way I envision it working is this. On a project level, the user can choose to encrypt the whole project, and is prompted for a password/key when this is first invoked. Thereafter, any time the project is opened in Storyist on Mac or iOS, the user is again prompted for the password. To disable the encryption, the user would open the project and choose to disable encryption. The user should be prompted to enter the password one last time before encryption is disabled, to prevent a third party disabling it on a previously-open file that the legitimate user forgot to close (does that make sense?).
  2. Julian Assagne, Wikileaks and Edward Snowden have proved me right. Sensitive information needs to be encrypted and You programmers must make sure there are no backdoors. Ask Your granddads why they fought the nazis. I have written something similar before but could not continue because I forgot my password.
×
×
  • Create New...