Firefox not creating sslkeylog file after setting SSLKEYLOGFILE variable
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I ran this in the terminal: export SSLKEYLOGFILE=/home/user/sslkeylog
After opening regular Firefox, the developer version of Firefox and Chromium, "sslkeylog" was never created, even after visiting a site that uses TLS. I also tried setting the file name to "sslkeylog.log", but that did not help either.
I want to decrypt my web browser traffic using wireshark.
`
firefox chromium environment-variables ssl tls
asked May 16 at 21:58
J. DOe
91
add a comment |Â
up vote
0
down vote
favorite
I ran this in the terminal: export SSLKEYLOGFILE=/home/user/sslkeylog
After opening regular Firefox, the developer version of Firefox and Chromium, "sslkeylog" was never created, even after visiting a site that uses TLS. I also tried setting the file name to "sslkeylog.log", but that did not help either.
I want to decrypt my web browser traffic using wireshark.
`
firefox chromium environment-variables ssl tls
asked May 16 at 21:58
J. DOe
91
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
The conclusion then is that you need to set that variable persistently, e.g. in~/.profilewhich is sourced by the display manager at login.
– Gunnar Hjalmarsson
May 16 at 22:22
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I ran this in the terminal: export SSLKEYLOGFILE=/home/user/sslkeylog
After opening regular Firefox, the developer version of Firefox and Chromium, "sslkeylog" was never created, even after visiting a site that uses TLS. I also tried setting the file name to "sslkeylog.log", but that did not help either.
I want to decrypt my web browser traffic using wireshark.
`
firefox chromium environment-variables ssl tls
asked May 16 at 21:58
J. DOe
91
I ran this in the terminal: export SSLKEYLOGFILE=/home/user/sslkeylog
After opening regular Firefox, the developer version of Firefox and Chromium, "sslkeylog" was never created, even after visiting a site that uses TLS. I also tried setting the file name to "sslkeylog.log", but that did not help either.
I want to decrypt my web browser traffic using wireshark.
`
firefox chromium environment-variables ssl tls
asked May 16 at 21:58
J. DOe
91
asked May 16 at 21:58
J. DOe
91
asked May 16 at 21:58
J. DOe
91
asked May 16 at 21:58
J. DOe
91
91
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
The conclusion then is that you need to set that variable persistently, e.g. in~/.profilewhich is sourced by the display manager at login.
– Gunnar Hjalmarsson
May 16 at 22:22
add a comment |Â
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
The conclusion then is that you need to set that variable persistently, e.g. in~/.profilewhich is sourced by the display manager at login.
– Gunnar Hjalmarsson
May 16 at 22:22
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
The conclusion then is that you need to set that variable persistently, e.g. in
~/.profile which is sourced by the display manager at login.– Gunnar Hjalmarsson
May 16 at 22:22
The conclusion then is that you need to set that variable persistently, e.g. in
~/.profile which is sourced by the display manager at login.– Gunnar Hjalmarsson
May 16 at 22:22
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
The variable you describe works as intended for me on Firefox 62. Perhaps the browser builds you are using have been built to ignore the variable? From https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format:
[S]tarting with NSS 3.24 (used by Firefox 48 and 49 only), the
SSLKEYLOGFILE approach is disabled by default for optimized builds
using the Makefile (those using gyp via build.sh are not affected).
Distributors can re-enable it at compile time though (using the
NSS_ALLOW_SSLKEYLOGFILE=1 make variable) which is done for the
official Firefox binaries. (See bug 1188657.) Notably, Debian does not
have this option enabled, see Debian bug 842292.
answered May 16 at 22:13
dsstorefile1
1,243111
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The variable you describe works as intended for me on Firefox 62. Perhaps the browser builds you are using have been built to ignore the variable? From https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format:
[S]tarting with NSS 3.24 (used by Firefox 48 and 49 only), the
SSLKEYLOGFILE approach is disabled by default for optimized builds
using the Makefile (those using gyp via build.sh are not affected).
Distributors can re-enable it at compile time though (using the
NSS_ALLOW_SSLKEYLOGFILE=1 make variable) which is done for the
official Firefox binaries. (See bug 1188657.) Notably, Debian does not
have this option enabled, see Debian bug 842292.
answered May 16 at 22:13
dsstorefile1
1,243111
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
add a comment |Â
up vote
1
down vote
The variable you describe works as intended for me on Firefox 62. Perhaps the browser builds you are using have been built to ignore the variable? From https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format:
[S]tarting with NSS 3.24 (used by Firefox 48 and 49 only), the
SSLKEYLOGFILE approach is disabled by default for optimized builds
using the Makefile (those using gyp via build.sh are not affected).
Distributors can re-enable it at compile time though (using the
NSS_ALLOW_SSLKEYLOGFILE=1 make variable) which is done for the
official Firefox binaries. (See bug 1188657.) Notably, Debian does not
have this option enabled, see Debian bug 842292.
answered May 16 at 22:13
dsstorefile1
1,243111
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The variable you describe works as intended for me on Firefox 62. Perhaps the browser builds you are using have been built to ignore the variable? From https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format:
[S]tarting with NSS 3.24 (used by Firefox 48 and 49 only), the
SSLKEYLOGFILE approach is disabled by default for optimized builds
using the Makefile (those using gyp via build.sh are not affected).
Distributors can re-enable it at compile time though (using the
NSS_ALLOW_SSLKEYLOGFILE=1 make variable) which is done for the
official Firefox binaries. (See bug 1188657.) Notably, Debian does not
have this option enabled, see Debian bug 842292.
answered May 16 at 22:13
dsstorefile1
1,243111
The variable you describe works as intended for me on Firefox 62. Perhaps the browser builds you are using have been built to ignore the variable? From https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format:
[S]tarting with NSS 3.24 (used by Firefox 48 and 49 only), the
SSLKEYLOGFILE approach is disabled by default for optimized builds
using the Makefile (those using gyp via build.sh are not affected).
Distributors can re-enable it at compile time though (using the
NSS_ALLOW_SSLKEYLOGFILE=1 make variable) which is done for the
official Firefox binaries. (See bug 1188657.) Notably, Debian does not
have this option enabled, see Debian bug 842292.
answered May 16 at 22:13
dsstorefile1
1,243111
answered May 16 at 22:13
dsstorefile1
1,243111
answered May 16 at 22:13
dsstorefile1
1,243111
answered May 16 at 22:13
dsstorefile1
1,243111
1,243111
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
add a comment |Â
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
I only have Firefox 60 and 61.0b5, though it should work on these versions according to the link in your answer. Perhaps it would work if I tried it on Firefox 62.
– J. DOe
May 16 at 22:17
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037134%2ffirefox-not-creating-sslkeylog-file-after-setting-sslkeylogfile-variable%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
How did you open FF after having run that terminal command? From terminal or from the graphical environment?
– Gunnar Hjalmarsson
May 16 at 22:19
I opened FF from the graphical environment. After opening it from the terminal, the sslkeylog file was succesffully created. Thank you.
– J. DOe
May 16 at 22:21
The conclusion then is that you need to set that variable persistently, e.g. in
~/.profilewhich is sourced by the display manager at login.– Gunnar Hjalmarsson
May 16 at 22:22