Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
tails
tails
Commits
f31e2b82
Commit
f31e2b82
authored
Mar 18, 2017
by
anonym
Browse files
Test suite: verifry that dirmngr used the configured keyserver.
Will-fix:
#12371
parent
50f409fe
Changes
2
Hide whitespace changes
Inline
Side-by-side
features/step_definitions/torified_gnupg.rb
View file @
f31e2b82
...
...
@@ -246,3 +246,18 @@ Given /^(GnuPG|Seahorse) is configured to use Chutney's onion keyserver$/ do |ap
)
end
end
Then
/^GnuPG's dirmngr uses the configured keyserver$/
do
_
,
_
,
onion_keyserver_address
,
_
=
chutney_onionservice_info
dirmngr_request
=
$vm
.
execute_successfully
(
'gpg-connect-agent --dirmngr "keyserver --hosttable" /bye'
,
user:
LIVE_USER
)
server
=
dirmngr_request
.
stdout
.
chomp
.
lines
[
1
].
split
[
4
]
server
=
/keyserver\s+(\S+)$/
.
match
(
$vm
.
file_content
(
"/home/
#{
LIVE_USER
}
/.gnupg/dirmngr.conf"
)
)[
1
]
assert_equal
(
"hkp://
#{
onion_keyserver_address
}
:5858"
,
server
,
"GnuPG's dirmngr does not use the correct keyserver"
)
end
features/torified_gnupg.feature
View file @
f31e2b82
...
...
@@ -15,6 +15,7 @@ Feature: Keyserver interaction with GnuPG
When
I fetch the
"10CC5BC7"
OpenPGP key using the GnuPG CLI
And
the GnuPG fetch is successful
Then
the
"10CC5BC7"
key is in the live user's public keyring
And
GnuPG's dirmngr uses the configured keyserver
Scenario
:
Fetching OpenPGP keys using Seahorse should work and be done over Tor.
When
I fetch the
"10CC5BC7"
OpenPGP key using Seahorse
...
...
anonym
@anonym
mentioned in issue
#12371 (closed)
·
May 14, 2020
mentioned in issue
#12371 (closed)
mentioned in issue #12371
Toggle commit list
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment