New tool available to decrypt encryped N900 backups without a N900

Thanks to Pali finding some old osso-backup source in
http://repository.maemo.org/pool/maemo3.2/free/source/, I was able to build
a tool that decrypts encrypted osso-backup files without the need to have a
working N900 Fremantle install.

The download is at http://www.cncmods.net/files/backupdec.zip and is
compiled via backupdec.sh. It will compile in scratchbox if you have
libosso-gsf-1-dev, libglib-2.0-dev and libssl-dev installed or it should
compile in a normal linux environment if you have normal libgsf, glib and
openssl headers installed (you will need to edit the sh file pkg-config
options for this)

To run the compiled binary, run backupdec in out password where in is the
encrypted zip file from the backup, out is the name of the output
unencrypted zip file and password is the password used when the zip file
was created.

It can also be used to decrypt zip files on the N900 itself if you want to
decrypt the files without actually restoring the backup. (i.e. build an arm
binary of this and run it on the phone)

If someone has a specific need for a binary of this built for a specific
platform, let me know and I will see what I can do to get a binary.

Jonathan Wilson wrote:
> Thanks to Pali finding some old osso-backup source in
> http://repository.maemo.org/pool/maemo3.2/free/source/, I was able to build
> a tool that decrypts encrypted osso-backup files without the need to have a
> working N900 Fremantle install.
>
> The download is at http://www.cncmods.net/files/backupdec.zip and is
> compiled via backupdec.sh. It will compile in scratchbox if you have
> libosso-gsf-1-dev, libglib-2.0-dev and libssl-dev installed or it should
> compile in a normal linux environment if you have normal libgsf, glib and
> openssl headers installed (you will need to edit the sh file pkg-config
> options for this)
>
> To run the compiled binary, run backupdec in out password where in is the
> encrypted zip file from the backup, out is the name of the output
> unencrypted zip file and password is the password used when the zip file
> was created.
>
> It can also be used to decrypt zip files on the N900 itself if you want to
> decrypt the files without actually restoring the backup. (i.e. build an arm
> binary of this and run it on the phone)
>
> If someone has a specific need for a binary of this built for a specific
> platform, let me know and I will see what I can do to get a binary.
The source code here is released under the GPL if you want to re-use it.

Also, this only works if you know the actual password as the encryption is
too strong to brute force it.

On Monday 05 March 2012 18:34:55 Jonathan Wilson wrote:
> Thanks to Pali finding some old osso-backup source in
> http://repository.maemo.org/pool/maemo3.2/free/source/, I was able to build
> a tool that decrypts encrypted osso-backup files without the need to have a
> working N900 Fremantle install.
>
> The download is at http://www.cncmods.net/files/backupdec.zip and is
> compiled via backupdec.sh. It will compile in scratchbox if you have
> libosso-gsf-1-dev, libglib-2.0-dev and libssl-dev installed or it should
> compile in a normal linux environment if you have normal libgsf, glib and
> openssl headers installed (you will need to edit the sh file pkg-config
> options for this)
>
> To run the compiled binary, run backupdec in out password where in is the
> encrypted zip file from the backup, out is the name of the output
> unencrypted zip file and password is the password used when the zip file
> was created.
>
> It can also be used to decrypt zip files on the N900 itself if you want to
> decrypt the files without actually restoring the backup. (i.e. build an arm
> binary of this and run it on the phone)
>
> If someone has a specific need for a binary of this built for a specific
> platform, let me know and I will see what I can do to get a binary.

Hi, thanks very much for decrypting backup file format!

--
Pali Rohár
pali.rohar@gmail.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk9Umw0ACgkQi/DJPQPkQ1LXTQCeIrU/PEj7m3EP7TscE8SNeXE0
eWIAoIdoVsHxWDguFMyytWBGZJLk+pka
=2xqG
-----END PGP SIGNATURE-----

Hi,

i can't figure out how to use glext on n900 or on the n950 using gles1.

As a start i'd just like to access
glGenFramebuffers() and
glDeleteFramebuffers()

The only references to this is in GLES/glext.h and the prototypes have
are named glGenFramebuffersOES and glDeleteFramebuffersOES . So far
so good. I can compile this.

But i cannot link it. Against what am i supposed to link gles1 applications
using glext?

Regards,
Till

--
Dr. Till Harbaum <lists@harbaum.org>

glext.h looks like driver-specific extensions, am I right (at least the
internet seems to tell so)? So there is no guarantee if the driver has
them or not...

-Kimmo

On 03/07/12 17:28, ext Till Harbaum / Lists wrote:
> Hi,
>
> i can't figure out how to use glext on n900 or on the n950 using gles1.
>
> As a start i'd just like to access
> glGenFramebuffers() and
> glDeleteFramebuffers()
>
> The only references to this is in GLES/glext.h and the prototypes have
> are named glGenFramebuffersOES and glDeleteFramebuffersOES . So far
> so good. I can compile this.
>
> But i cannot link it. Against what am i supposed to link gles1 applications
> using glext?
>
> Regards,
> Till
>
> --
> Dr. Till Harbaum<lists@harbaum.org>
>

Since gles 1.1 glex is imho mandatory

Till

Am Freitag 09 März 2012 schrieb Kimmo Hämäläinen:
> glext.h looks like driver-specific extensions, am I right (at least the
> internet seems to tell so)? So there is no guarantee if the driver has
> them or not...
>
> -Kimmo
>
> On 03/07/12 17:28, ext Till Harbaum / Lists wrote:
> > Hi,
> >
> > i can't figure out how to use glext on n900 or on the n950 using gles1.
> >
> > As a start i'd just like to access
> > glGenFramebuffers() and
> > glDeleteFramebuffers()
> >
> > The only references to this is in GLES/glext.h and the prototypes have
> > are named glGenFramebuffersOES and glDeleteFramebuffersOES . So far
> > so good. I can compile this.
> >
> > But i cannot link it. Against what am i supposed to link gles1 applications
> > using glext?
> >
> > Regards,
> > Till
> >
> > --
> > Dr. Till Harbaum<lists@harbaum.org>
> > _______________________________________________
> > maemo-developers mailing list
> > maemo-developers@maemo.org
> > https://lists.maemo.org/mailman/listinfo/maemo-developers
> >
>

And for the records: As far as i understand by now the glex lib (if present) just wraps wglGetProcAddress (or similar) which in turn resolves the addresses if the various extensions via their name. So it should just be a matter of calling this getprocaddress function with the correct parameters.

Till

Am Freitag 09 März 2012 schrieb Kimmo Hämäläinen:
> glext.h looks like driver-specific extensions, am I right (at least the
> internet seems to tell so)? So there is no guarantee if the driver has
> them or not...
>
> -Kimmo
>
> On 03/07/12 17:28, ext Till Harbaum / Lists wrote:
> > Hi,
> >
> > i can't figure out how to use glext on n900 or on the n950 using gles1.
> >
> > As a start i'd just like to access
> > glGenFramebuffers() and
> > glDeleteFramebuffers()
> >
> > The only references to this is in GLES/glext.h and the prototypes have
> > are named glGenFramebuffersOES and glDeleteFramebuffersOES . So far
> > so good. I can compile this.
> >
> > But i cannot link it. Against what am i supposed to link gles1 applications
> > using glext?
> >
> > Regards,
> > Till
> >
> > --
> > Dr. Till Harbaum<lists@harbaum.org>
> > _______________________________________________
> > maemo-developers mailing list
> > maemo-developers@maemo.org
> > https://lists.maemo.org/mailman/listinfo/maemo-developers
> >
>