Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
Olm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nheko Reborn
Olm
Commits
09dc3b60
Commit
09dc3b60
authored
6 years ago
by
Hubert Chathi
Browse files
Options
Downloads
Patches
Plain Diff
document a couple more places where olm clobbers things
parent
22f8649c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
include/olm/olm.h
+14
-14
14 additions, 14 deletions
include/olm/olm.h
with
14 additions
and
14 deletions
include/olm/olm.h
+
14
−
14
View file @
09dc3b60
...
...
@@ -320,13 +320,13 @@ int olm_session_has_received_message(
/** Checks if the PRE_KEY message is for this in-bound session. This can happen
* if multiple messages are sent to this account before this account sends a
* message in reply.
Returns 1 if the session matches
. Returns
0
if
the session
*
does not
match. Returns
olm_error() on failure. If the base64
*
couldn't be decoded then olm_session_last_error will be "INVALID_BASE64".
*
If the message was for an unsupported protocol version the
n
*
olm_session_last_error() will be "BAD_MESSAGE_VERSION". If the messag
e
*
couldn't be decoded then then olm_session_last_error() will be
* "BAD_MESSAGE_FORMAT". */
* message in reply.
The one_time_key_message buffer is destroyed
. Returns
1
if
*
the session
match
es
. Returns
0 if the session does not match. Returns
*
olm_error() on failure. If the base64 couldn't be decoded then
*
olm_session_last_error will be "INVALID_BASE64". If the message was for a
n
*
unsupported protocol version then olm_session_last_error() will b
e
*
"BAD_MESSAGE_VERSION". If the message couldn't be decoded then then
*
olm_session_last_error() will be
"BAD_MESSAGE_FORMAT". */
size_t
olm_matches_inbound_session
(
OlmSession
*
session
,
void
*
one_time_key_message
,
size_t
message_length
...
...
@@ -334,13 +334,13 @@ size_t olm_matches_inbound_session(
/** Checks if the PRE_KEY message is for this in-bound session. This can happen
* if multiple messages are sent to this account before this account sends a
* message in reply.
Returns 1 if the session matches
. Returns
0
if
the session
*
does not
match. Returns
olm_error() on failure. If the base64
*
couldn't be decoded then olm_session_last_error will be "INVALID_BASE64".
*
If the message was for an unsupported protocol version the
n
*
olm_session_last_error() will be "BAD_MESSAGE_VERSION". If the messag
e
*
couldn't be decoded then then olm_session_last_error() will be
* "BAD_MESSAGE_FORMAT". */
* message in reply.
The one_time_key_message buffer is destroyed
. Returns
1
if
*
the session
match
es
. Returns
0 if the session does not match. Returns
*
olm_error() on failure. If the base64 couldn't be decoded then
*
olm_session_last_error will be "INVALID_BASE64". If the message was for a
n
*
unsupported protocol version then olm_session_last_error() will b
e
*
"BAD_MESSAGE_VERSION". If the message couldn't be decoded then then
*
olm_session_last_error() will be
"BAD_MESSAGE_FORMAT". */
size_t
olm_matches_inbound_session_from
(
OlmSession
*
session
,
void
const
*
their_identity_key
,
size_t
their_identity_key_length
,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment