Through [WayBack] netcat 1.11 for Win32/Win64 I bumped into [WayBack] Netcat – Wikipedia, the free encyclopedia.
The docs at [WayBack] Netcat: the TCP/IP swiss army made it arrive on my research list.
Time for some scripting with it (:
–jeroen
via:
Archive for the ‘Internet protocol suite’ Category
On my research list is Netcat: the TCP and UDP swiss army knife
Posted by jpluimers on 2016/01/14
Posted in Communications Development, Development, Internet protocol suite, TCP | Leave a Comment »
Computer network technologies and services/VoIP – Wikibooks, open books for an open world
Posted by jpluimers on 2015/12/25
Nice explanation of unicast, multicast, RTP and much more:
Computer network technologies and services/VoIP – Wikibooks, open books for an open world.
–jeroen
Share this:
Posted in Communications Development, Development, Internet protocol suite, TCP | Leave a Comment »
paping – Cross-platform TCP port testing, emulating the functionality of ping (port ping) – Google Project Hosting
Posted by jpluimers on 2015/12/22
Hopefully someone will move this to Github before Google code goes down: paping – Cross-platform TCP port testing, emulating the functionality of ping (port ping) – Google Project Hosting.
Paping (pronounced pah ping) is a computer network administration utility used to test the reachability of a host on an Internet Protocol (TCP/IP) network and to measure the time it takes to connect to a specified port
–jeroen
via:
- linux – Is it possible to ping an address:port? – Super User.
- Paping – Wikipedia, the free encyclopedia.
Share this:
Posted in *nix, *nix-tools, Communications Development, Console (command prompt window), Development, Internet protocol suite, Power User, TCP, Windows | 1 Comment »
network, multicast and send address in TransportNetwork; via Digging into Tibco Rendezvous network details – II
Posted by jpluimers on 2015/10/28
Tibco is very powerful and can do all sorts of casting.
For my memory (formatted for readability; there are more details at OpenPGM Concepts : Transport):
The network parameter consists of up to three parts, separated by semicolons—network, multicast groups, send address—as in these examples:
Example Meaning lan0 network only lan0;225.1.1.1 one multicast group lan0;225.1.1.1,225.1.1.5;225.1.1.6 two multicast groups, send address lan0;;225.1.1.6 no multicast group, send address The format is like this:
partOne;partTwo;partThreeand some bits are optional
partOne[;[partTwo][;[partThree]]]Part one identifies the network, which you can specify in several ways: – Host name, Host IP address, Network name, Network IP number, Interface name, Default TRDP daemons use the network interface which corresponds to the hostname of the system as determined by the C function gethostname(). PGM daemons use the default PGM multicast interface, 224.0.1.78.
Part Two—Multicast Groups – Part two is a list of zero or more multicast groups to join, specified as IP addresses, separated by commas. Each address in part two must denote a valid multicast address. Joining a multicast group enables listeners on the resulting transport to receive data sent to that multicast group.
Part Three—Send Address, Part three is a single send address. When a program sends multicast data on the resulting transport, it is sent to this address. (Point-to-point data is not affected.) If present, this item must be an IP address—not a host name or network name. The send address need not be among the list of multicast groups joined in part two. If you join one or more multicast groups in part two, but do not specify a send address in part three, the send address defaults to the first multicast group listed in part two.
Note: I wasn’t aware that for Tibco Rendezvous the default multi-cast network was 225 (often you see 224 here, as that is the starting multi-cast range in the IANA IPv4 Address Space list)
–jeroen
via:
- >Digging into Tibco Rendezvous network details – II | Feasting Technical Cognition.
- >Digging into Tibco Rendezvous network details – I | Feasting Technical Cognition.
- OpenPgmConceptsTransport – openpgm – OpenPGM Concepts : Transport – An implementation of the PGM reliable multicast protocol. – Google Project Hosting.
Share this:
Posted in Communications Development, Development, Internet protocol suite, Network-and-equipment, Software Development, TCP, TIBCO Rendezvous | Leave a Comment »
NOC Zone and NOC Apps – A Service and Free Mobile App for Website Monitoring
Posted by jpluimers on 2015/10/16
Interesting: this works through an on-line service that monitors up to 2 servers for free (including protocols like HTTP, SMTP and PING).
You can get reports at either through:
- their on-line web page: https://noczone.com
- a Chrome extension: NOC Zone Server Monitoring – Chrome Web Store.
- a mobile app (iOS or Android): NOC Apps – A Free Mobile App for Website Monitoring.
I’m using this to monitor my boxes at home.
A demo video is below.
–jeroen
Share this:
Posted in *nix, Communications Development, Development, HTTP, Internet protocol suite, Power User, SMTP, TCP | Leave a Comment »
Can a Raspberry Pi do NAT port forwarding to a non LAN address? If so, what…
Posted by jpluimers on 2015/09/19
Can a Raspberry Pi do NAT port forwarding to a non LAN address? If so, what distribution would be the easiest one?
Johannes Self added some nice comments for generic Linux distributions in the G+ thread, but just in case my blog readers have even more concrete answers…
–jeroen
Share this:
Posted in *nix, Development, Hardware Development, Internet protocol suite, Power User, Raspberry Pi, TCP | Leave a Comment »
Using httpbin to test http/https requests
Posted by jpluimers on 2015/09/15
StackOverflow user Kenneth Reitz has written a great on-line and free httpbin tool that responds to many kinds of http/https requests including the standaard http request methods (or verbs) used by REST: get, post (for http 1.0) and patch, put, delete (for http 1.1).
These verbs are not supported: head (http 1.0) and trace, options, connect (http 1.1).
The site is geared towards JSON (as most the responses are in JSON, except for one XML response and a few TEXT responses), but even if your environment does not use JSON, it is very useful as you basically get an echo of information on what you pass to it.
Except one endpoint (/encoding/utf8), none of the response encodings can be determined by the request. This is a pity as sometimes it is good to see how a specific encoding works for JSON, but it is very hard to support encodings well, so I can understand the support is not there (or not there yet).
There are many examples on the site, which I won’t list.
There are at least two sites hosting them. The original supports HTTP and HTTPS only, but the ngHttp2 people also support HTTP2 and SPDY:
- httpBin: [WayBack] httpbin.org 0.9.0: A simple HTTP Request & Response Service.
- ngHttp2: [WayBack] httpbin(1): HTTP Client Testing Service
What I do list are the endpoints as copied from the site on 20141228:
Share this:
Posted in .NET, Delphi, Development, HTTP, Internet protocol suite, REST, Software Development, TCP | Leave a Comment »
Hacking Team had more and more need for SSL MITM
Posted by jpluimers on 2015/07/07
Interesting reads:
- https://ht.transparencytoolkit.org/rcs-dev%5cshare/HOME/Naga/httpX/Presentation.pptx
- Hacking Team Breach Shows a Global Spying Firm Run Amok | WIRED.
- “Hacking Team Transparency Report” could sign Windows Kernel Drivers.
–jeroen
Share this:
Posted in Communications Development, Development, https, Internet protocol suite, LifeHacker, Power User, Security, TCP, TLS | Leave a Comment »
Research notes on Diffie Hellman over WebSockets over a MittM http proxy to setup an encapsulated secure channel
Posted by jpluimers on 2015/06/17
Inspired by CloudFlare Keyless SSL, I have this idea of using Diffie Hellman over WebSockets over a MittM based http proxy (which intercepts and decrypts HTTPS traffic) like mitmproxy (but them from a commercial vendor to inspect web traffic) to setup an encapsulated secure channel.
I know SSH uses Diffie Hellman to setup a secure channel over a binary TCP connection.
Binary communication over HTTP usually means WebSocket.
I don’t want WebSSH (which does use WebSockets, but is probably filtered by the MitM proxy anyway).
Maybe either of these open source tools will work:
If these don’t work, I need to do more research.
Since I use C# and .NET for much of my work, I started the WebSocket over HTTP C# query.
c# – How to use proxies with the WebSocket4Net library – Stack Overflow.
–jeroen
Share this:
Posted in *nix, *nix-tools, Communications Development, Development, HTTP, Internet protocol suite, Linux, Power User, SSH, SuSE Linux, TCP, WebSockets, Windows, Windows-Http-Proxy | Leave a Comment »
Time to upgrade: SHAAAAAAAAAAAAA | Check your site for weak SHA-1 certificates.
Posted by jpluimers on 2015/06/01
They days of SHA-1 are quickly coming to an end. Chrome has already marked SHA-1 signed TLS/SSL certificates for having an expiration > 2015-12-31 as insecure for a few weeks now. They promised to sunset SHA-1 about 9 months ago.
So if you haven’t done so, upgrade your HTTPS (and HTTP/2 which defaults to TLS) certificates to SHA-2. A great site of help here is SHAAAAAAAAAAAAA | Check your site for weak SHA-1 certificates. It is open source at GitHub.
You’ve less than 6 months now.
More in dept-reading (especially the comments by Ryan Sleevi): Chrome 42 (next stable) will mark SHA-1 signed certs with a validation date >2015 as insecure!.
–jeroen
PS: if you really need to do the balancing act, you technically can serve old certificates to SHA-2 incompatible clients while serving more secure certificates to modern clients. But it’s a risk, so you might as well tell these old clients they’re out.
Share this:
Posted in https, Power User, Public Key Cryptography, Security, TLS | Leave a Comment »
The Wiert Corner - irregular stream of stuff 