Release notes?
Appears to be encrypted with "E-SafeNet"
I read a
PDF and it's really rubbish encryption, if anybody can do Python there's a cracker here:
https://github.com/c3c/E-Safenet(I'm not a Python person, don't have it installed...)
Curious. It's on the Chinese web page (
www.rigol.com) but not on the "International" (int.rigol.com) website.
Who dares?
I did.
No more "Pluses" It was really a sort of trademark. And some sense of humor doesn't hurt!I was wrong, Pluses are still there
Vertical channel alignment is better in my unit. Mine had a very slight deviation between channels, it doesn't happen any longer.
Options still intact
Now I'm curious about the release notes.
On my MSO1074 worked as well, strangely enough, on the System Info version number didn't change ( 04.04.sp3) but trying to update again finds the software at the new version
.
Autocalibration in progress, let's see.
Cheers,
DC1MC
The last update (I have) is v00.04.04.03.02, this update is 00.04.04.03.05. So both versions are 00.04.04.03 :-)
Nice to know they have not completely abandoned this model.
I don't think there were any real bugs left. Maybe a few minor ones.
Or ... are there any new features?
(unlikely - the file size is almost identical)
Maybe the people over in the firmware hacking thread can put "Pluses" back in for us.
Are there no Python gurus reading this who can decrypt the release notes?
I don't think there were any real bugs left. Maybe a few minor ones.
The USB transfer speed as someone (is it Karel the DSRemote author ?) mentioned Rigol is not fully implementing certain USB standards if I'm not mistaken. I don't remember the details.
Return of sense of humour for Borjam the Horizontal Statistic selection menu now has Pulses spelt correctly but the actual displayed Stats at the bottom of the display is still Pluses. Oh well the next upgrade sigh!
DC1MC if you look at the detailed System Info via the rapid button pushing technique it displays the the full F/W status and it definitely is an 00.04.04.03.05 after the upgrade.
On my MSO1074 worked as well, strangely enough, on the System Info version number didn't change ( 04.04.sp3) but trying to update again finds the software at the new version .
Autocalibration in progress, let's see.
The ordinary system info doesn't show the final set of digits, only the first three.
DC1MC if you look at the detailed System Info via the rapid button pushing technique it displays the the full F/W status and it definitely is an 00.04.04.03.05 after the upgrade.
Menu -> Menu -> Force -> Menu -> Utility -> System -> System Info
But ... if the major numbers don't change then I think this could be a very minor update.
On my MSO1074 worked as well, strangely enough, on the System Info version number didn't change ( 04.04.sp3) but trying to update again finds the software at the new version .
Autocalibration in progress, let's see.
The ordinary system info doesn't show the final set of digits, only the first three.
DC1MC if you look at the detailed System Info via the rapid button pushing technique it displays the the full F/W status and it definitely is an 00.04.04.03.05 after the upgrade.
Menu -> Menu -> Force -> Menu -> Utility -> System -> System Info
But ... if the major numbers don't change then I think this could be a very minor update.
Well this a screenshot of this "magic"
info screen
Cheers,
DC1MC
Are there no Python gurus reading this who can decrypt the release notes?
I'm no Python guru, but I do know and use Python, and I'm trying to get to decrypt the release notes, but I'm not able to obtain yet any sensible cleartext.
I'm following the "probable plaintext attack" route, trying to feed pieces of the previous release notes.
It seems only the recent updates for the DS100Z and DS2000A have the release notes encrypted. Other f/w upgrades released this month are in plain text
as it should, with the oddball of the DG1KZ release notes being a UTF-16 file.
Are there no Python gurus reading this who can decrypt the release notes?
I'm no Python guru, but I do know and use Python, and I'm trying to get to decrypt the release notes, but I'm not able to obtain yet any sensible cleartext.
I'm following the "probable plaintext attack" route, trying to feed pieces of the previous release notes.
It seems only the recent updates for the DS100Z and DS2000A have the release notes encrypted. Other f/w upgrades released this month are in plain text as it should, with the oddball of the DG1KZ release notes being a UTF-16 file.
This encrypted file is also UTF-16 encoded, this why the ASCI decoder doesn't work
and it's a bit larger.
Probing with diverse parts I see now and then something like H i s t o r y and R e l e a s e, but the program replaces the zeroes in UTF-16 with spaces and itsn't able to deduce the key
The program needs to be adapted for UTF-16 in the plaintext mode, but this really needs someone who knows python and this is not me unfortunately.
DC1MC
This encrypted file is also UTF-16 encoded, this why the ASCI decoder doesn't work and it's a bit larger.
Probing with diverse parts I see now and then something like H i s t o r y and R e l e a s e, but the program replaces the zeroes in UTF-16 with spaces and itsn't able to deduce the key
The program needs to be adapted for UTF-16 in the plaintext mode, but this really needs someone who knows python and this is not me unfortunately.
I don't know Python but I'm guessing you have to add "or o == 0" at the end of line 86 of file partial_c.py
(in function "is_allowed_char")
This encrypted file is also UTF-16 encoded, this why the ASCI decoder doesn't work and it's a bit larger.
Probing with diverse parts I see now and then something like H i s t o r y and R e l e a s e, but the program replaces the zeroes in UTF-16 with spaces and itsn't able to deduce the key
The program needs to be adapted for UTF-16 in the plaintext mode, but this really needs someone who knows python and this is not me unfortunately.
I don't know Python but I'm guessing you have to add "or o == 0" at the end of line 86 of file partial_c.py
(in function "is_allowed_char")
Not that easy unfortunately, the whole program has to be modified for UTF-16
DC1MC
i think this is just a counter act on the hacked rigol fw thread, they probaly only correct Pluses in one place and thats it, and then encrypt it so no more low level hack. they dont even bother or dont know how to use "Find word" feature to correct all the Pluses, i guess they are on Win7 or later (Find file with keyword function in WinExplorer is real sucks). Possibly they also blocked hacked version from being installed in this version. If there is no substantial improvement, i will say there is no need to upgrade to this official version, we may keep an eye on the hacked fw thread. ymmv.
Release notes?
Appears to be encrypted with "E-SafeNet"
Why would one encrypt the release notes?
Why would one encrypt the release notes?
Perhaps the package was assembled using internal engineering documents, which could be encrypted to avoid possible 'leaks' to spill news before they are ready for the public release.
Those +Pluses -Pluses and RNAGe RNAG are exactly like in previous version
so for them they were already corrected and they think we are just joking...
Downgrade is possible in different ways and I believe hacking isn't problem
either. Comparing functions can give better overview what is changed.
Release notes?
Appears to be encrypted with "E-SafeNet"
I read a PDF and it's really rubbish encryption, if anybody can do Python there's a cracker here:
https://github.com/c3c/E-Safenet
(I'm not a Python person, don't have it installed...)
Here we go again!
00000000 - File Type: DS1000Z
00000010 - Software Branch/Version: 00.04.04.03.05
00000020 - Bitmask: 00000700
00000024 - # Sections: 10
Offset Section Name SectiSz StartAdr CRC32 Type
00000028 /sys/SparrowAPP.out 00109197 00000280 F0939219 00000001 [00000280-00109416] CRC OK
00000064 /sys/SparrowFPGA.hex 000C4372 00109417 D9C46F2E 00000005 [00109417-001CD788] CRC OK
000000A0 /sys/SparrowDGFPGA.hex 00046F04 001CD789 433D327B 00000006 [001CD789-0021468C] CRC OK
000000DC /sys/logo.hex 000BB818 0021468D C9D7EDE5 0000000A [0021468D-002CFEA4] CRC OK
00000118 /sys/guiResData.hex 000B6A2C 002CFEA5 322A3B01 0000000C [002CFEA5-003868D0] CRC OK
00000154 /sys/guiPicData.hex 0001E6BF 003868D1 7F322FAE 00000011 [003868D1-003A4F8F] CRC OK
00000190 /sys/SparrowConfig.hex 000BB818 003A4F90 DF2A2311 00000010 [003A4F90-004607A7] CRC OK
000001CC /sys/SparrowWaveTable.hex 000020E8 004607A8 C29BAD69 0000000B [004607A8-0046288F] CRC OK
00000208 /sys/SparrowCalFile.hex 0002329C 00462890 5613C891 0000000F [00462890-00485B2B] CRC OK
00000244 00000118 00485B2C 00000000 00000032 [00485B2C-00485C43]
Offset CRC32 Flags Filesize Endianes Branch/Version
00000280 FD9F4BF8 00000003 0010917F AA5555AA 00.04.04.03.05 [00000298-00109416] CRC OK
00109417 C9AF5D56 00000000 000C435A AA5555AA 00.04.04.03.05 [0010942F-001CD788] CRC OK
001CD789 138E13B9 00000000 00046EEC AA5555AA 00.04.04.03.05 [001CD7A1-0021468C] CRC OK
0021468D 9B4EA177 00000000 000BB800 AA5555AA 00.04.04.03.05 [002146A5-002CFEA4] CRC OK
002CFEA5 D7825E44 00000000 000B6A14 AA5555AA 00.04.04.03.05 [002CFEBD-003868D0] CRC OK
003868D1 01873014 00000001 0001E6A7 AA5555AA 00.04.04.03.05 [003868E9-003A4F8F] CRC OK
003A4F90 5DEF7058 00000000 000BB800 AA5555AA 00.04.04.03.05 [003A4FA8-004607A7] CRC OK
004607A8 558BD392 00000000 000020D0 AA5555AA 00.04.04.03.05 [004607C0-0046288F] CRC OK
00462890 7717C897 00000000 00023284 AA5555AA 00.04.04.03.05 [004628A8-00485B2B] CRC OK
Must be a minor bug correction since all other files are the same as in 00.04.04.03.02 and SparrowAPP is even 124 bytes shorter.
Regarding the encrypted release notes, I think they gave up on protecting the GEL and turned to the release notes!
Not that easy unfortunately, the whole program has to be modified for UTF-16
It shouldn't make any difference to the overall program.
The UTF-16 actually makes it a lot easier because you know what half the bytes of the plaintext are (assuming it's ASCII text like all the other release notes, every other byte will be zero).