Strace Ltrace Retrace

Term

Details

  • Location: KringleCon/Kitchen
  • Elf: Tinsel Upatree

Elf's Objective Message

Hiya hiya, I'm Tinsel Upatree!

Say, do you know what's going on next door? I'm a bit worried about the whole FrostFest event. It feels a bit... ill-conceived, somehow. Nasty even. Well, regardless – and more to the point, what do you know about tracing processes in Linux? We rebuilt this here Cranberry Pi that runs the cotton candy machine, but we seem to be missing a file. Do you think you can use strace or ltrace to help us rebuild the missing config? We'd like to help some of our favorite children enjoy the sweet spun goodness again! And, if you help me with this, I’ll give you some hints about using Wireshark filters to look for unusual options that might help you achieve Objectives here at the North Pole.

This terminal is located in the Kitchen at KringleCon. Solving this terminal challenge provides additional hints for objective 11. To view the hints for this terminal challenge use the menu on the left.

To solve this terminal challenge you need to recreate the registration file for the cotton candy machine.

You will need to use ltrace to figure out what the registration file for ./make_the_candy.

Start by running ltrace ./make_the_candy.

Term

The above result shows that the program is looking for a file called registration.json.

Create an empty file called registration.json by using vi or nano editors.

Rerunning ltrace ./make_the_candy shows the following results:

Term

This indicates that the program is looking for the string "[Description]" following by a '\n' new line. Use nano to edit registration.json and add "[Description]" and a new line by pressing enter. Save the file.

Rerunning ltrace ./make_the_candy again shows the following results:

Term

This indicates that the program is looking for the string "Registration: True". Use nano to edit registration.json and add "Registration:True". Save the file.

registration.json

Registration:True

Rerunning ltrace ./make_the_candy shows the candy machine is operational with the above registration.json file:

Term