Page 4 of 4 FirstFirst ... 234
Results 31 to 36 of 36

Thread: tty 2 question

  1. #31
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: tty 2 question

    Quote Originally Posted by bhubunt View Post
    The problem is that I am locked in a tty2 session and that I can't move to another session.

    I think your first guess that "something is a foul" was on the mark.

    Is there other code to check what is going on?

    I get the feeling that I am not in control of this tty feature on my personal laptop of which I am the sole user.

    So is there a way in which we can check if I do not have the necessary privileges to navigate out of a tty?

    What are the command lines to do such checks for (limited) privileges for ttys?
    No not really, but do you recall using any of the two I list below?

    vlock: (it is in the repos of most distros),
    • Virtual Console locking program
    • vlock either locks the current terminal (which may be any kind of terminal, local or remote), or locks the entire virtual console system, completely disabling all console access. vlock gives up these locks when either the password of the user who started vlock or the root password is typed.

    Wolud you remenber using that?
    Code:
     vlock --help
    vlock: locks virtual consoles, saving your current session.
    Usage: vlock [options]
           Where [options] are any of:
    -c or --current: lock only this virtual console, allowing user to
           switch to other virtual consoles.
    -a or --all: lock all virtual consoles by preventing other users
           from switching virtual consoles.
    -v or --version: Print the version number of vlock and exit.
    -h or --help: Print this help message and exit.
    Next there is bashlock: https://github.com/acornejo/bashlock

    bash script to lock the console.

    It requires the password of the calling user to unlock the console. This utility is similar in spirit to vlock, the only reason it exists is because vlock was unavailable for OS X.

    The main purpose of bashlock is to be used as a lock-server inside tmux. This allows you the user to lock tmux sessions.
    Dependencies
    • bashlock has very few dependencies, namely:
    • bash
    • expect
    • su



    I must say this is a first seeing what you now report.

    For me a solution would be a wipe and re-install.
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags | System-info | Forum Guide lines | Arch Linux, Debian Unstable, FreeBSD

  2. #32
    Join Date
    Mar 2019
    Beans
    215

    Re: tty 2 question

    Hi,

    Your comments and commands have been incredibly helpful.

    To answer your question: "do you recall using any of the two I list below?"

    No. Never.

    I also never launched tty2. As mentioned, I only recently discovered I was logging into a tty2 session and that I had been locked into it since October of last year.

    The unsolved question: how did I end up in a tty2 and why is it locked?

    You are probably right in suggesting inter alia that my system is compromised and that I need to reinstall ubuntu.



    Quote Originally Posted by 1fallen View Post
    No not really, but do you recall using any of the two I list below?

    vlock: (it is in the repos of most distros),
    • Virtual Console locking program
    • vlock either locks the current terminal (which may be any kind of terminal, local or remote), or locks the entire virtual console system, completely disabling all console access. vlock gives up these locks when either the password of the user who started vlock or the root password is typed.

    Wolud you remenber using that?
    Code:
     vlock --help
    vlock: locks virtual consoles, saving your current session.
    Usage: vlock [options]
           Where [options] are any of:
    -c or --current: lock only this virtual console, allowing user to
           switch to other virtual consoles.
    -a or --all: lock all virtual consoles by preventing other users
           from switching virtual consoles.
    -v or --version: Print the version number of vlock and exit.
    -h or --help: Print this help message and exit.
    Next there is bashlock: https://github.com/acornejo/bashlock

    bash script to lock the console.

    It requires the password of the calling user to unlock the console. This utility is similar in spirit to vlock, the only reason it exists is because vlock was unavailable for OS X.

    The main purpose of bashlock is to be used as a lock-server inside tmux. This allows you the user to lock tmux sessions.
    Dependencies
    • bashlock has very few dependencies, namely:
    • bash
    • expect
    • su



    I must say this is a first seeing what you now report.

    For me a solution would be a wipe and re-install.

  3. #33
    Join Date
    May 2008
    Location
    United Kingdom
    Beans
    5,274
    Distro
    Ubuntu

    Re: tty 2 question

    Quote Originally Posted by bhubunt View Post
    The unsolved question: how did I end up in a tty2 and why is it locked?
    The first part was answered earlier: This has been the default in Ubuntu for some time. By default, you are logged into tty2. Nothing strange about that.

    The second part, why is it locked, we still haven't managed to figure out.

    Did you try the suggestion by @tea for one, i.e. to use the Fn key on your laptop?

    If you have tried, and it still doesn't work, check if you have vlock or bashlock installed (as per @1fallen's idea):
    Code:
    type vlock
    type bashlock
    What we're hoping is that neither is installed.
    Always make regular backups of your data (and test them).
    Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.

  4. #34
    Join Date
    Mar 2019
    Beans
    215

    Re: tty 2 question

    To 1fallen --

    unfortunately, while I was reporting here on this forum about tty2, my system was breached again.

    when I typed in the command "last" just now, I noticed that my entire booting history since Aug 29 2023 (=wtmp) was wiped clean this morning, including the mysterious tty2 log in on October 19 2024 that I never launched.

    This is all that is left now when I type in "last"

    Code:
    me-ThinkPad-X240:~$ last
    
    me  tty2         tty2             Sat May 18 11:50   still logged in
    reboot   system boot  6.5.0-35-generic Sat May 18 11:50   still running
    me  tty2         tty2             Sat May 18 09:35 - 09:57  (00:21)
    reboot   system boot  6.5.0-35-generic Sat May 18 09:35 - 09:57  (00:22)
    me  tty2         tty2             Sat May 18 07:29 - 09:34  (02:04)
    reboot   system boot  6.5.0-35-generic Sat May 18 07:28 - 09:34  (02:06)
    
    wtmp begins Sat May 18 00:00:41 2024
    Everything else is gone.

    NOTE

    I just marked my thread as "solved," as the issues I have been reporting about on this thread are the result of a system breach. I have had system breaches in the past, about which I am meeting with a lawyer. Thanks especially to 1fallen for the expert input. It's appreciated.


    Quote Originally Posted by bhubunt View Post
    Hi,

    Your comments and commands have been incredibly helpful.

    To answer your question: "do you recall using any of the two I list below?"

    No. Never.

    I also never launched tty2. As mentioned, I only recently discovered I was logging into a tty2 session and that I had been locked into it since October of last year.

    The unsolved question: how did I end up in a tty2 and why is it locked?

    You are probably right in suggesting inter alia that my system is compromised and that I need to reinstall ubuntu.
    Last edited by bhubunt; 3 Weeks Ago at 12:48 PM.

  5. #35
    Join Date
    May 2008
    Location
    United Kingdom
    Beans
    5,274
    Distro
    Ubuntu

    Re: tty 2 question

    Quote Originally Posted by bhubunt View Post
    the issues I have been reporting about on this thread are the result of a system breach.
    That sucks. I hope that you manage to sort out everything.

    Back up your data (and check the backup), then reinstall from scratch using a freshly-downloaded ISO from a non-contaminated computer.
    Always make regular backups of your data (and test them).
    Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.

  6. #36
    Join Date
    Apr 2011
    Location
    Mystletainn Kick!
    Beans
    13,685
    Distro
    Ubuntu

    Re: tty 2 question

    Thread closed by the OP's request.
    Splat Double Splat Triple Splat
    Earn Your Keep
    Don't mind me, I'm only passing through.
    Once in a blue moon, I'm actually helpful
    .

Page 4 of 4 FirstFirst ... 234

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •