How to decode/decipher Mozilla Firefox proprietary .jsonlz4 format? (sessionstore-backups/recovery.jsonlz4)

Clash Royale CLAN TAG#URR8PPP

up vote
3
down vote

favorite

I'm trying to get a handle on Mozilla Firefox's proprietary file format .jsonlz4, used, for example, for sessionstore-backups/recovery.jsonlz4, but to no avail.

How do I get back my data, specifically, some long text I've typed in some textareas of a crashed session? It's my data!

firefox backup json session-restore jsonlz4

share|improve this question

asked 3 hours ago

cnst

1,04931633

add a comment | 

up vote
3
down vote

favorite

I'm trying to get a handle on Mozilla Firefox's proprietary file format .jsonlz4, used, for example, for sessionstore-backups/recovery.jsonlz4, but to no avail.

How do I get back my data, specifically, some long text I've typed in some textareas of a crashed session? It's my data!

firefox backup json session-restore jsonlz4

share|improve this question

asked 3 hours ago

cnst

1,04931633

add a comment | 

up vote
3
down vote

favorite

up vote
3
down vote

favorite

I'm trying to get a handle on Mozilla Firefox's proprietary file format .jsonlz4, used, for example, for sessionstore-backups/recovery.jsonlz4, but to no avail.

How do I get back my data, specifically, some long text I've typed in some textareas of a crashed session? It's my data!

firefox backup json session-restore jsonlz4

share|improve this question

asked 3 hours ago

cnst

1,04931633

I'm trying to get a handle on Mozilla Firefox's proprietary file format .jsonlz4, used, for example, for sessionstore-backups/recovery.jsonlz4, but to no avail.

How do I get back my data, specifically, some long text I've typed in some textareas of a crashed session? It's my data!

firefox backup json session-restore jsonlz4

firefox backup json session-restore jsonlz4

share|improve this question

asked 3 hours ago

cnst

1,04931633

share|improve this question

asked 3 hours ago

cnst

1,04931633

share|improve this question

share|improve this question

asked 3 hours ago

cnst

1,04931633

asked 3 hours ago

cnst

1,04931633

asked 3 hours ago

cnst

1,04931633

1,04931633

add a comment | 

add a comment | 

2 Answers
2

active

oldest

votes

up vote
4
down vote

As per https://www.reddit.com/r/firefox/comments/2ps6wg/jsonlz4_bookmark_backups/, the following appears to work:

• in about:config, toggle the devtools.chrome.enabled settings from the default of false to a value of true



• 
  

  open Scratchpad:

  
  
  
  • either with fn+Shift+F4 on a MacBook,
  
  
  • or Shift+F4,
  
  
  • or through the menu bar through Tools, Web Developer, Scratchpad
    
  
  



• in the menu bar within Scratchpad, change Enrivonment from Content to Browser (omitting this step would subsequently result in errors like Exception: ReferenceError: OS is not defined at the next step)



• 
  

  use code like the following in the Scratchpad:

  
  
  

  var file = "var file = "/Users/…/sessionstore-backups/recovery.baklz4";
  //OS.File.read(file, compression: "lz4" ).then(bytes => 
  // OS.File.writeAtomic(file + ".uncompressed", bytes));
  
  OS.File.read(file, compression: "lz4" ).then(bytes => 
   OS.File.writeAtomic(file + ".uncompressed.stringify",
   JSON.stringify(JSON.parse(new TextDecoder().decode(bytes)),null,1))
  );
  

  
  
  

  The final parameter to JSON.stringify handles how many spaces would be used at each line; putting 0 causes the whole thing to be printed on a single line, putting 1 splits the lines properly (putting 2 would create too much useless whitespace and increase the size of the file for little benefit)

  
  



• click the Run button




• run fgrep :textarea /Users/…/sessionstore-backups/recovery.baklz4.uncompressed.stringify from within the Terminal app

share|improve this answer

answered 3 hours ago

cnst

1,04931633

add a comment | 

up vote
0
down vote

Unfortunately, due to a non-standard header, standard tools won't work. There's an open proposal to change that. Apparently the Mozilla header was devised before a standard lz4 frame format existed; it does wrap a standard lz4 block.

That said, the same bug report includes a few alternative methods. I'll list them briefly:

• Use the dejsonlz4 tool, which includes binary builds for Windows and should be easy to build on *nix
  
  
  • 
    lz4json is a similar tool, but relies on an external liblz4 and is somewhat easier to build on *nix but harder on Windows (outside WSL)
  
  


• Use this fairly simple Python script: https://gist.github.com/Tblue/62ff47bef7f894e92ed5 (requires the lz4 package via pip or your package manager) -- the script appears to be python3 but is trivially adaptable to python2


• There is a webextension available that should be able to open these. NB: while source is available, I have not verified it, and the permissions it requests are a bit concerning (especially the response to concerns)


• In theory, you should be able to strip the first 8 bytes (e.g. with dd if=original.jsonlz4 of=stripped.lz4 bs=8 skip=1) and that should leave you with a valid lz4 block. Note that this is distinct from a lz4 frame. While most programming languages have libraries that can easily decode a block, finding a prebuilt tool to do so is more difficult, e.g. the liblz4-tool package only accepts the frame format.

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1363747%2fhow-to-decode-decipher-mozilla-firefox-proprietary-jsonlz4-format-sessionstor%23new-answer', 'question_page');

);

Post as a guest

Name Email

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
4
down vote

As per https://www.reddit.com/r/firefox/comments/2ps6wg/jsonlz4_bookmark_backups/, the following appears to work:

• in about:config, toggle the devtools.chrome.enabled settings from the default of false to a value of true



• 
  

  open Scratchpad:

  
  
  
  • either with fn+Shift+F4 on a MacBook,
  
  
  • or Shift+F4,
  
  
  • or through the menu bar through Tools, Web Developer, Scratchpad
    
  
  



• in the menu bar within Scratchpad, change Enrivonment from Content to Browser (omitting this step would subsequently result in errors like Exception: ReferenceError: OS is not defined at the next step)



• 
  

  use code like the following in the Scratchpad:

  
  
  

  var file = "var file = "/Users/…/sessionstore-backups/recovery.baklz4";
  //OS.File.read(file, compression: "lz4" ).then(bytes => 
  // OS.File.writeAtomic(file + ".uncompressed", bytes));
  
  OS.File.read(file, compression: "lz4" ).then(bytes => 
   OS.File.writeAtomic(file + ".uncompressed.stringify",
   JSON.stringify(JSON.parse(new TextDecoder().decode(bytes)),null,1))
  );
  

  
  
  

  The final parameter to JSON.stringify handles how many spaces would be used at each line; putting 0 causes the whole thing to be printed on a single line, putting 1 splits the lines properly (putting 2 would create too much useless whitespace and increase the size of the file for little benefit)

  
  



• click the Run button




• run fgrep :textarea /Users/…/sessionstore-backups/recovery.baklz4.uncompressed.stringify from within the Terminal app

share|improve this answer

answered 3 hours ago

cnst

1,04931633

add a comment | 

up vote
4
down vote

As per https://www.reddit.com/r/firefox/comments/2ps6wg/jsonlz4_bookmark_backups/, the following appears to work:

• in about:config, toggle the devtools.chrome.enabled settings from the default of false to a value of true



• 
  

  open Scratchpad:

  
  
  
  • either with fn+Shift+F4 on a MacBook,
  
  
  • or Shift+F4,
  
  
  • or through the menu bar through Tools, Web Developer, Scratchpad
    
  
  



• in the menu bar within Scratchpad, change Enrivonment from Content to Browser (omitting this step would subsequently result in errors like Exception: ReferenceError: OS is not defined at the next step)



• 
  

  use code like the following in the Scratchpad:

  
  
  

  var file = "var file = "/Users/…/sessionstore-backups/recovery.baklz4";
  //OS.File.read(file, compression: "lz4" ).then(bytes => 
  // OS.File.writeAtomic(file + ".uncompressed", bytes));
  
  OS.File.read(file, compression: "lz4" ).then(bytes => 
   OS.File.writeAtomic(file + ".uncompressed.stringify",
   JSON.stringify(JSON.parse(new TextDecoder().decode(bytes)),null,1))
  );
  

  
  
  

  The final parameter to JSON.stringify handles how many spaces would be used at each line; putting 0 causes the whole thing to be printed on a single line, putting 1 splits the lines properly (putting 2 would create too much useless whitespace and increase the size of the file for little benefit)

  
  



• click the Run button




• run fgrep :textarea /Users/…/sessionstore-backups/recovery.baklz4.uncompressed.stringify from within the Terminal app

share|improve this answer

answered 3 hours ago

cnst

1,04931633

add a comment | 

up vote
4
down vote

up vote
4
down vote

As per https://www.reddit.com/r/firefox/comments/2ps6wg/jsonlz4_bookmark_backups/, the following appears to work:

