Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 7 subscribers
  • Views 5884 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Documentation of Safeguard LanCrypt file format

MichaelMessner

Hello Sophos community,

 during an internal evaluation of Sophos LanCrypt I was wondering if there is some documentation of the encrypted file format that Safeguard LC uses/generates. Do you have some resources to documentation on that format?

Thank you very much,

Mike



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hello Mike,

    If you're talking about the encryption algorithm LanCrypt uses to encrypt the files the clients can be configured to use XTS-AES or AES encryption.

  • 0 in reply to FormerMember

    Hello Toby,

     thanks for answering. I am more interested in the meaning of the different bytes within the encrypted file. For example you can identify the encrypted blog quite easy and then there is a header with some clear text which gives you the information that it is a SafeGuard FileEncryption file. Then you can identify the key identifier and so on, but there are some other areas/bytes that are not that clear.

    Is there some documentation which describes every byte in the file?

    Best,

    Mike

  • 0 in reply to MichaelMessner

    MichaelMessner said:

    Is there some documentation which describes every byte in the file?

    I am not sure if this is publicly available information. The first 4K is always our file encryption header, so encrypted files and the GUID of their KEK can always be identified.

    “First things first, but not necessarily in that order” – Doctor Who

Reply
  • 0 in reply to MichaelMessner

    MichaelMessner said:

    Is there some documentation which describes every byte in the file?

    I am not sure if this is publicly available information. The first 4K is always our file encryption header, so encrypted files and the GUID of their KEK can always be identified.

    “First things first, but not necessarily in that order” – Doctor Who

Children
No Data
Unfiltered HTML