Hi people,
I have a sad story for you all. But don't cry much, maybe you can give some idea about what is wrong?
The problem: I can't make any new objects with my KDE applications (except Konsole running bash) having group write bit. I understand, all the new files will be in that way (unless ACL default permissions work), but is much better than readonly. Any idea?

If this one, it fails:
1. open Konsole
2. umask ug=rwx,o=
3. konqueror &
4. create something

Also changing ~/.profile is a sad story for me.

If you cannot create files in your own $HOME, then I would recommend checking the permissions of that folder.
Usually most security sensitive applications ( such as gnupg and ssh ) refuse to use keys unless only the owner can read them.

Is there any particular reason why you need your group to have write access?

KarlisRepsons wrote:Hi people,
I have a sad story for you all. But don't cry much, maybe you can give some idea about what is wrong?
The problem: I can't make any new objects with my KDE applications (except Konsole running bash) having group write bit. I understand, all the new files will be in that way (unless ACL default permissions work), but is much better than readonly. Any idea?

If this one, it fails:
1. open Konsole
2. umask ug=rwx,o=
3. konqueror &
4. create something

Also changing ~/.profile is a sad story for me.

I had a similar problem and broke down and used fmask and dmask in fstab.

I don't know if that will work for you, but I got it to work for me that way.

ww1065 wrote:I had a similar problem and broke down and used fmask and dmask in fstab.
I don't know if that will work for you, but I got it to work for me that way.

By reading man mount, I see it only works for vfat filesystem!
Maybe you know some developer in here, who might know?
And yes, I need group write permission. There is no group write in some of higher level directories (including /) above my used one, but should it mean there is no for new objects in it? I don't think that. In bash I can do things well as I wrote!
And yes: why are people scared of group writes? It is one of trivial policies: allow them or not. In my case I need to allow...

Anyway, it makes quite a problem, because, if whole system has been started up with one of policies, it affects everything that is created. No way to sepparate, except ACLs, which in turn might cause problems for tar backups and who knows what else.
Maybe some link to more expanded toughts with some propositions?

You may find this page here of help http://www.cyberciti.biz/tips/understan ... usage.html

It would be much better, if I knew a clear answer to this: if I set an umask in bash and then run KDE app, why isn't it taking that umask like console programs (mkdir, touch...)? Maybe someone hard-coded it for security reasons?

/note, I think, I tried those things already/