blublob

When it is off: short 8 and 6 for a split second, and it should begin to boot When it is on: short 8 and 6 for a split second, and it should begin the shutdown process (depends, but usually this is the case) When it is on: short 8 and 6 for like 4 second, and you will do a forced shutdown, if you keep it shorted it'll loop: boot -> forced shutdown -> boot -> forced shutdown...

It was complicated enough to get them started with RetroShare ;) Besides they will probably just leave the container mounted after using it, and write down the 50+ passphrase in plain text somewhere...

I need to know if this is even possible. I have gotten family members to use RetroShare to share files with each other, and also to keep multiple copies for backups, but in general our internet-speeds are appalling. This made me think of renting a server with a 10 gbit line, and 2tb of space, and run it as our 'main node'. The issue is just how do I actually completely secure the data. My main idea is to run retroshare via xpra on the server, but I do not want the server company to ever actually be able to access our data, and this made me think of black boxes. Is it possible to create an encrypted 'container' on the server that keeps the files and retroshare inside it, and the only way to access the data is via retroshare, or manually input the encryption keys? example: server (ubuntu) -> encrypted container (retroshare, data files) -> internet What I have out so far involves using luks and setting up an encrypted block device, but the drawback is the encryption keys are stored in memory while the server is online, so anyone could potentially access the files while the server was running. I want it like a black box that exists on the server, and the only communication in and out of it goes via retroshare, and to be able to read what is inside it requires an input of the encryption key.

So, I was fiddling with a satnav I have for my boat, and became interested in how the map data was accessed. On very old satnavs we used to have floppy disks that had the map info on them, and for a new area we had to put in a new disk. I had made backups of those to have at home, incase well, someone messed around with them intoxicated and it flew over board (yes, that actually happened one time we used the boat as transport to an island festival, there 'might' have been beer involved..) [According to our laws this is perfectly legal, and I believe it also recently became legal in the UK.] After a bit of searching I figured out it is a 2gb Samsung microSD card that contains the map data. Fine let us try dd it. Nope, this card is 'empty' he tells me, while infact it is full/identical to the original when I check on the pc. So I came to think that it might be something in the Protected Area that prevents the satnav from reading the microSD I created (it was also a 2gb samsung one). Does anyone here maybe know if this is the case, and if so, is there a way for me to read this Protected Area? (Maybe with an atmel microprocessor and an sd adapter, if the normal pc ones does not support it.) Possible to write to such an area?

That is why I am wondering how to create it, and if the parasitic elements even helps me when I am on a specific frequence. There is also how to calculate the spacings, and the parasitic elements if I would want to cover more than a given frequence. Then there is this form of reflector, it just puzzles me how to do it. Using this on the numbers in the video gives me this: 36 - 2020 MHz 34 - 2140 MHz 33 - 2205 MHz 32 - 2270 MHz 31 - 2350 MHz 30 - 2425 MHz 34 - 2140 MHz 31.5 - 2310 MHz 30 - 2425 MHz 29 - 2510 MHz 28 - 2600 MHz 27 - 2690 MHz Now you know wifi is: 2412 - 30.2 mm 2417 - 30.1 mm 2422 - 30.0 mm 2427 - 30.0 mm 2432 - 29.9 mm 2437 - 29.9 mm 2442 - 29.8 mm 2447 - 29.7 mm 2452 - 29.7 mm 2457 - 29.6 mm 2462 - 29.5 mm 2467 - 29.5 mm 2472 - 29.4 mm 2484 - 29.3 mm He mention that 31.5 mm would be in the middle of the spectrum, but the calculator gives 2310 MHz, that can't be right. What is up with that?

I have to say that is a wonderful webpage. However it brings a few questions to light. If I take base on the yt-video I see that instead of a reflektor there is a slightly larger element behind the driving element. How are the measurements on that calculated, and is it important as long as it is just larger? There is also the thing with parasitic elements. How do they help? How are they sized? How is the spacing between them calculated?

With the uproar of IoT I am using the TI C1110 transceiver for 315mhz, 433mhz and 868-915mhz, but I am lacking a proper antenna. I tried a cheap Yagi from aliexpress, but it was, to put it mildly, garbage. After going through different forums and the web I did find these two: https://web.archive.org/web/20071023032712/http://diy.wifi-live.pl/node/8 This is something I can easily pull off I believe, but there is a problem. I can not find any theory to help me do the proper calculations needed to create a biquad yagi for a given frequency I am using. ie. I test stuff on 433mhz, 868mhz and 869.5mhz atm. (I am using an SMA connection for external antenna.)

I have not had time to look into this much since last time, but I have now tried some more. These two sites did provide some information: http://netfilter-devel.vger.kernel.narkive.com/mzw6VT2E/patch-net-2-6-25-add-packet-filtering-based-on-process-ssecurity-context http://tomoyo.sourceforge.jp/1.7/tutorial-7.html.en But they do seem to talk about a different version. However I was able to stop access to an ip. In Domain Policy Editor I can go into /usr/bin/x-www-browser and add network inet stream connect 23.32.84.110 80 Now I can access that site over port 80 with iceweasel, but if I remove it, I can no longer access it. The webpages speak about allow_network TCP accept/bind/listen <ip> <port number> This is however for 1.7, and I am on 2.5 I believe since my kernel is 3.2.0.4. The problem is that I would also like the option to block certain ip/ports, not just allow them.

Hello all, this will be long; two parts, but don't be afraid, I will make it easy for you. Part One is backstory (you can skip this entirely), part two is current problem, and I will even include a TL;DR in the end. --------Part One-------- Help me get away from big data? I have been wanting to setup my desktop with linux for quite some time now, and have began working with it inside VirtualBox so I am sure I can get all the settings, and programs working that I will use, before I install it natively. However when I came across this article Choosing a Linux Music Player I hit a massive roadbump. So now my search began for something similar to Little Snitch for Linux.The problem is that every forum post I manage to find, that even mention application based firewall for linux, are littered with besserwissers who speak about how linux need no such thing as it is not windows, and therefore is no target of malware and trojans and the likes. Others speak of how you should trust the programs in the offical repos, and need no option to block any outgoing traffic. Basically every such topic derails massively without any real solutions given, other than 'if linux had a need for this, someone would have made it allready!'. Now I will try my luck with you guys. Is there currently a way for me to block unknown outgoing traffic as it first happens on an application level? If it is retroactive it might be too late, as it might have gotten info to change contact server, and me blocking the ip it used last time is of no use. Maybe block all traffic not approved, and log any that attempts, so I can give it access before next time it tries. (Keep in mind that some programs might have tcp traffic on port 80 that I want, but traffic on port 443 and 80 to a different ip that I have no interest in granting them. Others might use p2p, like skype, so they will not have static ip's they contact.) --------Part Two-------- It took some more searching, but I found out that a LSM could do this for me. So I turned on TOMOYO. After reading these two pages I was able to turn it from blacklist to whitelist, and block network on a per application basis. https://forum.manjaro.org/index.php?topic=6408.0 http://tomoyo.sourceforge.jp/2.5/chapter-9.html.en Now my problem is how to whitelist, or blacklist a given ip over a given port for a certain program. In this page it lists: That means it should be possible, right?As an example, how and where would I edit to allow firefox access to the web, except 23.32.84.110 tcp port 80 ? And how would I do it if I wanted firefox to only be able to access 23.32.84.110 tcp port 80 ? --------TL;DR-------- Using TOMOYO Linux I would like to know where and how I need to edit something to block a program from doing outgoing calls to a given ip over a given port and protocol.