problem shell

Started by Darkopnsense, September 01, 2021, 11:40:22 AM

Previous topic - Next topic
hi guy,

cannot work in console mode

an idea ?

_________________________________________________________________________________________
FreeBSD/amd64 (PareFeu-NG.debnet) (ttyu0)

login: Stephane
Password:
Last login: Fri Aug 27 21:13:03 on ttyu0
----------------------------------------------
|      Hello, this is OPNsense 21.7          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website:      https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook:     https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums:       https://forum.opnsense.org/  |         @@@///   \\\@@@
| Code:         https://github.com/opnsense  |        @@@@         @@@@
| Twitter:      https://twitter.com/opnsense |         @@@@@@@@@@@@@@@
----------------------------------------------
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$ su Stephane
$ sudo Stephane
Password:
Stephane is not in the sudoers file.  This incident will be reported.
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$ sudo Stephane
Password:
Stephane is not in the sudoers file.  This incident will be reported.
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts
$
_________________________________________________________________________________________

regards,
Depuis 2017
X7SPA-HF, Intel(R) ATOM(TM) D525, 4Go RAM, 120Go, 2 Lan 24.1.2_1
APU4c, 4Go RAM, 120Go, 4 Lan 24.1.10_8
APU3a, 2Go RAM, 60Go, 3 Lan 24.1.2_1
APU2c, 2Go RAM, 60Go, 3 Lan 23.7.1_3
BIOS A JOUR (v4.19.0.1).

September 01, 2021, 11:42:41 AM #1 Last Edit: September 01, 2021, 11:44:16 AM by Greelan
sudo su -l

But looks like your user is not configured as a sudoer?

Hi

Quote from: Darkopnsense on September 01, 2021, 11:40:22 AM
hi guy,

cannot work in console mode

an idea ?

_________________________________________________________________________________________
FreeBSD/amd64 (PareFeu-NG.debnet) (ttyu0)

login: Stephane
Password:
Last login: Fri Aug 27 21:13:03 on ttyu0
----------------------------------------------
|      Hello, this is OPNsense 21.7          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website:      https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook:     https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums:       https://forum.opnsense.org/  |         @@@///   \\\@@@
| Code:         https://github.com/opnsense  |        @@@@         @@@@
| Twitter:      https://twitter.com/opnsense |         @@@@@@@@@@@@@@@
----------------------------------------------
$ sudo su
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
sudo: 3 incorrect password attempts

What password you are using? For sudo, you need use the password of the user Stephane.

KH

Hello everyone,

@Greelan,
Thanks for the answer and I have the same thoughts.

@KHE,
Thank you also for your relevant answer, but it is the rules of SUDO.

I am sure of my password.
After various attempts, I can only log in with the correct rights with the following instruction:

  $ su -
Password:
*** Firewall-NG.debnet: OPNsense 21.7.1 (amd64 / OpenSSL) ***
Enter an option: 8
root @ PareFeu-NG: ~ #

The malfunction appeared after reinitializing in console mode with option 4) Reset to factory defaults.

Switching to version 21.7 was tedious in many ways. But hey, you have to deal with it.

Regards,
Depuis 2017
X7SPA-HF, Intel(R) ATOM(TM) D525, 4Go RAM, 120Go, 2 Lan 24.1.2_1
APU4c, 4Go RAM, 120Go, 4 Lan 24.1.10_8
APU3a, 2Go RAM, 60Go, 3 Lan 24.1.2_1
APU2c, 2Go RAM, 60Go, 3 Lan 23.7.1_3
BIOS A JOUR (v4.19.0.1).

As you haven't given much information about your authentication setup I suspect the wrong password message is correct for one reason or another. There isn't a known general issue with authentication and so this points to misconfiguration, possibly also because of the password reset which resets the authentication mode to allow for local password access if e.g. LDAP connectivity is buggy.


Cheers,
Franco