added basic expect script to generate seed-phrase
This commit is contained in:
parent
2414b19b41
commit
8dc577ca2a
@ -28,6 +28,17 @@ if ! id clightning > /dev/null 2>&1; then
|
||||
chown -R $USERID:$GROUPID /home/clightning
|
||||
fi
|
||||
|
||||
# Test if hsm_secret exist, if not create with random mnemonic
|
||||
|
||||
if [ -s /root/.lightning/bitcoin/hsm_secret ];
|
||||
then
|
||||
echo "hsm_secret exist, exiting..."
|
||||
else
|
||||
seed=$(python3 -c "from mnemonic import Mnemonic;m=Mnemonic('english');print(m.generate(128))")
|
||||
echo "Seed Phrase: $seed" > /root/.lightning/bitcoin/seed_phrase.txt
|
||||
expect /root/.lightning/script.exp "$seed"
|
||||
fi
|
||||
|
||||
if [ $(echo "$1" | cut -c1) = "-" ]; then
|
||||
echo "$0: assuming arguments for lightningd"
|
||||
|
||||
|
||||
57
roles/apps/files/clightning/script.exp
Executable file
57
roles/apps/files/clightning/script.exp
Executable file
@ -0,0 +1,57 @@
|
||||
#!/usr/bin/expect -f
|
||||
#
|
||||
# This Expect script was generated by autoexpect on Tue Feb 20 15:56:50 2024
|
||||
# Expect and autoexpect were both written by Don Libes, NIST.
|
||||
#
|
||||
# Note that autoexpect does not guarantee a working script. It
|
||||
# necessarily has to guess about certain things. Two reasons a script
|
||||
# might fail are:
|
||||
#
|
||||
# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
|
||||
# etc.) and devices discard or ignore keystrokes that arrive "too
|
||||
# quickly" after prompts. If you find your new script hanging up at
|
||||
# one spot, try adding a short sleep just before the previous send.
|
||||
# Setting "force_conservative" to 1 (see below) makes Expect do this
|
||||
# automatically - pausing briefly before sending each character. This
|
||||
# pacifies every program I know of. The -c flag makes the script do
|
||||
# this in the first place. The -C flag allows you to define a
|
||||
# character to toggle this mode off and on.
|
||||
|
||||
set force_conservative 0 ;# set to 1 to force conservative mode even if
|
||||
;# script wasn't run conservatively originally
|
||||
if {$force_conservative} {
|
||||
set send_slow {1 .1}
|
||||
proc send {ignore arg} {
|
||||
sleep .1
|
||||
exp_send -s -- $arg
|
||||
}
|
||||
}
|
||||
|
||||
#
|
||||
# 2) differing output - Some programs produce different output each time
|
||||
# they run. The "date" command is an obvious example. Another is
|
||||
# ftp, if it produces throughput statistics at the end of a file
|
||||
# transfer. If this causes a problem, delete these patterns or replace
|
||||
# them with wildcards. An alternative is to use the -p flag (for
|
||||
# "prompt") which makes Expect only look for the last line of output
|
||||
# (i.e., the prompt). The -P flag allows you to define a character to
|
||||
# toggle this mode off and on.
|
||||
#
|
||||
# Read the man page for more info.
|
||||
#
|
||||
# -Don
|
||||
set WORDS [lindex $argv 0]
|
||||
|
||||
set timeout -1
|
||||
spawn lightning-hsmtool generatehsm ./test.hsm
|
||||
match_max 100000
|
||||
expect "*"
|
||||
expect "*"
|
||||
send -- "0\r"
|
||||
expect -exact "Introduce your BIP39 word list separated by space (at least 12 words):\r
|
||||
"
|
||||
send -- "$WORDS\r"
|
||||
expect "*"
|
||||
send -- "\r"
|
||||
expect eof
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user