http authentication bug after daa8 commit?
|
2017-01-03, 01:38
Post: #3
|
|||
|
|||
RE: http authentication bug after daa8 commit?
(2017-01-02 11:48)robinsmidsrod Wrote: There was a patch recently that made it possible to disable the Tivoli workaround with a configuration change. You might want to try it with the Tivoli workaround disabled. There is no problem with the Tivoli workaround. It's the next commit "Provide intf_reinit() to reinitialise nullified interfaces" (https://git.ipxe.org/ipxe.git/commit/daa...2c98b0a11a) the one that introduces the bug. After the "Provide intf_reinit() to reinitialise nullified interfaces" commit, the HTTP request always return with the the "Permission denied" error. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
http authentication bug after daa8 commit? - murmansk - 2016-12-28, 13:24
RE: http authentication bug after daa8 commit? - robinsmidsrod - 2017-01-02, 11:48
RE: http authentication bug after daa8 commit? - murmansk - 2017-01-03 01:38
RE: http authentication bug after daa8 commit? - vtwaldo21 - 2017-01-31, 23:00
RE: http authentication bug after daa8 commit? - NiKiZe - 2017-02-02, 22:36
RE: http authentication bug after daa8 commit? - murmansk - 2017-02-03, 15:32
|
User(s) browsing this thread: 1 Guest(s)