On Thu, Aug 21, 2014 at 3:48 PM, Bjoern Schiessle <[email protected]> wrote:
> > On Thu, Aug 21, 2014 at 2:34 PM, Bjoern Schiessle > > <[email protected]> wrote: > > > > Yes, I can see the key files are there. (ie filename.key). For the > > newly uploaded file, the keyfile is still carrying its old name. The > > filename was build.sh then when I started to see errors, I thought > > the .sh extension (executable) might be stuck on some permissions, so > > I renamed it from the web interface to buildddd. Now, the buildddd > > file is there, but it's key is still buildddd.sh.key. > > > > Note that other files where there are these encryption errors, the key > > files are there and correctly named. But the error persists. > > > This looks strange, especially that the file changed from "build.sh" to > "buidddd" but the key changed from "build.sh.key" to "buildddd.sh.key". > Don't know why the ".sh" is still there. What's the name of the share > key? > Sorry, I mislead. it's key file has remained the same = build.sh.key. Which server configuration do you have? Operating system, webserver, > PHP version, etc. > Debian Wheezy on a VPS, here are details: Debian Version: 7.6 Webserver apache2 Server version: Apache/2.2.22 (Debian Php: PHP 5.4.4-14+deb7u12 (cli) Owncloud Version: 7.0.1-0, Architecture: all, Maintainer: Jürgen Weigert, installed from repositories of Opensuse build service. Let me know if you need other info. Thanks, Emre
_______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
