Hi developers,
Mohit and I are working on some aspect of Designer, specifically the
js/designer/history.js file and anything relating to the history
feature within Designer. This doesn't seem familiar to me; I don't
recall any aspect of Designer that relates to using any history.
Further, trying to break in to this code and show a debugging message
(as you can see in the screenshot) doesn't seem to work, either (it
does, for instance, in js/designer/init.js), so I'm pretty stumped
about what this block of code is for. Does anyone have familiarity
with this to help nudge us in the right direction?
Thanks,
Isaac
> ---------- Forwarded message ----------
> From: MOHIT KURi <ikurimohit(a)gmail.com>
> To: developers(a)phpmyadmin.net
> Date: Fri, 7 Jun 2019 14:03:58 +0530
> Subject: Testing in Designer
> Hi everyone,
>
> I have been trying to print and test(using alert) some values inside the functions of history.js of the designer. I couldn't figure it out that where are we calling the different functions(display function here as an example) of the designer's history and thus how can I print and test some values. Can someone please help me here?
>
> Like here in the attached image(belongs to js/designer/history.js), by performing what set of actions can I get this 'alert("inside display")' to be executed?
> Would be great if you can provide steps for this.
>
> Thanks & Regards,
> Mohit Kuri
Hello,
I made a slight mistake creating version 4.9.0 and did not include the
fix for the attack against Designer. I've quickly released 4.9.0.1 to
address this.
Isaac for the phpMyAdmin team
Welcome to phpMyAdmin 4.9.0, a bugfix release that includes important
security fixes.
This release fixes two security vulnerabilities:
* PMASA-2019-3 is an SQL injection flaw in the Designer feature
* PMASA-2019-4 is a CSRF attack that's possible through the 'cookie'
login form
Upgrading is highly recommended for all users. Using the 'http'
auth_type instead of 'cookie' can mitigate the CSRF attack.
The solution for the CSRF attack does remove the former functionality to
log in directly through URL parameters (as mentioned in FAQ 4.8, such as
https://example.com/phpmyadmin/?pma_username=root&password=foo). Such
behavior was discouraged and is now removed. Other query parameters work
as expected; only pma_username and pma_password have been removed.
This release also includes fixes for many bugs, including:
- Several issues with SYSTEM VERSIONING tables
- Fixed json encode error in export
- Fixed JavaScript events not activating on input (sql bookmark issue)
- Show Designer combo boxes when adding a constraint
- Fix edit view
- Fixed invalid default value for bit field
- Fix several errors relating to GIS data types
- Fixed javascript error PMA_messages is not defined
- Fixed import XML data with leading zeros
- Fixed php notice, added support for 'DELETE HISTORY' table privilege
(MariaDB >= 10.3.4)
- Fixed MySQL 8.0.0 issues with GIS display
- Fixed "Server charset" in "Database server" tab showing wrong information
- Fixed can not copy user on Percona Server 5.7
- Updated sql-parser to version 4.3.2, which fixes several parsing and
linting problems
There are many, many more bug fixes thanks to the efforts of our
developers, Google Summer of Code applicants, and other contributors.
The phpMyAdmin team
Hello,
This is an advanced notification that the phpMyAdmin team is preparing a
security release to address two issues that have been reported.
The release is planned for tomorrow, that is, in roughly 18-20 hours
from the time of this message.
This message is part of a continuing effort to provide advanced
notification (when possible) for upcoming security announcements.
Thank you,
Isaac for the phpMyAdmin team
