Skip to contentSkip to conversation

package/openocd: bump to version 104a5cb

PATCH New Frank Hunleth 2 participants 3 messages Dec 17, 2019 – Dec 22, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 package/openocd: bump to version 104a5cb

The OpenOCD project hasn't made a release since January 2017. Much work has happened since then and now. This bumps the version to the latest commit and removes a patch that has been applied upstream.

---
 ...event-some-forms-of-Cross-Protocol-S.patch | 50 -------------------
 package/openocd/openocd.hash                  |  5 +-
 package/openocd/openocd.mk                    |  7 +--
 3 files changed, 6 insertions(+), 56 deletions(-)
 delete mode 100644 package/openocd/0003-CVE-2018-5704-Prevent-some-forms-of-Cross-Protocol-S.patch
package/openocd/0003-CVE-2018-5704-Prevent-some-forms-of-Cross-Protocol-S.patch deleted +0 -50
deleted file mode 100644
index ba19bf5735..0000000000
@@ -1,50 +0,0 @@
-From 3a223ca3ebc7ac24d7726a0cd58e5695bc813657 Mon Sep 17 00:00:00 2001
-From: Andreas Fritiofson <[email protected]>
-Date: Sat, 13 Jan 2018 21:00:47 +0100
-Subject: [PATCH] CVE-2018-5704: Prevent some forms of Cross Protocol Scripting
- attacks
-
-OpenOCD can be targeted by a Cross Protocol Scripting attack from
-a web browser running malicious code, such as the following PoC:
-
-var x = new XMLHttpRequest();
-x.open("POST", "http://127.0.0.1:4444", true);
-x.send("exec xcalc\r\n");
-
-This mitigation should provide some protection from browser-based
-attacks and is based on the corresponding fix in Redis:
-
-https://github.com/antirez/redis/blob/8075572207b5aebb1385c4f233f5302544439325/src/networking.c#L1758
-
-
-Upstream-status: Under review: http://openocd.zylin.com/#/c/4335/
-Change-Id: Ia96ebe19b74b5805dc228bf7364c7971a90a4581
-Signed-off-by: Andreas Fritiofson <[email protected]>
-Reported-by: Josef Gajdusek <[email protected]>
-Signed-off-by: Peter Korsgaard <[email protected]>
----
- src/server/startup.tcl | 11 +++++++++++
- 1 file changed, 11 insertions(+)
-
-diff --git a/src/server/startup.tcl b/src/server/startup.tcl
-index 64ace407..dd1b31e4 100644
---- a/src/server/startup.tcl
-+++ b/src/server/startup.tcl
-@@ -8,3 +8,14 @@ proc ocd_gdb_restart {target_id} {
- 	# one target
- 	reset halt
- }
-+
-+proc prevent_cps {} {
-+	echo "Possible SECURITY ATTACK detected."
-+	echo "It looks like somebody is sending POST or Host: commands to OpenOCD."
-+	echo "This is likely due to an attacker attempting to use Cross Protocol Scripting"
-+	echo "to compromise your OpenOCD instance. Connection aborted."
-+	exit
-+}
-+
-+proc POST {args} { prevent_cps }
-+proc Host: {args} { prevent_cps }
--- 
-2.11.0
-
package/openocd/openocd.hash +2 -3
index 3fb817b4a2..8575cd825d 100644
@@ -1,4 +1,3 @@
-# From http://sourceforge.net/projects/openocd/files/openocd/0.10.0/
-sha1 3245d43d60a1a93f8b0f6b1ce20b53e38cab7a4a  openocd-0.10.0.tar.bz2
-md5 b412bdef0481a3859c6585eb69f6f6ba  openocd-0.10.0.tar.bz2
+# Locally calculated
+sha256 a88acc1e7fc9af0d91d56041923b80563be7b17b2198a21c6c2656ce596ccd16  openocd-104a5cbef8965d47b9111f7e010f96ebb5fdf06c.tar.gz
 sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  COPYING
package/openocd/openocd.mk +4 -3
index d35ed77cd1..0a3f1c9a21 100644
@@ -4,9 +4,10 @@
 #
 ################################################################################
 
-OPENOCD_VERSION = 0.10.0
-OPENOCD_SOURCE = openocd-$(OPENOCD_VERSION).tar.bz2
-OPENOCD_SITE = http://sourceforge.net/projects/openocd/files/openocd/$(OPENOCD_VERSION)
+OPENOCD_VERSION = 104a5cbef8965d47b9111f7e010f96ebb5fdf06c
+OPENOCD_SITE = git://git.code.sf.net/p/openocd/code
+OPENOCD_METHOD = git
+OPENOCD_GIT_SUBMODULES = YES
 OPENOCD_LICENSE = GPL-2.0+
 OPENOCD_LICENSE_FILES = COPYING
 # 0002-configure-enable-build-on-uclinux.patch patches configure.ac
Signature · 1 line
2.20.1
#1 lore raw

PATCH 1/1 package/openocd: bump to version 104a5cb

Hello Frank,

Quoted 5 lines · On Tue, 17 Dec 2019 18:26:57 -0500 Frank Hunleth…

The OpenOCD project hasn't made a release since January 2017. Much work has happened since then and now. This bumps the version to the latest commit and removes a patch that has been applied upstream.

Overall, it certainly looks good to bump OpenOCD, since indeed the project is essentially no longer tagging any "official" release.

However, there a few changes that I'd like to see:

- Sync with Fabrice Fontaine, who posted a patch that drops the internal jimctl usage, and instead uses our jimtcl package.

- Create a separate package for libjaylink, and use it in OpenOCD.

- Thanks to the above two points, drop the OPENOCD_GITSUBMODULES = YES variable.

- Perhaps use the Git mirror at https://repo.or.cz/w/openocd.git,
which is accessible over https://, and therefore will work better for some users behind corporate firewalls.

Could you rework your submission according to these suggestions?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

PATCH 1/1 package/openocd: bump to version 104a5cb

Quoted 11 lines · On Sun, 22 Dec 2019 13:50:26 +0100 Thomas Petazzoni…

Hello Frank,

Quoted 5 lines · On Tue, 17 Dec 2019 18:26:57 -0500 Frank Hunleth…

The OpenOCD project hasn't made a release since January 2017. Much work has happened since then and now. This bumps the version to the latest commit and removes a patch that has been applied upstream.

Quoted 7 lines

Overall, it certainly looks good to bump OpenOCD, since indeed the project is essentially no longer tagging any "official" release.

However, there a few changes that I'd like to see:

- Sync with Fabrice Fontaine, who posted a patch that drops the internal jimctl usage, and instead uses our jimtcl package.

In the mean time, the patch from Fabrice has been merged, so the internal jimtcl of OpenOCD is no longer needed.

My following points remain valid, though.

Quoted 11 lines

- Create a separate package for libjaylink, and use it in OpenOCD.

- Thanks to the above two points, drop the OPENOCD_GITSUBMODULES = YES variable.

- Perhaps use the Git mirror at https://repo.or.cz/w/openocd.git,
which is accessible over https://, and therefore will work better for some users behind corporate firewalls.

Could you rework your submission according to these suggestions?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com