Visible content of 2 variables in bash is the same, but the length is different












0















These 2 variables will have the same visible content



  x_sign1="aabbccdd_and_somthing_else"



  var1="...."

  [........]

  x_sign2=$(echo -n "${var1}${var2}${var3}" | shasum -a 256)

  echo $x_sign2



  ====> 

  aabbccdd_and_somthing_else -


Note the "-" in the end.



However, their lengths will be different. Even though the x_sign2 doesn't contain a new line symbol. To ensure this:



  x_sign22=$(echo -n "${var1}${var2}${var3}" | shasum -a 256 | tr -d 'n')


But:



  echo ${#x_sign1}

  ====> 64

  And:


And:



  echo ${#x_sign2}



  ====> 67



  echo ${#x_sign22}



  ====> 67


The difference is 3 symbols. The visible content is identical.



Also, when I make a request via curl to a REST API which needs that value of a signature, x_sign1 always succeeds, whereas x_sign2 doesn't -- "wrong signature"



Why? How to fix that?






bash terminal







share|improve this question







New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Possibly related: Echo hash only from shasum

    – steeldriver
    15 hours ago











  • @steeldriver I'm not asking how to calculate hash

    – Immani
    14 hours ago











  • But you do seem to be asking why the result has three extra characters, and how to remove them

    – steeldriver
    14 hours ago











  • @steeldriver yes, but your link suggests perl

    – Immani
    14 hours ago
















0















These 2 variables will have the same visible content



  x_sign1="aabbccdd_and_somthing_else"



  var1="...."

  [........]

  x_sign2=$(echo -n "${var1}${var2}${var3}" | shasum -a 256)

  echo $x_sign2



  ====> 

  aabbccdd_and_somthing_else -


Note the "-" in the end.



However, their lengths will be different. Even though the x_sign2 doesn't contain a new line symbol. To ensure this:



  x_sign22=$(echo -n "${var1}${var2}${var3}" | shasum -a 256 | tr -d 'n')


But:



  echo ${#x_sign1}

  ====> 64

  And:


And:



  echo ${#x_sign2}



  ====> 67



  echo ${#x_sign22}



  ====> 67


The difference is 3 symbols. The visible content is identical.



Also, when I make a request via curl to a REST API which needs that value of a signature, x_sign1 always succeeds, whereas x_sign2 doesn't -- "wrong signature"



Why? How to fix that?






bash terminal







share|improve this question







New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Possibly related: Echo hash only from shasum

    – steeldriver
    15 hours ago











  • @steeldriver I'm not asking how to calculate hash

    – Immani
    14 hours ago











  • But you do seem to be asking why the result has three extra characters, and how to remove them

    – steeldriver
    14 hours ago











  • @steeldriver yes, but your link suggests perl

    – Immani
    14 hours ago














0












0








0








These 2 variables will have the same visible content



  x_sign1="aabbccdd_and_somthing_else"



  var1="...."

  [........]

  x_sign2=$(echo -n "${var1}${var2}${var3}" | shasum -a 256)

  echo $x_sign2



  ====> 

  aabbccdd_and_somthing_else -


Note the "-" in the end.



However, their lengths will be different. Even though the x_sign2 doesn't contain a new line symbol. To ensure this:



  x_sign22=$(echo -n "${var1}${var2}${var3}" | shasum -a 256 | tr -d 'n')


But:



  echo ${#x_sign1}

  ====> 64

  And:


And:



  echo ${#x_sign2}



  ====> 67



  echo ${#x_sign22}



  ====> 67


The difference is 3 symbols. The visible content is identical.



Also, when I make a request via curl to a REST API which needs that value of a signature, x_sign1 always succeeds, whereas x_sign2 doesn't -- "wrong signature"



Why? How to fix that?






bash terminal







share|improve this question







New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












These 2 variables will have the same visible content



  x_sign1="aabbccdd_and_somthing_else"



  var1="...."

  [........]

  x_sign2=$(echo -n "${var1}${var2}${var3}" | shasum -a 256)

  echo $x_sign2



  ====> 

  aabbccdd_and_somthing_else -


Note the "-" in the end.



However, their lengths will be different. Even though the x_sign2 doesn't contain a new line symbol. To ensure this:



  x_sign22=$(echo -n "${var1}${var2}${var3}" | shasum -a 256 | tr -d 'n')


But:



  echo ${#x_sign1}

  ====> 64

  And:


And:



  echo ${#x_sign2}



  ====> 67



  echo ${#x_sign22}



  ====> 67


The difference is 3 symbols. The visible content is identical.



Also, when I make a request via curl to a REST API which needs that value of a signature, x_sign1 always succeeds, whereas x_sign2 doesn't -- "wrong signature"



Why? How to fix that?






bash terminal




bash terminal






share|improve this question







New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 15 hours ago









ImmaniImmani

1




1




New contributor




Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Immani is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Possibly related: Echo hash only from shasum

    – steeldriver
    15 hours ago











  • @steeldriver I'm not asking how to calculate hash

    – Immani
    14 hours ago











  • But you do seem to be asking why the result has three extra characters, and how to remove them

    – steeldriver
    14 hours ago











  • @steeldriver yes, but your link suggests perl

    – Immani
    14 hours ago



















  • Possibly related: Echo hash only from shasum

    – steeldriver
    15 hours ago











  • @steeldriver I'm not asking how to calculate hash

    – Immani
    14 hours ago











  • But you do seem to be asking why the result has three extra characters, and how to remove them

    – steeldriver
    14 hours ago











  • @steeldriver yes, but your link suggests perl

    – Immani
    14 hours ago

















Possibly related: Echo hash only from shasum

– steeldriver
15 hours ago





Possibly related: Echo hash only from shasum

– steeldriver
15 hours ago













@steeldriver I'm not asking how to calculate hash

– Immani
14 hours ago





@steeldriver I'm not asking how to calculate hash

– Immani
14 hours ago













But you do seem to be asking why the result has three extra characters, and how to remove them

– steeldriver
14 hours ago





But you do seem to be asking why the result has three extra characters, and how to remove them

– steeldriver
14 hours ago













@steeldriver yes, but your link suggests perl

– Immani
14 hours ago





@steeldriver yes, but your link suggests perl

– Immani
14 hours ago










1 Answer
1






active

oldest

votes


















2














$ echo foo |shasum -a 256

b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c  -    

                                                                ^^


Note that there are two spaces in the output of shasum before the filename. When the input is taken from stdin, shasum prints a dash as the filename.



If you run echo foo | shasum | od -c you can check that, and see the newline at the end also. The newline, however, is removed by the command substitution, so removing it explicitly with tr doesn't do anything. (see here and here)



The two spaces and the dash are three characters that cause the difference in your counts.



To get just the hash, you could use parameter expansions to remove anything after the first space, e.g.:



$ h=$(echo foo | shasum -a 256)

$ h=${h%% *}

$ printf ">%s<n" "$h"

>b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c<


The ${var%%pattern} expands to the value of var with the longest suffix matching pattern removed.






share|improve this answer


























  • how did those 2 whitespaces and the dash end up in the variable?

    – Immani
    14 hours ago











  • @Immani because that's the default behavior when shasum reads from standard input instead of a named file

    – steeldriver
    14 hours ago











  • @steeldriver how to get rid of them?

    – Immani
    14 hours ago











  • @Immani, edited

    – ilkkachu
    12 hours ago











  • what are >, n and < for?

    – Immani
    11 hours ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Immani is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495098%2fvisible-content-of-2-variables-in-bash-is-the-same-but-the-length-is-different%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














$ echo foo |shasum -a 256

b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c  -    

                                                                ^^


Note that there are two spaces in the output of shasum before the filename. When the input is taken from stdin, shasum prints a dash as the filename.



If you run echo foo | shasum | od -c you can check that, and see the newline at the end also. The newline, however, is removed by the command substitution, so removing it explicitly with tr doesn't do anything. (see here and here)



The two spaces and the dash are three characters that cause the difference in your counts.



To get just the hash, you could use parameter expansions to remove anything after the first space, e.g.:



$ h=$(echo foo | shasum -a 256)

$ h=${h%% *}

$ printf ">%s<n" "$h"

>b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c<


The ${var%%pattern} expands to the value of var with the longest suffix matching pattern removed.






share|improve this answer


























  • how did those 2 whitespaces and the dash end up in the variable?

    – Immani
    14 hours ago











  • @Immani because that's the default behavior when shasum reads from standard input instead of a named file

    – steeldriver
    14 hours ago











  • @steeldriver how to get rid of them?

    – Immani
    14 hours ago











  • @Immani, edited

    – ilkkachu
    12 hours ago











  • what are >, n and < for?

    – Immani
    11 hours ago


















2














$ echo foo |shasum -a 256

b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c  -    

                                                                ^^


Note that there are two spaces in the output of shasum before the filename. When the input is taken from stdin, shasum prints a dash as the filename.



If you run echo foo | shasum | od -c you can check that, and see the newline at the end also. The newline, however, is removed by the command substitution, so removing it explicitly with tr doesn't do anything. (see here and here)



The two spaces and the dash are three characters that cause the difference in your counts.



To get just the hash, you could use parameter expansions to remove anything after the first space, e.g.:



$ h=$(echo foo | shasum -a 256)

$ h=${h%% *}

$ printf ">%s<n" "$h"

>b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c<


The ${var%%pattern} expands to the value of var with the longest suffix matching pattern removed.






share|improve this answer


























  • how did those 2 whitespaces and the dash end up in the variable?

    – Immani
    14 hours ago











  • @Immani because that's the default behavior when shasum reads from standard input instead of a named file

    – steeldriver
    14 hours ago











  • @steeldriver how to get rid of them?

    – Immani
    14 hours ago











  • @Immani, edited

    – ilkkachu
    12 hours ago











  • what are >, n and < for?

    – Immani
    11 hours ago
















2












2








2







$ echo foo |shasum -a 256

b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c  -    

                                                                ^^


Note that there are two spaces in the output of shasum before the filename. When the input is taken from stdin, shasum prints a dash as the filename.



If you run echo foo | shasum | od -c you can check that, and see the newline at the end also. The newline, however, is removed by the command substitution, so removing it explicitly with tr doesn't do anything. (see here and here)



The two spaces and the dash are three characters that cause the difference in your counts.



To get just the hash, you could use parameter expansions to remove anything after the first space, e.g.:



$ h=$(echo foo | shasum -a 256)

$ h=${h%% *}

$ printf ">%s<n" "$h"

>b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c<


The ${var%%pattern} expands to the value of var with the longest suffix matching pattern removed.






share|improve this answer















$ echo foo |shasum -a 256

b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c  -    

                                                                ^^


Note that there are two spaces in the output of shasum before the filename. When the input is taken from stdin, shasum prints a dash as the filename.



If you run echo foo | shasum | od -c you can check that, and see the newline at the end also. The newline, however, is removed by the command substitution, so removing it explicitly with tr doesn't do anything. (see here and here)



The two spaces and the dash are three characters that cause the difference in your counts.



To get just the hash, you could use parameter expansions to remove anything after the first space, e.g.:



$ h=$(echo foo | shasum -a 256)

$ h=${h%% *}

$ printf ">%s<n" "$h"

>b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c<


The ${var%%pattern} expands to the value of var with the longest suffix matching pattern removed.







share|improve this answer














share|improve this answer



share|improve this answer








edited 12 hours ago

























answered 14 hours ago









ilkkachuilkkachu

56.7k784156




56.7k784156













  • how did those 2 whitespaces and the dash end up in the variable?

    – Immani
    14 hours ago











  • @Immani because that's the default behavior when shasum reads from standard input instead of a named file

    – steeldriver
    14 hours ago











  • @steeldriver how to get rid of them?

    – Immani
    14 hours ago











  • @Immani, edited

    – ilkkachu
    12 hours ago











  • what are >, n and < for?

    – Immani
    11 hours ago





















  • how did those 2 whitespaces and the dash end up in the variable?

    – Immani
    14 hours ago











  • @Immani because that's the default behavior when shasum reads from standard input instead of a named file

    – steeldriver
    14 hours ago











  • @steeldriver how to get rid of them?

    – Immani
    14 hours ago











  • @Immani, edited

    – ilkkachu
    12 hours ago











  • what are >, n and < for?

    – Immani
    11 hours ago



















how did those 2 whitespaces and the dash end up in the variable?

– Immani
14 hours ago





how did those 2 whitespaces and the dash end up in the variable?

– Immani
14 hours ago













@Immani because that's the default behavior when shasum reads from standard input instead of a named file

– steeldriver
14 hours ago





@Immani because that's the default behavior when shasum reads from standard input instead of a named file

– steeldriver
14 hours ago













@steeldriver how to get rid of them?

– Immani
14 hours ago





@steeldriver how to get rid of them?

– Immani
14 hours ago













@Immani, edited

– ilkkachu
12 hours ago





@Immani, edited

– ilkkachu
12 hours ago













what are >, n and < for?

– Immani
11 hours ago







what are >, n and < for?

– Immani
11 hours ago












Immani is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Immani is a new contributor. Be nice, and check out our Code of Conduct.













Immani is a new contributor. Be nice, and check out our Code of Conduct.












Immani is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495098%2fvisible-content-of-2-variables-in-bash-is-the-same-but-the-length-is-different%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Loup dans la culture

Image
Loups sur une enluminure du Bestiaire d'Aberdeen Le loup est l'animal le plus emblématique de l'histoire de l'Eurasie, il était à l'honneur durant l'Antiquité chez la totalité des anciens peuples européens [ 1 ] . Sommaire 1 Le loup dans la mythologie 2 Les loups dans le folklore 2.1 L'évolution des mentalités 2.2 Le loup dans la psychanalyse 3 Le loup dans les œuvres culturelles 3.1 Le loup dans la littérature 3.1.1 Fables 3.1.2 Poésie 3.1.3 Romans 3.1.4 Littérature jeunesse 3.1.4.1 Quelques titres d'albums contemporains 3.1.5 Bande dessinée 3.2 Le loup à l'écran 3.2.1 Le cinéma et la télévision 3.2.2 Documentaires 3.2.3 Dessins animés 3.2.4 Jeux vidéo 3.3 Le loup en peinture et en sculpture 3.4 Le loup dans les œuvres musicales 4 Le loup et les noms propres 5 Bibliographie 6 Notes et références 7 Voir aussi 7.1 Articles connexes
Read more

How to solve the problem of ntp “Unable to contact time server” from KDE?

Image
1 0 I want to set date and time automatically but this error appears when I try to .. I'm using openSUSE, I tried different servers but it didn't work either, help please! It doesn't seem to be a network problem: $ ping pool.ntp.org 64 bytes from 41.78.128.17: icmp_seq=1 ttl=41 time=260 ms To the question of whether ntpd is installed and running: $ ps -C ntpd PID TTY TIME CMD i.e. there's no ntpd process running. $ rpm -qa | grep ntp yast2-ntp-client-3.1.12-1.7.noarch ntp-4.2.6p5-25.2.1.i586 Further information from the comments: $ sudo ntpdate pool.ntp.org 25 Sep 19:41:51 ntpdate[3162]: no server suitable for synchronization found networking kde opensuse ntp ntpd sh
Read more

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux

Image
0 1 I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture 1). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved? EDIT1: I have had a look at the official Windows drivers for the UX433FA TouchPad, but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited.
Read more