| 1 |
On Tue, 17 Mar 2015 20:39:46 +0200 |
| 2 |
Matti Nykyri <matti.nykyri@×××.fi> wrote: |
| 3 |
|
| 4 |
> > On Mar 17, 2015, at 19:33, German <gentgerman@×××××.com> wrote: |
| 5 |
> > |
| 6 |
> > On Tue, 17 Mar 2015 19:16:42 +0200 |
| 7 |
> > Matti Nykyri <matti.nykyri@×××.fi> wrote: |
| 8 |
> > |
| 9 |
> >>>> On Mar 17, 2015, at 18:11, German <gentgerman@×××××.com> wrote: |
| 10 |
> >>>> |
| 11 |
> >>>> Don't hit your head to a brick wall. A small strace to the login process reveals that login set things as you tell it to in /etc/login.defs |
| 12 |
> >>>> |
| 13 |
> >>>> In this file change the line: |
| 14 |
> >>>> TTYPERM 0600 |
| 15 |
> >>>> To: |
| 16 |
> >>>> TTYPERM 0620 |
| 17 |
> >>>> |
| 18 |
> >>>> And your problem is fixed. |
| 19 |
> >>> |
| 20 |
> >>> Sorry, this didn't fix it |
| 21 |
> >> |
| 22 |
> >> Yes. Sorry. The mode was wrong: |
| 23 |
> >> |
| 24 |
> >> TTYPERM 660 |
| 25 |
> >> |
| 26 |
> >> Will fix it, if your screen is setgid tty and ttyX is gid tty. If not then: |
| 27 |
> >> |
| 28 |
> >> TTYPERM 666 |
| 29 |
> >> |
| 30 |
> >> Will fix it, but also your tty will be world readable. If you don't consider that too big security risk, then just go |
| 31 |
> > |
| 32 |
> > Neither 660 nor 666 fixed it. Sorry :( |
| 33 |
> |
| 34 |
> If you have: |
| 35 |
> |
| 36 |
> TTYPERM 0666 |
| 37 |
> |
| 38 |
> And logout and login. What mode and ownership do you have in you tty (/dev/ttyX)? |
| 39 |
|
| 40 |
Ok, Matti, 0666 worked, now I can run screen as a user. Thanks. Do you think I have to try to run it 0660? Will it be less security risk? |
| 41 |
> |
| 42 |
> -- |
| 43 |
> -Matti |
| 44 |
> |
| 45 |
> |
| 46 |
> |
| 47 |
|
| 48 |
|
| 49 |
-- |
| 50 |
German <gentgerman@×××××.com> |
Archives