Unmerged flask notebook (#11080 and related)

62 views
Skip to first unread message

Jeroen Demeyer

unread,
Jul 23, 2012, 3:06:35 AM7/23/12
to sage-n...@googlegroups.com, sage-r...@googlegroups.com
Due to a serious security issue with the new Flask notebook (see
#13270), it has been decided on that ticket not to ship sage-5.2 with
sagenb-0.9.0.

Since I see no reason why the other tickets in sage-5.2 couldn't be
released, I will unmerge #11080 and related tickets and release sage-5.2
still with the old notebook.

If you don't care about #13270, feel free to use sage-5.2.rc0:
http://boxen.math.washington.edu/home/release/sage-5.2.rc0/

It's a pity that this has to happen, but we need to move on,
Jeroen.

Dima Pasechnik

unread,
Jul 23, 2012, 3:39:24 AM7/23/12
to sage-n...@googlegroups.com, sage-r...@googlegroups.com
hmm, did anyone try to debug this?
If we come up with a fix in 24 hours, say?

Dima Pasechnik

unread,
Jul 23, 2012, 6:38:32 AM7/23/12
to sage-r...@googlegroups.com, sage-n...@googlegroups.com
I think that thanks to Basu we have a patch for this problem on #11080.

Could we please, please, have it added and everything related re-merged back?


On Monday, 23 July 2012 15:06:35 UTC+8, Jeroen Demeyer wrote:

Jeroen Demeyer

unread,
Jul 23, 2012, 6:42:15 AM7/23/12
to sage-n...@googlegroups.com
On 2012-07-23 12:38, Dima Pasechnik wrote:
> I think that thanks to Basu we have a patch for this problem on #11080.
> http://trac.sagemath.org/sage_trac/attachment/ticket/11080/trac_11080-user_registration.patch
>
> Could we please, please, have it added and everything related re-merged
> back?
Somebody needs to create a sagenb spkg fixing this and add this to
#13270, and it needs to be reviewed.

Dima Pasechnik

unread,
Jul 23, 2012, 9:29:47 AM7/23/12
to sage-n...@googlegroups.com
it is done. 

Jeroen Demeyer

unread,
Jul 25, 2012, 2:39:07 AM7/25/12
to sage-n...@googlegroups.com
On 2012-07-23 09:06, Jeroen Demeyer wrote:
> Due to a serious security issue with the new Flask notebook (see
> #13270), it has been decided on that ticket not to ship sage-5.2 with
> sagenb-0.9.0.

Since #13270 is fixed, that decision has been undone, and sage-5.2.rc1
now contains sagenb-0.9.1.
Reply all
Reply to author
Forward
0 new messages