[Commits] [wesnoth/wesnoth] 920508: Expose preferences to Lua

GitHub noreply at github.com
Sat Sep 17 06:32:23 UTC 2016


  Branch: refs/heads/expose-preferences-to-lua
  Home:   https://github.com/wesnoth/wesnoth
  Commit: 92050812309882ce47a1416ca1dbf797cf84b080
      https://github.com/wesnoth/wesnoth/commit/92050812309882ce47a1416ca1dbf797cf84b080
  Author: Jyrki Vesterinen <sandgtx at gmail.com>
  Date:   2016-09-17 (Sat, 17 Sep 2016)

  Changed paths:
    M changelog
    M projectfiles/VC12/wesnoth.vcxproj
    M projectfiles/VC12/wesnoth.vcxproj.filters
    M src/CMakeLists.txt
    M src/SConscript
    M src/scripting/lua_kernel_base.cpp
    A src/scripting/lua_preferences.cpp
    A src/scripting/lua_preferences.hpp

  Log Message:
  -----------
  Expose preferences to Lua


  Commit: ae52e83e24a7fbf2bfd3d02f66a209a698eb198a
      https://github.com/wesnoth/wesnoth/commit/ae52e83e24a7fbf2bfd3d02f66a209a698eb198a
  Author: Jyrki Vesterinen <sandgtx at gmail.com>
  Date:   2016-09-17 (Sat, 17 Sep 2016)

  Changed paths:
    M changelog
    M src/scripting/application_lua_kernel.cpp
    M src/scripting/lua_kernel_base.cpp

  Log Message:
  -----------
  Restrict preference access to plugins

@gfgtdf pointed out that preferences contain MP passwords. We can't allow
untrusted code to access them. Since we only need preference access from
plugins for now, the simplest way to avoid security issues is to block Lua
code outside of plugins from accessing preferences at all.


Compare: https://github.com/wesnoth/wesnoth/compare/56038bb212b8...ae52e83e24a7


More information about the Commits mailing list