SRX300 Firmware

vangoose

Active Member
May 21, 2019
268
70
28
Canada
For anyone upgrading from 15 train, read juniper document before upgrading to 18, there is syntax change.
 
Jan 10, 2019
85
17
8
blog.azureinfra.com
hi

please note that the CHECKSUM does NOT comply with the official ones you can download from Juniper website..

18.4R3
MD5 : eec1a878079c4ca37b997ddd40cf95f9
SHA1 : 5827f906e58f6af35ad28978c948cdc3df6f756c
SHA256 : fb2b8bec261d67196bb9b49d63a5378385bb7577f2626977e207e9f1b2ba395c
SHA512 : 4e9e9e8f18e051713d425b4cbe3c2400bb173db0ff3d9e1328172481632a4c559af3235c371d41116740fe10733311be526350654fc490a5b16de460f69cc281

file:
SHA256: 2DE6B753371494E0C4F19602994F9090A9E376E784394564E8362D0686DC710D
 
  • Like
Reactions: klui

vangoose

Active Member
May 21, 2019
268
70
28
Canada
hi

please note that the CHECKSUM does NOT comply with the official ones you can download from Juniper website..

18.4R3
MD5 : eec1a878079c4ca37b997ddd40cf95f9
SHA1 : 5827f906e58f6af35ad28978c948cdc3df6f756c
SHA256 : fb2b8bec261d67196bb9b49d63a5378385bb7577f2626977e207e9f1b2ba395c
SHA512 : 4e9e9e8f18e051713d425b4cbe3c2400bb173db0ff3d9e1328172481632a4c559af3235c371d41116740fe10733311be526350654fc490a5b16de460f69cc281

file:
SHA256: 2DE6B753371494E0C4F19602994F9090A9E376E784394564E8362D0686DC710D

This checksum is for 18.4R3

The one I posted is 18.4R3-S4.2, the TAC recommended version.

Don't download it if you don't want to trust it.
 

vangoose

Active Member
May 21, 2019
268
70
28
Canada
Hi,

ok.. then the difference makes sense.. but can find the checksum for S4.2...

just trying to be cautious
You are totally right, I wouldn't download the random firmware from internet to put it on my firewall if I don't know where it's coming from.

I should've put disclaim there, if you don't trust me, don't download it.

I bought a brand new licensed SRX 300 last year that comes with 1 year support. Even with that, register with juniper was still a hassle.
 
  • Like
Reactions: klui

klui

Active Member
Feb 3, 2019
176
73
28
The packages within are signed. There could be hash collisions but I would think Juniper has started using sha256 or sha512 for their installation checks.