<p dir="ltr">Netcat isn't really a security risk. It's just convienent. Most of what it does can be done with creative scripting and bash.</p>
<div class="gmail_quote">On Jan 10, 2014 11:55 PM, "Alex Carver" <<a href="mailto:agcarver%2Bale@acarver.net">agcarver+ale@acarver.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 1/10/2014 16:50, Pete Hardie wrote:<br>
> XMPP is a fairly widespread protocol, and libraries exist for the<br>
> sending end to hook into for most languages<br>
<br>
Most languages but if it's able to be used by bash then I'll consider<br>
it. Not every transmitter is going to be a fully compiled program. I<br>
really do want to occasionally set up a simple bash script that fires<br>
off a preformatted text file at the destination receiver. I have<br>
already tested that with Growl, simple text file with the GNTP headers<br>
as per the protocol spec, transmit with netcat and notifications pop up<br>
on the receivers. No libraries needed.<br>
<br>
<br>
><br>
> On Fri, Jan 10, 2014 at 7:02 PM, JD <<a href="mailto:jdp@algoloma.com">jdp@algoloma.com</a>> wrote:<br>
>> On 01/10/2014 06:16 PM, Alex Carver wrote:<br>
>>> I was looking into notification methods that I could use for one of my<br>
>>> projects to send quick messages to multiple machines (pretty much every<br>
>>> desktop or mobile platform currently in use) on my local network. I see<br>
>>> Growl seems to be available for nearly every platform and seems to be a<br>
>>> fairly simple protocol. I just wanted to solicit opinions on this kind<br>
>>> of notification method. The originating computer is going to be one of<br>
>>> the Linux machines and I've been experimenting with sending by bash<br>
>>> script which is nice, simple, and requires no libraries, just netcat. I<br>
>>> might later write up a small transmitter in C but I think bash will<br>
>>> probably work well for now.<br>
>><br>
>> Netcat is a HUGE!!!!!!! security risk. I wouldn't ever use it beyond POC and<br>
>> only on an air-gapped lab network.<br>
>><br>
>> What sort of notifications? Desktops, system to system, system to specific<br>
>> client? system to any normal web-client?<br>
>> Any chance this will every be wanted over the internet in the future?<br>
>><br>
>> And ... isn't growl commercial? What is the fallback if it isn't available?<br>
>> What about non-GUI client machines?<br>
>><br>
>> Is polling an option? If so, you could setup a REST web interface on a central<br>
>> box that clients can push and pull from. REST means it is trivial to make a<br>
>> client via a bash+curl script.<br>
>><br>
>> XMMP? More effort to use (only slightly), but extremely flexible.<br>
>><br>
>> Or place the messages into a file that every client has read access from. KISS<br>
>> does work after all.<br>
>><br>
>> What are the authentication needs?<br>
>><br>
>> What are the encryption needs? Anything sensitive involved .. even in the future?<br>
>><br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
><br>
><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>