• in about:config, toggle the devtools.chrome.enabled settings from the default of false to a value of true



• 
  

  open Scratchpad:

  
  
  
  • either with fn+Shift+F4 on a MacBook,
  
  
  • or Shift+F4,
  
  
  • or through the menu bar through Tools, Web Developer, Scratchpad
    
  
  



• in the menu bar within Scratchpad, change Enrivonment from Content to Browser (omitting this step would subsequently result in errors like Exception: ReferenceError: OS is not defined at the next step)



• 
  

  use code like the following in the Scratchpad:

  
  
  

  var file = "var file = "/Users/…/sessionstore-backups/recovery.baklz4";
  //OS.File.read(file, compression: "lz4" ).then(bytes => 
  // OS.File.writeAtomic(file + ".uncompressed", bytes));
  
  OS.File.read(file, compression: "lz4" ).then(bytes => 
   OS.File.writeAtomic(file + ".uncompressed.stringify",
   JSON.stringify(JSON.parse(new TextDecoder().decode(bytes)),null,1))
  );
  

  
  
  

  The final parameter to JSON.stringify handles how many spaces would be used at each line; putting 0 causes the whole thing to be printed on a single line, putting 1 splits the lines properly (putting 2 would create too much useless whitespace and increase the size of the file for little benefit)

  
  



• click the Run button




• run fgrep :textarea /Users/…/sessionstore-backups/recovery.baklz4.uncompressed.stringify from within the Terminal app

share|improve this answer

answered 3 hours ago

cnst

1,04931633

As per https://www.reddit.com/r/firefox/comments/2ps6wg/jsonlz4_bookmark_backups/, the following appears to work:

• in about:config, toggle the devtools.chrome.enabled settings from the default of false to a value of true



• 
  

  open Scratchpad:

  
  
  
  • either with fn+Shift+F4 on a MacBook,
  
  
  • or Shift+F4,
  
  
  • or through the menu bar through Tools, Web Developer, Scratchpad
    
  
  



• in the menu bar within Scratchpad, change Enrivonment from Content to Browser (omitting this step would subsequently result in errors like Exception: ReferenceError: OS is not defined at the next step)



• 
  

  use code like the following in the Scratchpad:

  
  
  

  var file = "var file = "/Users/…/sessionstore-backups/recovery.baklz4";
  //OS.File.read(file, compression: "lz4" ).then(bytes => 
  // OS.File.writeAtomic(file + ".uncompressed", bytes));
  
  OS.File.read(file, compression: "lz4" ).then(bytes => 
   OS.File.writeAtomic(file + ".uncompressed.stringify",
   JSON.stringify(JSON.parse(new TextDecoder().decode(bytes)),null,1))
  );
  

  
  
  

  The final parameter to JSON.stringify handles how many spaces would be used at each line; putting 0 causes the whole thing to be printed on a single line, putting 1 splits the lines properly (putting 2 would create too much useless whitespace and increase the size of the file for little benefit)

  
  



• click the Run button




• run fgrep :textarea /Users/…/sessionstore-backups/recovery.baklz4.uncompressed.stringify from within the Terminal app

share|improve this answer

answered 3 hours ago

cnst

1,04931633

share|improve this answer

share|improve this answer

answered 3 hours ago

cnst

1,04931633

answered 3 hours ago

cnst

1,04931633

answered 3 hours ago

cnst

1,04931633

1,04931633

add a comment | 

add a comment | 

up vote
0
down vote

Unfortunately, due to a non-standard header, standard tools won't work. There's an open proposal to change that. Apparently the Mozilla header was devised before a standard lz4 frame format existed; it does wrap a standard lz4 block.

That said, the same bug report includes a few alternative methods. I'll list them briefly:

• Use the dejsonlz4 tool, which includes binary builds for Windows and should be easy to build on *nix
  
  
  • 
    lz4json is a similar tool, but relies on an external liblz4 and is somewhat easier to build on *nix but harder on Windows (outside WSL)
  
  


• Use this fairly simple Python script: https://gist.github.com/Tblue/62ff47bef7f894e92ed5 (requires the lz4 package via pip or your package manager) -- the script appears to be python3 but is trivially adaptable to python2


• There is a webextension available that should be able to open these. NB: while source is available, I have not verified it, and the permissions it requests are a bit concerning (especially the response to concerns)


