Re: Not really useful
Then check the link in my first post above ;)
1046 publicly visible posts • joined 23 Dec 2009
I think he was listing brands with security issues, couldn't find an article on a QNAP security cockup (other than OpenSSL which everyone suffered).
Not that they will be without issues, and I bet they will be doing even more audits and tests in the light of current news...
Over here most shops just have a payment terminal that is connected to the PoS via serial or network, and the software just tells the terminal what amount the customer has to pay.
No way for crooks to steal any data, the worst they could do is send it incorrect amounts. Money always goes from customer to shop bank account.
I surely wasn't...
Some 20 years ago, when the digital age was still in front of us, I did contract work on the network and computer equipment at a very large picture print company (for the young ones: a company that develops your negatives and prints them).
Their staff had lots of picture books with nude pics in them: All pictures passed by quality assurance people who marked badly developed pics, to be redone, and if it contained nude, it was marked as well, and the discarded pic was then recovered from the bin.
There will always be people with access to this stuff that will not mind taking a private copy. The only solution is not to give them access.
Call me paranoid, but I never let any wireless device near my babies when they were young. Even the monitor was in the opposite corner of the room.
So kudos for sticking a transmitter in their mouth at that young age. I'd not take the risk, whatever low power they claim to use.
it's not because the frequency response of the ear isn't flat, that the reproduction of sound shouldn't.
In ideal circumstances, you'd want both the microphones and speakers to have a flat frequency response so that the original sound reaches your ears the way it was. Your ears will do the non-flat bit anyway.
I don't see where the body of your post supports its title.
IMHO forking should be the last solution, the FOSS community is littered with forked and parallel produced code. In many cases they end up all having some kind of issue, and picking an implementation is choosing a tradeoff.
If possible, people should try to contribute to the existing project, and that's where the problem with OpenSSL lies: many users but not many contributors. Theo can have a big mouth and fork it, but that only shows nobody really cared or contributed, because the fork was because of the code, not the community.
There are cases where forking is good, because it is a nice defense mechanism to guarantee continuation of the code. Like the OpenOffice -> LibreOffice fork.
- they are way too expensive for what they are and do
- more intelligence is needed, there's already a model that detects its perimeter with a sensor and not a wire though.
- same basic problem as robo vacuum cleaners: can't deal with stuff lying around
Solve these and then we can talk ;)
I've been experimenting a bit with simple things, and found it easiest (at least for peace of mind) to have some kind of hub (my NAS in this case), and write a bit of interface code to interact with them. Much easier to secure and no need to worry about gaping security holes that will never get fixed.
And remember, once a hacker is inside one of these things, he can use it as relay to attack the rest of your network from the inside.
Not when you go destroying some VERY nice parts of nature to do so.
Same goes for the idiots who are planning the hydroelectric projects in Iceland. All nice on paper with their zero emissions, until you visit the place where they will build this and see what rare piece of nature has to go for this.
I normally don't agree very much with Greenpeace, but in this case, I fully understand them. This one's for nature!
The way 'fragmentation' is stressed in an article shows the bias of the writer.
The truth is that the story is much more nuanced: many, if not most apps will run on an older Android version, and if an app doesn't, half the time it's because the developer used a higher API version than was needed. The number of apps that actually need the latest features are much lower.
What the figures DO say, is the sorry state of affairs when it comes to upgrades. How hard can it be to separate HAL from OS, so that OS upgrades are 'easy' on mobile devices?