246 karma · joined July 10, 2015
PS: Unfortunately, most Fortune 2000 enterprise (ms and non-ms shops) abuse the fuck out of open source and give zero back (time, $ or help). I really think there should be some "community charge" funding model which doesn't make it nakedly for-profit but rewards people that contribute, maintain and support useful code that is widely deployed so they're not completely abused as unpaid crowdslaves.
Metal is extremely difficult to model because light travels oddly along crystalline and micro-fissure structures.
Also, what data is collected permanently, for how long? What happens if the venture where acquired? Whom would own that?
* I think virustotal could be easily monetized (without altering or cheapening itself) by freemium to orgs, nonprofits, govts that want faster, private, shared/dedicated access to the same "cloud" capabilities. There was HitmanPro which was good early on, but it didn't seem to be stay anywhere near as comprehensive as virustotal.
It becomes more of a "what should this program should consume, do and output and feedback" problem... Bash, Ruby, whatever... but aim for some standards, in general.
Furthermore, with Ruby, as a dynamic language with full network capabilities and add-on packages (gems) with other IPC libraries (zmq), there are other structured, efficient serialized service consumer/producer configurations possible rather than only shell commands. There are also background job processing frameworks like sidekiq and parallel job processors like celluloid, parallel and EventMachine.
The future, really (for dev &| ops tasks) in on-demand loaded, micro-services rather than giant, slow frameworks. The glue (say chef code) and one-ofs will likely still be a bunch of Ruby code and hopefully more Ruby code, respectively, too.
Sample output (tethering):
0 ~ git:master ❯❯❯ internet_access
Bluetooth DUN: Bluetooth-Modem dns 127.0.0.1
Ethernet: en0 macaddr xx:xx:xx:...:xx dns 127.0.0.1
FireWire: fw0 dns 127.0.0.1
Wi-Fi: en1 macaddr xx:xx:xx:...:xx dns 127.0.0.1
iPhone USB: en4 172.20.10.3/24 router 172.20.10.2 macaddr xx:xx:xx:...:xx dns 127.0.0.1
Bluetooth PAN: en3 dns 127.0.0.1
Thunderbolt Bridge: bridge0 dns 127.0.0.1
0 ~ git:master ❯❯❯
Sample output (wifi enable, unassociated, no tethering): 0 ~ git:master ❯❯❯ internet_access
1 ~ git:master ❯❯❯
This is driven by a non-privileged infinite looping event bash scripts which TCP connects to another pair of bash scripts running as root which can actually make the change because they're listening on two localhost tcp ports.(I've tried these other event-based app/script utilities and they're fragile and buggy as heck.)
It seems like something Apple, for one, should take on... deprecate AppleScript and use something more common, accessible and make a common, standardized scripting platform far more comprehensively documented in something like Ruby. AppleScript is just too COBOL/Cucumber "English" and poorly documented to be practical for advanced users. (I've been gradually moving all new scripts over to Ruby because Bash scripts are fragile and not as inherently reusable as standardizing on a dynamic languages (like RedHat w/ Python).)
0. If I had budget authority, I would've ordered something which could grab memory and disk images on a live system and sign-up multiple .edu researchers & symantec security group and equivalent shops under NDA to analyze them.
1. And I would've yanked all those janky (R)ILO (aka RMSA, aka DRAC) cards with their always outdated Linux / Java / PHP "wifi router"-like whatever embedded systems.
2. Finally, I would've spent some cash on honeynet setups and cc: to item 0.
Edit^2: Props to Josh Wieder for taking sounding the sec awareness alarm. I would only do active sec research on untrusted materials within a decent hypervisor's VM on a virtual desktop (VDI) which has "nonpersistence" on all storage, so it's clean on every power cycle.
Also, perhaps wikileaks / virustotal could come to sort of agreement to scan things and flag them while still making assets available to researchers whom still need raw docs, but with large virus warnings which intercept downloads to a warning landing page confirmation if there's no referrer (direct, deep linking).
Finally, the other issue is that not all malware (past, current or future) is known. We ran Windows Servers (NT, 2003) boxes directly on the internet (before I forced them to offer departmental firewalls) and these boxes had already attracted all sorts of multi-vendor unseen malware, rootkits and backdoors long before I got there. After deploying WOLF to a number of boxes, Mark Russinovich was like "yea, you should probably take [the IT sec depts advice]" by just get firewalls and then format all these boxes back to clean image, fully-patched and strong, production-usable, security policy state. Most IT folks don't conduct forensics research... they see strange behavior, try to find a scanner/remover (maybe 80% success), or partially remove it and continue despite unprovable to fully remove all traces... Or they wipe the boxes, start over and guess/pray that the same 'sploit doesn't exist twice. There's just too many unknown variants of existing sploits and too many new sploits to have much faith in antivirus (it's reactive, last line-of-defense security). Antivirus is an opposite Bloom filter... it'll tell you if you're pwned or may not pwned. It's a good to have, just not a complete holistic security posture.
Ruby's turbolinks is a clever hack and mostly works approach to make nav-based (browser history- and crawler SEO-compatible) almost as responsive as SPA... it replaces assets, title, meta and body on-the-fly and updates the url location with javascript to save a whole page update. It's basically a hybrid of client+server coordinated fragment caching. There are some gotchas and workarounds for onLoad() and other JS hooks, but it mostly works pretty well.
On the client side (browser-land), JavaScript (and HTML & CSS) is ubiquitous. The issue of course is that every browser is "especially" different. So it makes no sense to deploy browser extensions unless things need to talk to other local apps. It makes more sense to develop hybrid native apps which are mostly html5 using something like QtWebKit and add your own per-platform goop rather than try to use something like node-webkit, phonegap (cordova) or appcelerator, because, inevitably, system-specific code will be needed, and not having direct access to APIs because of limited proxy/thunk/trampoline code doesn't make for happy developers. Java tried to do the hybrid way using JNI, which could load dll's, dylib's and so's dynamically (I wrote a custom, cross-platform (Linux, Windows), CD-ROM-based app installer using Java + JNI in 1995 by the way, it was trivial.. And then I wrote a Java source to MIPS binary, direct, non-JIT compiler in C++ in 1999.).
Deflection approximated by:
tan( G * mE / (r * c(air)^2) ) / 4345 [m]There's a clear need of AWS-like features for bio/biomedical informatics specifically enabling sharing, security, reuse and anonymization of data (PHI), libraries (like R's bioconductor) and infrastructure (IaaS/PaaS/SaaS).
The issue is that some labs archive still archive their data on actual hard drives (USB and bare drives), making their data much less useful than somewhere readily available and sharable.
I think it's a huge (billion+) opportunity where the right execution would need loads of smart, consultingish customer service reps (huge overhead costs) to help researchers with coding, sysadmining and bio to some degree. Basically, a full-service (with self-service, a-la carte features) hosting company for bio / medical.
This space is only going to grow deeper and wider as more is discovered and confirmed about each gene, protein, pathway and each accompanying expansion in nosology. This sort of research knowledge is vital and unlikely to shrink. The main issues are that it would be a cash-intensive and undefensible business model because it requires paying lots of consultant/scientist brains and anyone can copy the model.