Hi Léa Raya,
RE UP-3640 and UP-3665, I think that is from uPortal 4.1 dropping
support for Tomcat 6 and only supporting Tomcat 7+.
RE UP-3642, I believe we are only supporting last 2 IE versions (IE-10
and IE-11), so there is no longer a need to safeguard console (which was
back in IE 7 or something).
RE UP-4106, Andrew P is best to respond.
James Wennmacher - Unicon
480.558.2420
On 07/07/2014 02:17 AM, Léa Raya DÉCORNOD wrote:
Le lundi 07 juillet 2014 03:02:33 Andrew Petro a écrit :
Made some good progress towards 4.1.0 release […].
Andrew
Hi uPortal developers,
During a rebasing of a forked uportal-4.0.14…uportal-4.0.6.SR1¹ onto
uportal-4.1.0-RC2, I came across 4 specific commits from 4.0 branch where I
didn't found a matching² commit/code in 4.1 timeline.
— UP-3640 → https://issues.jasig.org/browse/UP-3640
seems to be resolved differently by UP-3298 in 4.1 line.
— UP-3665 → https://issues.jasig.org/browse/UP-3665
seems to me, to be related to ↑UP-3640 so may be irrelevant to 4.1 line.
— UP-3642 → https://issues.jasig.org/browse/UP-3642
UP-3981 removed console.log(…) lines from personLookup.jsp,
but not from the three other files (grep -rF console.log .)…
UP-3642 might be cherry-picked if relevant (there's only one unchecked console
access left in entity-selector.js I guess)
$ git cherry-pick $(git rev-list --grep=UP-3642 uportal-4.0.14)
$ git checkout HEAD -- uportal-war/src/main/webapp/WEB-INF/flows/person-
lookup/personLookup.jsp
$ git cherry-pick --continue
— UP-4106 → https://issues.jasig.org/browse/UP-4106
CVE-2014-3417 (Illicit access to Config mode) is marked as fixed in JIRA but the
commit still may be cherry-picked without many unresolvable conflicts (through
my non-expert eyes however).
I thought that these ↑ might eventually interest some of you, so I shared that
here. Sorry for the noise if not.
Regards,
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
