Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fake webId on LongChat #36

Open
scenaristeur opened this issue Mar 3, 2020 · 3 comments
Open

Fake webId on LongChat #36

scenaristeur opened this issue Mar 3, 2020 · 3 comments
Labels
bug Something isn't working security

Comments

@scenaristeur
Copy link

For Solidarity, or any LongChat on Solid, it is really easy to make a fake message as @aveltens pointed.
As the folder is open to everyone in writing, @aveltens wrote a message with a dc:creator Tim's webId. So I thought Tim has wrote the message.
And everyone can make a message with any webId.
This is a real problem, how can we be sure that the message is posted by the good webId
Screenshot_20200303-082939_Chrome

Can the server allow only writing when the webId is the same as the dc:creator ? But I use ldflex-query, that don't use batch/transaction, so how could be a whole transaction ( a group of statements ) blocked if webId is not dc:creator ?

@megoth megoth added the bug Something isn't working label Mar 4, 2020
@timbl
Copy link
Contributor

timbl commented Mar 5, 2020

Yes the way chat works is naive from the security point of view.

We'd need to check the whole shape, in fact, including the author as being really the user. We could also add to a shape automatic stamping with user and timestamp.

Another way would be for each person to create and edit their own chat.ttl, and merge the messages from all of them, but we would need server functionality to automatically set the ACL for that file up.

@timbl timbl added the security label Mar 5, 2020
@timbl
Copy link
Contributor

timbl commented Mar 8, 2020

(Another whole direction is to request a change log to be kept for the resource. One keep the log of all the patches sent including their user, time, possibly IP address, etc. Anything added by a given user would be attributed in the chat to that user.)

@timbl
Copy link
Contributor

timbl commented Mar 8, 2020

Other directions to go include digital signature of the message by the author.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working security
Projects
None yet
Development

No branches or pull requests

3 participants