Can we access the secured coap url through copper plugin in Firefox? - coap

I am just wondering if we can access the DTLS enabled COAP urls through the copper plugin.
I am able to access
coap:\localhost:5683
How can we access
coaps:\localhost:5683
after enabling DTLS, through copper plugin in the Firefox browser?

I've found nothing regarding DTLS in the Copper code
https://github.com/mkovatsc/Copper
So unfortunately the answer is - we can not.

Related

Why does Youtube use Insecure RTMP, considering that Facebook uses secure RTMPS?

RTMP being an insecure unencrypted protocol, suffers from attacks like MITM and network sniffing. Naturally so, FB uses RTMPS: https://ppc.land/streaming-facebook-moves-live-videos-completely-to-rtmps/
Why is Google lackluster about adopting this secure approach? Is it due to less compatibility for the RTMPS protocol with streaming software and providers?
Azure does not provide RTMPS, at least their official developer doc does not mention that.
RTMPS was never an official standard. Adobe has a custom encryption called RTMPE, but that was never really supported outside Adobe software.
Because RTMPS is not official most high end video equipment and a lot of server software does not support it.

Browser's mDNS strategies for WebRTC

I can use mDNS feature by WebRTC by enabling -enable-webrtc-hide-local-ips-with-mdns flag at Google Chrome. But after a long investigation, I could not find a clear way for mDNS usage by WebRTC at other browsers such as Firefox or Edge.
Is there such a way to use mDNS while using WebRTC apps on browsers?
Thanks
Firefox is currently working on adding support for mDNS here https://bugzilla.mozilla.org/show_bug.cgi?id=1544770
For firefox go to configuration about:config and set media.peerconnection.ice.obfuscate_host_addresses to false if this flag is true it will change local ip to uuid

Chrome/firefox extension to read data streaming over USB and network to localhost

I'm looking at the possibility of using a chrome extension or firefox addon that will allow me to read information that is sent over USB in the form of text data? And to the localhost/IP of the machine to certain port?
Can someone point me to the any examples or API documents that will help with my search?
The idea be that the extension is listening for text data on USB or to the localhost of the machine.
Thanks in advance
Additional information:
Can an extension listen to traffic being set over a local IP? on a certain port? Can it be sent to localhost?
Can you listen to data being sent over a USB port?
There is chrome.usb for interacting with USB devices. It is only accessible in Chrome apps however and not extensions.
In Chrome the browser will not provide such access to the system.
The correct way would be to have an external program collecting the data and communicating with the browser add-on. It is achieved through Native Messaging.
Note that you will not be able to bundle the external program with the extension; you'll need to have your own installer.
Edit: I have to comment that #abraham's answer is perhaps more correct. You can have raw USB access in a context of a Packaged App.

Sending an SMS from mobile browser

Is it possible for a mobile browser to send an SMS using the device's built-in capabilities?
By that I mean, NOT using some online SMS services provider but actually making the mobile device send the SMS (same you would do using J2ME).
There are lots of different mobile browsers out there, so I doubt that this is standardised. Safari/iPhone supports SMS URIs, which strikes me as a sensible approach to the problem and one that might be more widely supported than just the iPhone.
Based on the link (above) I found, and a comment from Zamel, I suspect this would work:
SMS
Although with a real phone number, and possibly escaping the + sign as %2B.
Some versions of the Opera Mini browser provide a javascript interface for authoring SMS messages to be sent from the user's phone.
Also, some versions of Nokia's Symbian browser include a javascript interface with similar functionality.
There might be others, but these are the only two I've found documentation for so far.
I think a GSM modem is capable of acting as a SMS Gateway but you have to have the software installed on the modem to do this. You might also look into the Carrier Gateway Emails to SMS as another option. Example is AT&T number#txt.att.net
There are a couple of free services popping up these days like ZeepMobile that you might also want to look into.
What exactly are you trying to accomplish?
No as a mobile browser is specifically built to render markup (html) documents. Therefore, if you wanted to send SMS via a mobile browser it would call a web server page and send from the server NOT the mobile browser.
Mobile OS and their applications have quite a lot of limitations. The closest you will see is the ability to hyperlink a phone # in a mobile browser to send a message but it will be handled via their SMS app not the browser.
Its not possible . You can call device functionality from browser . That is the way to go about it . Webkit lets you do it
Android and blackberry support
"mailto:" and "tel:".
Android supports "sms:" (and maybe iPhone, I don't have one :))
good luck and please post your result.
It's a good thing that is not possible. It would be quite a security risk IMHO. I imagine spammers would be all over it.

How to create sockets in google chrome extension?

I created small hello world extension for google chrome http://code.google.com/chrome/extensions/getstarted.html. I need to use sockets in extension for peer to peer communication using UDP. Is there any firefox Jslib equivalent in google chrome or how we can use other languages in google chrome extension?
I doubt its possible in google chrome, looking at its documentation. ? Are there any other ways to achieve p2p communication in extension?
Chrome has an packaged app support for raw socket connections. More general info here. This used to be available to extensions as well but it's not clear if that's still true.
The documentation indicates that only UDP is available for the type when the socket is created. However, recently (Jan 2012) there was a commit adding TCP support.
These are not websockets (it's TCP or UDP sockets):
http://developer.chrome.com/apps/socket.html
https://developers.google.com/live/shows/7320022-5001
The second link is a howto for making a web-server in a Chrome app.

Resources