[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #26151 [Obfuscation/Snowflake]: Snowflake rendezvous using Amazon SQS
#26151: Snowflake rendezvous using Amazon SQS
---------------------------------------+--------------------
Reporter: dcf | Owner: (none)
Type: project | Status: new
Priority: Medium | Milestone:
Component: Obfuscation/Snowflake | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
---------------------------------------+--------------------
Nathan Freitas suggests using
[https://en.wikipedia.org/wiki/Amazon_Simple_Queue_Service Amazon Simple
Queue Service] for exchanging rendezvous messages. "It supports
programmatic sending of messages via web service applications as a way to
communicate over the Internet."
It looks like messages are relayed through URLs like
https://queue.amazonaws.com/
https://sqs.us-east-1.amazonaws.com/
https://sqs.us-east-2.amazonaws.com/
etc.
[https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide
/sqs-making-api-requests.html Here is an example of a SendMessage call]:
!https://sqs.us-
east-2.amazonaws.com/123456789012/MyQueue?Action=SendMessage&MessageBody=Your%20message%20text&Version=2012-11-05&AUTHPARAMS
There's a [https://docs.aws.amazon.com/cli/latest/reference/sqs/index.html
command-line interface].
I'm not sure how you would send a message back to the client, and have it
match up with the message the client sent initially. Maybe a separate
queue per client?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26151>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs