Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Can videocalls and textchats be end-to-end encrypted in ConnectyCube?
I could not find any indication on that on the website.
For example in Twilio, there is the following description:
end-to-end encryption: All media is routed Peer-to-Peer or via Twilio’s Global TURN infrastructure and secured using DTLS/SRTP. Twilio can never decrypt the media shared in a Peer-to-Peer Room.
End-to-end encryption for video calling
ConnectyCube uses WebRTC which provides secure video calls out of the box via DTLS/SRTP which is mandatory in WebRTC.
Encryption is a mandatory feature of WebRTC and is enforced on all components - all media streams sent over WebRTC are securely encrypted, enacted through standardised and well-known encryption protocols.
So the same what is applied to Twilio can be applied to ConnectyCube.
There are lots of very useful information about WebRTC security is available at http://webrtc-security.github.io document
End-to-end encryption for messaging
ConnectyCube provides pluggable system so any end-to-end encryption libraries and solutions can be integrated on top of the ConnectyCube messaging system, for example:
OTR
OMEMO that adapts Signal Protocol to the XMPP world.
OLM
Here is a guide how to use OTR on top of ConnectyCube https://developers.connectycube.com/guides/end-to-end-encryption-otr
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 13 hours ago.
Improve this question
I am confused as to what the statelessness of HTTP means in terms of the client.
I get that stateless-ness means the server does not store any state information about the client but does the client still remember the identities of the servers it has interacted with, assuming cookies are not used?
The “remembering” logic you are talking about would have to be added to either the server, or the client, or both. HTTP is just a protocol, not an implementation, and that protocol is stateless because it doesn’t define any remembering logic as part of its specification
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 months ago.
Improve this question
I have an embedded system (Netburner 5441x) that consumes public-private RSA keypairs. I have ported OpenSSL into the system but the processor cannot make keypairs fast enough for the application. So the next logical step is to have the embedded system, which has Ethernet, get keys from a PC based server.
I've read about half the PKCS#N documents and it looks like it's all about object formats. Is there an accepted network protocol for transferring public-private keypairs? Would you just open a secure socket and send the PKCS objects with no other framing? Use a shared Key Encryption Key, or have the client send a public RSA key for key encryption by the server?
Is there a standard?
Edit 13Jun22 in response to StackOverflow blocking the question: This question is not asking for recommendation of a book etc., but whether a standard exists for a particular unusual use case. If such a standard existed, that citation would answer the question. Respectfully request removal of the block.
According to the Information Security Stack Exchange, there is no accepted answer for this unusual use case. The best practice seems to be setting up a web service that serves passphrase encoded key files over HTTPS, which implies SSL protection.
https://security.stackexchange.com/questions/262533/what-is-the-right-way-to-transfer-public-private-keypairs-over-intranet
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Suppose my Skype integration wants to filter notifications for a user to messages that contain the string "server down". Is this possible?
Per default Skype for Business (=SfB) can only block URL or attachments as written here. Maybe there exist an 3rd party application which can do that, but I do not think so. Reason: The problem here is that SfB can perform peer2peer connections (see more here). That means if you and your workmade are in the same network and no firewall restricts you both and you both perform a chat together, the chat is done between both of you (without a real server connection; for more infos see the official documentation inside the 2nd link). So a 3rd party software (which might sitting on the server) will not capture that kind of information. So what you might need is a client software on every PC. But what about the mobile clients then? So I do not think that such a software exists or would be possible to build.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I know my question is broad, but I have no clue where to start my research.
How can one implement VoIP on a server? I am fairly certain it does not use the http/https protocol. If so, what standard/famous protocols one can use? are there any open-source ones? What are good references to start working on that?
Start by looking at the SIP,RTP and RTCP protocols. I believe they form a minimalistic set of required protocols for VoiP
Some relevant open source projects:
http://www.fsf.org/campaigns/priority-projects/priority-projects/highpriorityprojects#Replaceskype
"There are a number of such programs, such as Ekiga, Twinkle, Coccinella, QuteCom, and Jitsi. Unfortunately, these programs only replace some of Skype's functionality, and only in some situations. WebRTC has a mission to enable rich, high quality, Real-Time Communications (RTC) applications to be developed in the browser via simple Javascript APIs and HTML5. Developers should consider helping free software VoIP and video, chat, and multimedia communications projects."
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Correct me if i am wrong with my understanding:
BitTorrent is a protocol used for P2P sharing and it is used by torrent client. BitTorrent protocol have ability to download the files in chunks. Once all the chunks are downloaded the torrent client application will merge them in a single file.
Is there any encryption method is used while transmission of data by BitTorrent protocol or torrent application?
I have seen BitTorrent was earlier open source but after release version 6 it is no more open source. It is about protocol or BitTorrent Client?
Please clear my doubt.
Thanks.
All modern BitTorrent clients support protocol encryption. You can find the specification here.