Results 1 to 18 of 18

Thread: autologin?

  1. #1
    Join Date
    2014-Jul
    Posts
    55

    autologin?

    is autologin feature is missing in kali for Rpi 3 ?


    i want to get a automatic SSH connection with my Rpi 3
    so the solution i thought is i will use autologin option so that after booting it will log in to a non root user & open SSH service after login in it will also automatically connect to my wifi so that i can access it in lan

    my problem is i dont want to connect keyboard, mouse & monitor to my Rpi again & again
    so i was thinking to use SSh & control it via SSH or VNC using my laptop or desktop...

    can you guys help me with this?
    or can tell any other alternative way ?

  2. #2
    Join Date
    2014-Jul
    Posts
    55
    Tried to edit daemon file

    it didnt worked

    i removed # from autologin line
    then i restarted the Pi still not working

  3. #3
    Join Date
    2014-Feb
    Posts
    299
    I'm not exactly sure what you are even asking for here.

    If you log in via keyboard and mouse and monitor, and set up the wifi connection to be available to "all users"; openssh-server is already installed, running and enabled, so once the machine boots up, it should connect to the wifi network every time and you should be able to ssh in. This has the added bonus of NOT logging in and running the extra processes.

  4. #4
    Join Date
    2014-Jul
    Posts
    55
    Quote Originally Posted by steev View Post
    I'm not exactly sure what you are even asking for here.

    If you log in via keyboard and mouse and monitor, and set up the wifi connection to be available to "all users"; openssh-server is already installed, running and enabled, so once the machine boots up, it should connect to the wifi network every time and you should be able to ssh in. This has the added bonus of NOT logging in and running the extra processes.
    ok bro
    i will try to explain my problem again

    i want to make my raspberry pi 3 portable
    so i was thinking about controlling it with my android device
    but for that i need SSH connection & Raspberry connected to my phone hotspot (or any other wifi)

    but ARM image start ssh service & network manager after login only

    so it means for controlling raspberry pi with my android device
    firstly i have to connect PI with a monitor, keyboard & mouse
    log in to a user
    then SSH service will start...



    i want to skip the login task


    i mean

    i want pi to connect to my hotspot (with saved password) & open ssh without log in..
    so that i can control it directly

    i hope you understood what i am trying to say


    PS
    i didnt tried the your suggestion yet will surely try it after dinner
    and sorry for my bad english :/

  5. #5
    Join Date
    2016-Mar
    Posts
    3
    Quote Originally Posted by yhi View Post
    ok bro
    but ARM image start ssh service & network manager after login only
    Umm... are you sure about that? I have a Pi3 on my desk I reboot and ssh into all the time, and aside from the initial setup to add a non-root user I've never logged into it on the console. NetworkManager and the ssh daemon should come up on boot, no waiting for login.

  6. #6
    Join Date
    2014-Jul
    Posts
    55
    Quote Originally Posted by bearda View Post
    Umm... are you sure about that? I have a Pi3 on my desk I reboot and ssh into all the time, and aside from the initial setup to add a non-root user I've never logged into it on the console. NetworkManager and the ssh daemon should come up on boot, no waiting for login.
    ya i am sure

    wifi and ssh start after i log in

    i have kali in my PC i didnt configured ssh but network manager start on boot & it automatically connect with my wifi before login


    but Rpi is not connecting before log in...
    please help me....

  7. #7
    Join Date
    2014-Jul
    Posts
    55

  8. #8
    Join Date
    2013-Mar
    Posts
    22
    Quote Originally Posted by yhi View Post
    ya i am sure

    wifi and ssh start after i log in

    i have kali in my PC i didnt configured ssh but network manager start on boot & it automatically connect with my wifi before login


    but Rpi is not connecting before log in...
    please help me....
    why you dont use adhoc on RP3 instead hotspot on your Phone ?

  9. #9
    Join Date
    2016-Apr
    Posts
    1
    Auto login
    Open /etc/lightdm/lightdm.conf and find these lineunder [Seat:*]:
    --------------------------------------------------------------------
    #autologin-user=username
    #autologin-user-timeout=delay
    --------------------------------------------------------------------
    Uncoment and change username to your username (in my case root) and delay to 0
    autologin-user=root
    autologin-user-timeout=0
    --------------------------------------------------------------------

  10. #10
    Join Date
    2014-Jul
    Posts
    55
    ^ kolopuci

    already tried it it is not working not sure why..

    @ Mehran

    i want Ri to connect to a wifi without log in as a user
    it works in my pc



    i think its because of network-manager process
    it start before login in PC version but not start before login in ARM version


    what do u think i a right ?

    anyway i am starting again
    formatting my SD card & installing kali arm again on it

    hope this time it will work

  11. #11
    Join Date
    2014-Feb
    Posts
    299
    This isn't a Kali specific issue, but if you want the wifi before you log in, you will need to connect to the wifi network, and then go into NetworkManager's settings and tick the little check box that says "enable this connection for all users".

  12. #12
    Join Date
    2014-Jul
    Posts
    55
    ok finally my problem is solved

    i edited this file
    /etc/lightdm/lightdm.conf


    After uncommenting and changing the other 2 rows under section [Seat:*] now KALI XFCE autologins to root.
    This is how the 2 lines appear now:
    [Seat:*]
    ...
    autologin-user=root
    autologin-user-timeout=0



    i found solution here
    https://forums.kali.org/showthread.p...root-autologin
    thx to that guy

  13. #13
    Join Date
    2016-Feb
    Posts
    19
    Hello,

    I have the same problem. No autologin.
    Fresh install. apt-get update, apt-get upgrade, apt-get dist-upgrade done.
    I couldn't switch on autologin function.
    Could you help me?

    My lightdm.conf file:
    #
    # General configuration
    #
    # start-default-seat = True to always start one seat if none are defined in the configuration
    # greeter-user = User to run greeter as
    # minimum-display-number = Minimum display number to use for X servers
    # minimum-vt = First VT to run displays on
    # lock-memory = True to prevent memory from being paged to disk
    # user-authority-in-system-dir = True if session authority should be in the system location
    # guest-account-script = Script to be run to setup guest account
    # logind-check-graphical = True to on start seats that are marked as graphical by logind
    # log-directory = Directory to log information to
    # run-directory = Directory to put running state in
    # cache-directory = Directory to cache to
    # sessions-directory = Directory to find sessions
    # remote-sessions-directory = Directory to find remote sessions
    # greeters-directory = Directory to find greeters
    # backup-logs = True to move add a .old suffix to old log files when opening new ones
    #
    [LightDM]
    #start-default-seat=true
    #greeter-user=lightdm
    #minimum-display-number=0
    #minimum-vt=7
    #lock-memory=true
    #user-authority-in-system-dir=false
    #guest-account-script=guest-account
    #logind-check-graphical=false
    #log-directory=/var/log/lightdm
    #run-directory=/var/run/lightdm
    #cache-directory=/var/cache/lightdm
    #sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
    #remote-sessions-directory=/usr/share/lightdm/remote-sessions
    #greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters
    #backup-logs=true

    #
    # Seat configuration
    #
    # Seat configuration is matched against the seat name glob in the section, for example:
    # [Seat:*] matches all seats and is applied first.
    # [Seat:seat0] matches the seat named "seat0".
    # [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
    #
    # type = Seat type (xlocal, xremote, unity)
    # pam-service = PAM service to use for login
    # pam-autologin-service = PAM service to use for autologin
    # pam-greeter-service = PAM service to use for greeters
    # xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
    # xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
    # xserver-config = Config file to pass to X server
    # xserver-layout = Layout to pass to X server
    # xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
    # xserver-share = True if the X server is shared for both greeter and session
    # xserver-hostname = Hostname of X server (only for type=xremote)
    # xserver-display-number = Display number of X server (only for type=xremote)
    # xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
    # xdmcp-port = XDMCP UDP/IP port to communicate on
    # xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
    # unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
    # unity-compositor-timeout = Number of seconds to wait for compositor to start
    # greeter-session = Session to load for greeter
    # greeter-hide-users = True to hide the user list
    # greeter-allow-guest = True if the greeter should show a guest login option
    # greeter-show-manual-login = True if the greeter should offer a manual login option
    # greeter-show-remote-login = True if the greeter should offer a remote login option
    # user-session = Session to load for users
    # allow-user-switching = True if allowed to switch users
    # allow-guest = True if guest login is allowed
    # guest-session = Session to load for guests (overrides user-session)
    # session-wrapper = Wrapper script to run session with
    # greeter-wrapper = Wrapper script to run greeter with
    # guest-wrapper = Wrapper script to run guest sessions with
    # display-setup-script = Script to run when starting a greeter session (runs as root)
    # display-stopped-script = Script to run after stopping the display server (runs as root)
    # greeter-setup-script = Script to run when starting a greeter (runs as root)
    # session-setup-script = Script to run when starting a user session (runs as root)
    # session-cleanup-script = Script to run when quitting a user session (runs as root)
    # autologin-guest = True to log in as guest by default
    autologin-user=root
    autologin-user-timeout=0
    # autologin-session = Session to load for automatic login (overrides user-session)
    # autologin-in-background = True if autologin session should not be immediately activated
    # exit-on-failure = True if the daemon should exit if this seat fails
    #
    [Seat:*]
    #type=xlocal
    #pam-service=lightdm
    #pam-autologin-service=lightdm-autologin
    #pam-greeter-service=lightdm-greeter
    #xserver-command=X
    #xmir-command=Xmir
    #xserver-config=
    #xserver-layout=
    #xserver-allow-tcp=false
    #xserver-share=true
    #xserver-hostname=
    #xserver-display-number=
    #xdmcp-manager=
    #xdmcp-port=177
    #xdmcp-key=
    #unity-compositor-command=unity-system-compositor
    #unity-compositor-timeout=60
    #greeter-session=example-gtk-gnome
    #greeter-hide-users=false
    #greeter-allow-guest=true
    #greeter-show-manual-login=false
    #greeter-show-remote-login=true
    #user-session=default
    #allow-user-switching=true
    #allow-guest=true
    #guest-session=
    #session-wrapper=lightdm-session
    #greeter-wrapper=
    #guest-wrapper=
    #display-setup-script=
    #display-stopped-script=
    #greeter-setup-script=
    #session-setup-script=
    #session-cleanup-script=
    #autologin-guest=false
    autologin-user=root
    autologin-user-timeout=0
    #autologin-in-background=false
    #autologin-session=
    #exit-on-failure=false

    #
    # XDMCP Server configuration
    #
    # enabled = True if XDMCP connections should be allowed
    # port = UDP/IP port to listen for connections on
    # listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
    # key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
    # hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
    #
    # The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
    # it can be a word and the first 7 characters are used as the key.
    #
    [XDMCPServer]
    #enabled=false
    #port=177
    #listen-address=
    #key=
    #hostname=

    #
    # VNC Server configuration
    #
    # enabled = True if VNC connections should be allowed
    # command = Command to run Xvnc server with
    # port = TCP/IP port to listen for connections on
    # listen-address = Host/address to listen for VNC connections (use all addresses if not present)
    # width = Width of display to use
    # height = Height of display to use
    # depth = Color depth of display to use
    #
    [VNCServer]
    #enabled=false
    #command=Xvnc
    #port=5900
    #listen-address=
    #width=1024
    #height=768
    #depth=8

  14. #14
    Join Date
    2014-Jul
    Posts
    55
    LOL
    now i am also having same issue again
    i am having issue after dist-upgrade

    i have no idea why..
    before dist-upgrade it was working fine

    i suggest you to reinstall OS in SD card..
    and dont run that command
    and your config file is fine

    anyone have any idea why we are having issue after dist upgrade ????

  15. #15
    Join Date
    2015-Mar
    Posts
    48
    Well, lightdm 1.16.6 works with just one line (autologin-user=root) but 1.18.2 doesn't work, so there's the problem.

    What's strange is that I used apt upgrade and it prompted something about the lightdm.conf file, I can't remember what it was and just chose the default. So that machine is fully updated and autologin works.

  16. #16
    Join Date
    2015-Mar
    Posts
    48
    The solution is to comment out line #11 in /etc/pam.d/lightdm-autologin

  17. #17
    Join Date
    2016-Feb
    Posts
    19
    Have you the same configuration file?

    My /etc/lightdm/lightdm.conf:

    # autologin-guest = True to log in as guest by default
    autologin-user = root
    autologin-user-timeout = 0
    # autologin-session = Session to load for automatic login (overrides user-session)

    #autologin-guest=false
    autologin-user=root
    autologin-user-timeout=0
    #autologin-in-background=false

    I have commented out line #11 in /etc/pam.d/lightdm-autologin:

    #%PAM-1.0

    # Block login if they are globally disabled
    auth requisite pam_nologin.so

    # Load environment from /etc/environment and ~/.pam_environment
    session required pam_env.so readenv=1
    session required pam_env.so readenv=1 envfile=/etc/default/locale

    # Allow access without authentication
    auth required pam_succeed_if.so user != root quiet_success
    auth required pam_permit.so

  18. #18
    Join Date
    2015-Mar
    Posts
    48
    I only changed one line in each file:

    /etc/lightdm/lightdm.conf
    autologin-user=root

    /etc/pam.d/lightdm-autologin
    #auth required pam_succeed_if.so user != root quiet_success

Similar Threads

  1. Autologin to OpenBox DE
    By throwaway_ in forum General Archive
    Replies: 0
    Last Post: 2017-12-04, 05:35
  2. autologin console mode
    By sbalymov in forum ARM Archive
    Replies: 1
    Last Post: 2017-07-20, 17:49
  3. Can't get autologin/start ssh/vnc on boot!
    By UnfairGamer in forum ARM Archive
    Replies: 0
    Last Post: 2016-08-16, 19:12
  4. ssh acces and autologin on raspbery 2 b with kali
    By 750rom in forum General Archive
    Replies: 2
    Last Post: 2016-03-28, 11:19

Posting Permissions

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