github/greenshot
1
0
Fork 0
mirror of https://github.com/greenshot/greenshot synced 2025-08-20 21:43:24 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add Update about 1.3 bugfix version and fix typo

Browse source
This commit is contained in:
jklingen 2025-07-18 11:02:52 +02:00 • committed by GitHub
commit f3277621b9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
_posts/2025-07-14-final-release-greenshot-1-3.markdown
View file

@ -9,14 +9,16 @@ tags:
--- ---
# 🎉 Greenshot v1.3.290 RC1 Released — Fixed Vulnerability, Zoom, improved HiDPI awareness & More! # 🎉 Greenshot v1.3 Released — Fixed Vulnerability, Zoom, improved HiDPI awareness & More!
**Update 2025-07-17: we have published a bug fix release (v1.3.202) which fixes some problems when running the installer as administrator.**
We're excited to announce the release of **Greenshot v1.3.290 (Final Release)** – a significant step forward for one of the most popular open-source screenshot tools for Windows. We're excited to announce the release of **Greenshot v1.3.290 (Final Release)** – a significant step forward for one of the most popular open-source screenshot tools for Windows.
This version introduces **new features**, **UI improvements**, and **important bug fixes** that refine the overall user experience. This version introduces **new features**, **UI improvements**, and **important bug fixes** that refine the overall user experience.
## 🛠 Fixed Vulerability Issue ## 🛠 Fixed Vulnerability Issue
Greenshot 1.2.10 and below allowed arbitrary code execution because .NET content is insecurely deserialized when a .greenshot file is opened. Greenshot 1.2.10 and below allowed arbitrary code execution because .NET content is insecurely deserialized when a .greenshot file is opened.
This long awaited fix has already been provided in unstable versions and now found it's way into the final release of version 1.3. This long awaited fix has already been provided in unstable versions and now found it's way into the final release of version 1.3.