| commit | 30f7a115f9ae9d0c259f04cabcc292a93598138c | [log] [tgz] |
|---|---|---|
| author | David Why Use Two When One Will Do Presotto <p@google.com> | Mon Aug 17 09:39:33 2015 -0700 |
| committer | David Why Use Two When One Will Do Presotto <p@google.com> | Mon Aug 17 09:39:33 2015 -0700 |
| tree | adf8160fea5b8eaa33ab9b939fb4ff442fee1cd7 | |
| parent | 8344434ea6c380f07a6a853ed142bca6c739b479 [diff] |
mounttablelib: correct limit enforcement - when reading from the log, we were always debiting against the server id, not the actual user. Hence we hit the allocation limit for the server. - we now debit against the correct user when replaying the log. We also don't enforce limits during replay. The code has been changed to pass a callContext that includes security information. This has the added advantage of avoiding a lot of redundant crypto that was happening whenever we looked at remote blessings. Change-Id: I9847e51164495985b37fb643c0b599f39243d925
This repository contains a reference implementation of the Vanadium APIs.
Unlike the APIs in https://github.com/vanadium/go.v23, which promises to provide backward compatibility this repository makes no such promises.