• In theory, you should be able to strip the first 8 bytes (e.g. with dd if=original.jsonlz4 of=stripped.lz4 bs=8 skip=1) and that should leave you with a valid lz4 block. Note that this is distinct from a lz4 frame. While most programming languages have libraries that can easily decode a block, finding a prebuilt tool to do so is more difficult, e.g. the liblz4-tool package only accepts the frame format.

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

add a comment | 

up vote
0
down vote

Unfortunately, due to a non-standard header, standard tools won't work. There's an open proposal to change that. Apparently the Mozilla header was devised before a standard lz4 frame format existed; it does wrap a standard lz4 block.

That said, the same bug report includes a few alternative methods. I'll list them briefly:

• Use the dejsonlz4 tool, which includes binary builds for Windows and should be easy to build on *nix
  
  
  • 
    lz4json is a similar tool, but relies on an external liblz4 and is somewhat easier to build on *nix but harder on Windows (outside WSL)
  
  


• Use this fairly simple Python script: https://gist.github.com/Tblue/62ff47bef7f894e92ed5 (requires the lz4 package via pip or your package manager) -- the script appears to be python3 but is trivially adaptable to python2


• There is a webextension available that should be able to open these. NB: while source is available, I have not verified it, and the permissions it requests are a bit concerning (especially the response to concerns)


• In theory, you should be able to strip the first 8 bytes (e.g. with dd if=original.jsonlz4 of=stripped.lz4 bs=8 skip=1) and that should leave you with a valid lz4 block. Note that this is distinct from a lz4 frame. While most programming languages have libraries that can easily decode a block, finding a prebuilt tool to do so is more difficult, e.g. the liblz4-tool package only accepts the frame format.

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

add a comment | 

up vote
0
down vote

up vote
0
down vote

Unfortunately, due to a non-standard header, standard tools won't work. There's an open proposal to change that. Apparently the Mozilla header was devised before a standard lz4 frame format existed; it does wrap a standard lz4 block.

That said, the same bug report includes a few alternative methods. I'll list them briefly:

• Use the dejsonlz4 tool, which includes binary builds for Windows and should be easy to build on *nix
  
  
  • 
    lz4json is a similar tool, but relies on an external liblz4 and is somewhat easier to build on *nix but harder on Windows (outside WSL)
  
  


• Use this fairly simple Python script: https://gist.github.com/Tblue/62ff47bef7f894e92ed5 (requires the lz4 package via pip or your package manager) -- the script appears to be python3 but is trivially adaptable to python2


• There is a webextension available that should be able to open these. NB: while source is available, I have not verified it, and the permissions it requests are a bit concerning (especially the response to concerns)


• In theory, you should be able to strip the first 8 bytes (e.g. with dd if=original.jsonlz4 of=stripped.lz4 bs=8 skip=1) and that should leave you with a valid lz4 block. Note that this is distinct from a lz4 frame. While most programming languages have libraries that can easily decode a block, finding a prebuilt tool to do so is more difficult, e.g. the liblz4-tool package only accepts the frame format.

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

Unfortunately, due to a non-standard header, standard tools won't work. There's an open proposal to change that. Apparently the Mozilla header was devised before a standard lz4 frame format existed; it does wrap a standard lz4 block.

That said, the same bug report includes a few alternative methods. I'll list them briefly:

• Use the dejsonlz4 tool, which includes binary builds for Windows and should be easy to build on *nix
  
  
  • 
    lz4json is a similar tool, but relies on an external liblz4 and is somewhat easier to build on *nix but harder on Windows (outside WSL)
  
  


• Use this fairly simple Python script: https://gist.github.com/Tblue/62ff47bef7f894e92ed5 (requires the lz4 package via pip or your package manager) -- the script appears to be python3 but is trivially adaptable to python2


• There is a webextension available that should be able to open these. NB: while source is available, I have not verified it, and the permissions it requests are a bit concerning (especially the response to concerns)


• In theory, you should be able to strip the first 8 bytes (e.g. with dd if=original.jsonlz4 of=stripped.lz4 bs=8 skip=1) and that should leave you with a valid lz4 block. Note that this is distinct from a lz4 frame. While most programming languages have libraries that can easily decode a block, finding a prebuilt tool to do so is more difficult, e.g. the liblz4-tool package only accepts the frame format.

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

share|improve this answer

share|improve this answer

answered 3 hours ago

Bob

43.3k19132167

answered 3 hours ago

Bob

43.3k19132167

answered 3 hours ago

Bob

43.3k19132167

43.3k19132167

add a comment | 

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1363747%2fhow-to-decode-decipher-mozilla-firefox-proprietary-jsonlz4-format-sessionstor%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

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

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email