My bash script verification code does not work

Question

I am trying to write a program where the user can enter a username and password, then the code should check if the username and password are correct unfortunately whenever it checks no matter if the username/password is correct of not it will echo "Username Verified".

#!/bin/bash
echo "Username"  
read username  
echo "Password"
read password
sleep 1
correct_u=user
correct_p=pass
if [[ $username -eq $correct_u ]]
then
  echo "Username Verified..."
else 
  echo "Username Incorect..."
fi
sleep 1
if [[ $correct_p -eq $password ]]
then 
  sleep 1
  echo "Password Verified..."
else 
  echo "Password Incorect..."
fi

I have tired checking that all the variables work

What have you tried to resolve the problem? Where are you stuck? — Nico Haase
– Nico Haase, Commented Jan 9, 2023 at 12:54
Use this guide for asking good questions that get good, quick answers. — Paul Hodges
– Paul Hodges, Commented Jan 9, 2023 at 14:08

user1934428 · Accepted Answer · 2023-01-09 13:00:54Z

1

Unless username and correct_u consist solely of digits, [[ $username -eq $correct_u ]] will always evaluate to true, since -eq forces the arguments to be numbers, and if there are no number, the arguments are treated as zero.

To do a string comparision, do

[[ $username == "$correct_u" ]]

Quoting the right-hand side is important here, to avoid that it is interpreted as glob-pattern, since == in general does a wildcard match.

answered Jan 9, 2023 at 13:00

user1934428

22.8k9 gold badges57 silver badges108 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jetchisel Over a year ago

The single = does the same, the magic is from [[ ]] afaik.

user1934428 Over a year ago

@Jetchisel: Yes; according to the man page: _The = operator is equivalent to ==. _ It's a matter of taste. I usually prefer the == form, perhaps this is the way many programming languages express equality. But the point of my answer is that you can't use -eq here.

Roniel López · Accepted Answer · 2023-01-09 13:01:36Z

0

You should use = instead of -eq when comparing strings in bash. = is used for string comparison while -eq is used for integer comparison:

#!/bin/bash
echo "Username"  
read username  
echo "Password"
read password
sleep 1
correct_u=user
correct_p=pass
if [[ "$username" = "$correct_u" ]]
then
  echo "Username Verified..."
else 
  echo "Username Incorrect..."
fi
sleep 1
if [[ "$correct_p" = "$password" ]]
then 
  sleep 1
  echo "Password Verified..."
else 
  echo "Password Incorrect..."
fi

answered Jan 9, 2023 at 13:01

Roniel López

4112 silver badges10 bronze badges

1 Comment

Roniel López Over a year ago

if you consider this answer is useful please mark it as accepted :)

Paul Hodges · Accepted Answer · 2023-01-09 14:57:54Z

Embedding your name & pw in cleartext in the file isn't ideal. The user ID must be able to read it to execute the commands in it; executable permissions won't help if you take away read.

Use that to your advantage. Set the user/group/world permissions appropriately. Then the user and password are entered at login...

You might want to combine methods from here and here, reading the right password securely from a vault file and comparing that to the one you read silently from the user.

But first, as already mentioned - fix your test.

$: [[ "one" -eq "two" ]] && echo same || echo no
same

$: [[ "one" == "two" ]] && echo same || echo no
no

$: [[ "one" == "one" ]] && echo same || echo no
same

Collectives™ on Stack Overflow

My bash script verification code does not work

3 Answers 3

2 Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

1 Comment

Comments

Linked

Related