Skip to content

"decode_secrets: Error opening environment file '/proc/sys/urlader/environment'." #27

Closed

Description

@BlackMage2

the decoder cant read a export file from a FB7530 164.07.21. Why? And where i can specify the password for the export file?
when i run "./decoder.x86_64 decode_secrets ../../../../Downloads/FRITZ.Box\ 7530\ 164.07.21_13.05.22_1650.export" , reports the script:
decode_secrets: Error opening environment file '/proc/sys/urlader/environment'.

Activity

  1. PeterPawn commented on May 13, 2022

    @PeterPawn
    Owner

    Try decoder --help first.

    There you should find the line

    decode_export         - decrypt a FRITZ!OS export file
    

    and taking this hint into account it's obviously, that you've used a wrong call.

    Now try decoder decode_export --help ... this will reveal the "secret":

    Usage:
    
        decode_export [ options ] [ -- ] [ password | serial maca ] [ [ < ] input-file ]
    
    Supported options are:
    
    -t, --tty              - don't quit execution, if STDIN is connected to a terminal device
    -a, --alt-env filename - use an alternative source for the 'urlader environment'
    -c, --checksum         - re-compute (and replace) the checksum for the provided export file, after
                             the cipher-text values were replaced with the corresponding clear-text
    -l, --low-memory       - do not try to consolidate input data into a single buffer
    -b, --block-size size  - read input data in blocks of the specified size
    -v, --verbose          - show additional information on STDERR
    -q, --quiet            - suppress any error messages on STDERR
    -s, --strict           - treat warnings as errors and exit
    -h, --help             - show this information (on STDOUT) and exit
    -V, --version          - show version (on STDOUT) and exit
    

    (and more explanations may be found there)

    HTH

    PS: Due to this is not really an "issue" (this means "a problem with the software", not "I don't know, how to use it."), so I'll convert this to a discussion thread.

  2. Repository owner locked and limited conversation to collaborators on May 13, 2022
  3. converted this issue into a discussion #28 on May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions