Opened 7 months ago

Last modified 7 months ago

#26151 new project

Snowflake rendezvous using Amazon SQS

Reported by: dcf Owned by:
Priority: Medium Milestone:
Component: Obfuscation/Snowflake Version:
Severity: Normal Keywords:
Cc: n8fr8, dcf, arlolra Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Nathan Freitas suggests using 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.

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 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?

Child Tickets

Change History (1)

comment:1 Changed 7 months ago by n8fr8

I guess I need to understand the interactive nature of a Snowflake rendezvous better... My basic thought was that this could be used for a variety of "bridge" type publishing capabilities. If you can provide a bridge on a public IP, you can broadcast it here. This is meant for the ephemeral, temporary type bridges that might be made available from mobile devices or home appliances, while people are not using them.

Note: See TracTickets for help on using tickets.