We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operating system: Linux ssh 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-1kali1 (2021-06-25) x86_64 GNU/Linux
Linux ssh 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-1kali1 (2021-06-25) x86_64 GNU/Linux
Build version (signal-back --version):
signal-back --version
└─$ ./signal-back_linux_amd64 --version signal-back v0.1.6-dirty proto commit: d6610f0
I am unable to extract ANY messages when using signal-back. I am however able to run:
└─$ ./signal-back_linux_amd64 extract -o output signal-2021-08-18-16-03-23.backup
And the signal-back successfully extracts all attachments from the backup.
I have tried using the same build on Windows 10 and have got the same results.
Any help or suggestions would be greatly appreciated.
Getting the following error when running analyse:
analyse
└─$ ./signal-back_linux_amd64 analyse signal-2021-08-18-16-03-23.backup Password: <REDACTED> This is still largely in flux and reflects whatever task I was having issues with at the time. map[insert_into_part:1123 insert_into_drafts:2 attachment:517 insert_into_identities:13 insert_into_groups:25 insert_into_group_receipts:80 versio n:1 create_table:28 create_index:42 other_stmt:12 insert_into_sticker:1] part: 42 statement:"INSERT INTO part VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)" parameters:<int egerParameter:2 > parameters:<integerParameter:2 > parameters:<integerParameter:0 > parameters:<stringParamter:"image/jpeg" > parameters:<nullpara meter:true > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<nullparameter:true > p arameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<int egerParameter:0 > parameters:<stringParamter:"/data/data/org.thoughtcrime.securesms/app_parts/part-1577011632.mms" > parameters:<integerParameter: 160682 > parameters:<nullparameter:true > parameters:<stringParamter:"/data/data/org.thoughtcrime.securesms/app_parts/part946133067.mms" > paramet ers:<doubleParameter:0.7920634746551514 > parameters:<integerParameter:1475912214356 > parameters:<nullparameter:true > parameters:<nullparameter: true > parameters:<integerParameter:0 > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<integerParameter:0 > paramet ers:<integerParameter:0 > parameters:<integerParameter:0 > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<nullparam eter:true > parameters:<integerParameter:18446744073709551615 > parameters:<nullparameter:true > parameters:<nullparameter:true > parameters:<null parameter:true > parameters:<nullparameter:true > parameters:<integerParameter:0 > parameters:<integerParameter:0 > parameters:<integerParameter:0 > parameters:<integerParameter:0 > parameters:<nullparameter:true > parameters:<integerParameter:0 >
Running:
└─$ ./signal-back_linux_amd64 format -f CSV -o backup.csv signal-2021-08-18-16-03-23.backup -v Password: <REDACTED>
Results in no console output, but cat backup.csv returns the following output:
ID,THREAD_ID,ADDRESS,ADDRESS_DEVICE_ID,PERSON,DATE_RECEIVED,DATE_SENT,PROTOCOL,READ,STATUS,TYPE,REPLY_PATH_PRESENT,DELIVERY_RECEIPT_COUNT,SUBJECT,BODY,MISMATCHED_IDENTITIES,SERVICE_CENTER,SUBSCRIPTION_ID,EXPIRES_IN,EXPIRE_STARTED,NOTIFIED,READ_RECEIPT_COUNT
└─$ ./signal-back_linux_amd64 format -f XML -o backup.xml signal-2021-08-18-16-03-23.backup -v 130 ⨯ Password: <REDACTED>
Results in no console output, but cat backup.xml returns the following output:
└─$ cat backup.xml <?xml version='1.0' encoding='UTF-8' standalone='yes' ?> <?xml-stylesheet type="text/xsl" href="sms.xsl" ?> <smses count="0"></smses>
The text was updated successfully, but these errors were encountered:
Seeing this as well.
Sorry, something went wrong.
I am experiencing same on darwin_amd64. Both in XML and CSV format. No data, only headers/surrounding tags.
Same sad noises I was able to get the RAW to work from this project https://github.com/pajowu/signal-backup-decode
Same issue here
No branches or pull requests
Operating system:
Linux ssh 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-1kali1 (2021-06-25) x86_64 GNU/Linux
Build version (
signal-back --version
):Detailed description
I am unable to extract ANY messages when using signal-back. I am however able to run:
└─$ ./signal-back_linux_amd64 extract -o output signal-2021-08-18-16-03-23.backup
And the signal-back successfully extracts all attachments from the backup.
I have tried using the same build on Windows 10 and have got the same results.
Any help or suggestions would be greatly appreciated.
Full relevant output
Getting the following error when running
analyse
:Running:
Results in no console output, but cat backup.csv returns the following output:
Running:
Results in no console output, but cat backup.xml returns the following output:
The text was updated successfully, but these errors were encountered: