It took me a while to figure out what was happening, but after a couple days of running into repeated "403 Forbidden" errors on my web host's server, I noticed that every time I open and edit a file over sftp, Kate changes the permission bits to 600.

Why? This is so weird.

I've read similar issues online, where other users suggested setting up umask or ACL, but I'm not sure that's the appropriate solution. Setting umask to 022 in my .bashrc file didn't fix the problem, for one thing. And from what I've read about setfacl it seems very similar to chmod. Right?

Reproducible: Always

Steps to Reproduce:
1. To verify this, I started by creating a test plaintext file. 
2. I checked the permission bits, which defaulted to 644. 
3. I edited the file in Kate (which never changes the permission bits of files on my local system).
4. I refreshed the sftp folder and checked the permission bits again -- and for some reason it changed to 600.

Other experiments: 

* I tried this process again with gedit, but it didn't change the file permissions. 
*I've mainly been using Nautilus File Manager for SFTP access; I tried the experiment one more time, using Kate again, but this time accessing SFTP with FileZilla, and this also fails to change the file permissions. 

Strangely, the problem only seems to happen when I'm using both Nautilus as my SFTP client and Kate as my text editor.
Actual Results:  
Kate changes the remote file's permissions to 600, while using Nautilus for SFTP access.

Expected Results:  
Kate should preserve the file permissions it receives, no matter the SFTP client used.