I'm working on a WiFi Keyboard and Mouse interface, using a Cactus Micro v2 board. This has an atmega32u4, which appears to the PC as a keyboard and mouse, as well as an ESP8266 Wifi microcontroller, which connects to your home wifi and exposes a TCP service to accept K/M events. Connect to it using your phone/tablet, send keystrokes/mouse movements to your PC, view the results via an HDMI over Ethernet extender.
Still in progress, but sounds like it might address your problem.
Indeed, my solution would have involved something like a TP-Link WR703N, running OpenWRT, powered from a USB battery pack. (I'm assuming that each of the pumps is some distance from the next, and you don't want to have Ethernet cables running across the forecourt. The battery pack is optional, I guess you may also have power available at each pump). Configure each mini router with an appropriate IP address on the Ethernet port, and then do Source NAT from the Wifi to that IP address when talking to the pump. Configure the WiFi interface to connect to an AP that you set up centrally, that your laptop will also be connected to. This takes care of the issue of simultaneous connectivity to each pump.
As far as software goes, it sounds like a virtual machine for each is a requirement, so that they can run independently of each other. This *might* end up being the trickiest part, depending on how much configurability you have in the application that actually does the firmware updates.
* If you can specify the IP address of the destination pump in the update software, great, simply bridge or NAT each VM onto the Wifi network set up in step 1. Configure each VM to speak to the IP address of each 703N, and perform the update. Done. * If each VM needs to have the corresponding IP to the pump's, things get a little trickier, and you may need to have another layer of NAT to get this to work. I suspect that you would run into issues with the number of private networks that your Virtualisation software supports, in this case.
Am I the only one wondering how they get a CA to sign the certificate? Seems like an interesting opportunity for someone within CloudFlare to get their own SSL certs signed, and MITM to their hearts content.
In this context, something like tor or a socks proxy would also qualify as spoofing ones IP address, and could throw an ICBM on the wrong track. Just saying.
The achievements in the rest of this paper far outweigh the existence of a tablet built on this foundation.
They've created their own 64-bit processor! They've implemented a compiler for it! They've ported FreeBSD to it! That's some seriously impressive stuff!
But the leader has to be the laser cut tablet assembly.:-(
Noone has to intercept anything, or maintain a session. Just TCPdump the lot, and look at it later.
That is, unless they are trying to intercept SSL, which they COULD do, as a CA cert controlled by a Chinese company has been added to most browsers already.
In other words, this design is powered with a power source that isn't even available until the iPhone/iPod is booted up.
I guess you could fix that with an appropriate external power supply; a little wall-wart and some appropriate voltage regulation.
A USB-serial adapter like the CA-42 (powered from the PC on the other end) would be perfect for that purpose. Check out all the OpenWRT or similar "serial console" articles.
It would be interesting to try listen on this serial port to see if the device emits any messages while booting up. Some trial and error on the baud rate may be required, of course.
Dominic chose to start his efforts to remove the evercookie with Safari. Others have tried with Chrome and FF, etc. No browser is immune, although those that do not support HTML5, or flash are a lot better off.
I recently bought an HP 6730b laptop on auction. I took it out of the container, and turned it on (without attaching the power supply). It's pretty snappy, and seems to be in good nick.
Perfect for my mother, I thought.
I plugged the charger in, and started installing Ubuntu. Good God! It's taking an AGE to even go through the POST, never mind running the OS. Shit! And the auction specified no returns if the OS has been changed! Now what?
Xorg is taking 80% of the CPU, just moving the mouse around. WTF!?
Long story short, it turns out it is the aftermarket power brick that is to blame. Unplug it, run it on battery, works like a dream. Plug it in, and it all goes to shit.
Check the voltage on the brick - all according to spec.
Looks like it is time to get a genuine brick for my mom.
My only thought is that the laptop is spending more time cycling between power saving (C3?) states that it actually does executing the instructions it has been given. Can anyone explain this behaviour better?
I have bought a Buffalo WZR-HP-G300NH, and couldn't be happier with it.
4 GbE ports (plus one GbE downstream to an ADSL modem in bridged mode), 32MB flash, 64MB RAM, 1 USB port. Supported by OpenWRT.
While ideally I'd also prefer an integrated ADSL + all of the above, the reality is that they are few and far between (meaning: I couldn't find one!) The advantage of the separated configuration is that should the ADSL modem be fried (e.g. by lightning), with any luck, the more expensive router might survive.
One thing that a lot of people are ignoring is that Thawte FreeMail certs are used by a lot of small developers to publish Java apps, and this would kill off that ability quite quickly.
That said, I have not seen a word of this on the Thawte web site, which makes me wonder if the submitter is trying to perform a DoS on Thawte for some reason, and are tricking the slashdotters into being that DoS. The page linked takes an enormous amount of time to decide that there is nothing to return, meanwhile slashdotters are beating on the server over and over. Sorry for the OP, though. The rest of their site still seems to be just fine.
I did some work for a local bank, and their ATM's were running Windows XP (not embedded), IIS (can't remember the version), and IE. This was to allow them to serve "rich content" (movies, images, animations, etc), without having to write it all themselves. The ATM just had IE talking to IIS, and displaying the results in "kiosk mode". The buttons on the sides of the screen were mapped to keys on the keyboard (I think), and that's how it ran.
I specified a full set of ports that needed to be accessible to the ATM controllers, and that was all that was supposed to be accessible from the network.
However, if you can get access to the back of the machine, it has a second monitor, keyboard and mouse, and you can access the OS, and do whatever you want to do. I *THINK* that the keyboard and mouse were locked away in the vault (or at least behind a door), but the hardware itself is pretty standard PC, so I don't imagine that it would be particularly difficult to add a USB keyboard or mouse and gain access when rebooting the device. Maybe even boot from a USB disk or similar.
The reality is that if you have physical access to practically anything, it is game over.
Personally, I would have been a lot happier to see a stripped down Linux kernel + minimal OS, BIOS passwords, bootloader passwords, etc than the entire Windows stack. Less to verify == more security.
Yes, the example cited is "RESOLVED INVALID", because the bug reporter thought there was a problem in FF, which really turned out to be a real live MITM attack, which is exactly what the link was provided as.
Re:Silly to create the organization
on
Houses With Tails
·
· Score: 1
The one difference (at least, as I understand it), is that Comcast owns the tail. In this case, the homeowner/HOA owns the tail, and can tell whomever is operating the tail to get lost if they don't match up to expectations.
1. A firewall is not the be-all and end-all of security. But it certainly is a good starting point. You are making the assumption that the majority of people deploy systems with secure configurations. History has shown is that they do not. 2. Ok, if they *do* have a firewall, then the implication is that the firewall admins are incompetent. Better? I find it difficult to believe that that many databases *need* to be exposed to the random Internet. 3. Open port != DB Server, agreed. But if you connect to the port using the DB protocol, and get a response indicating the version of the DB in question, the odds are good that it *is* a DB. Read the article. He checks to see which versions they are, too. 4. Fair enough. Not too many install Oracle, though. 5. As you say in 6, some people just need to get their shit together.
1. You enter your username and password 2. The phisher uses a botnet[1] to fetch the picture from the real bank site 3. You verify the picture 4. You enter the answers to your personal questions 5 The phisher gains access to your account.
Game over. Thanks for playing.
[1] Use of a botnet prevents the bank from spotting lots of requests from a single location.
You have typed in your password, and the phisher already has it . ..
Anyway, how difficult is it for the phisher to fetch the picture from the eral site, and show it to you . ..
I still reckon the NetCraft toolbar (or similar) is one of the best solutions available. Show the history of the site, for the user to check.
Now, I've heard that it is trivial to fake by framing the untrusted site, but that is an implementation detail, which can be fixed. The concept is still good.
In fact, I think they registered com.net, and simply created a wildcard DNS result for anything under that, which points to their search page.
As the parent says, it is common behaviour for browsers to try appending common TLD's to the end of an URL that is not found verbatim. When Google went away, the browser appended.net to google.com, and ended up at *.com.net.
A bug that people seem to be ignoring is that whatever browser is shown in the screenshot did not show the correct URL after the.net was appended, but left the original URL in the location bar.
Slashdot Mirror
I'm working on a WiFi Keyboard and Mouse interface, using a Cactus Micro v2 board. This has an atmega32u4, which appears to the PC as a keyboard and mouse, as well as an ESP8266 Wifi microcontroller, which connects to your home wifi and exposes a TCP service to accept K/M events. Connect to it using your phone/tablet, send keystrokes/mouse movements to your PC, view the results via an HDMI over Ethernet extender.
Still in progress, but sounds like it might address your problem.
Indeed, my solution would have involved something like a TP-Link WR703N, running OpenWRT, powered from a USB battery pack. (I'm assuming that each of the pumps is some distance from the next, and you don't want to have Ethernet cables running across the forecourt. The battery pack is optional, I guess you may also have power available at each pump). Configure each mini router with an appropriate IP address on the Ethernet port, and then do Source NAT from the Wifi to that IP address when talking to the pump. Configure the WiFi interface to connect to an AP that you set up centrally, that your laptop will also be connected to. This takes care of the issue of simultaneous connectivity to each pump.
As far as software goes, it sounds like a virtual machine for each is a requirement, so that they can run independently of each other. This *might* end up being the trickiest part, depending on how much configurability you have in the application that actually does the firmware updates.
* If you can specify the IP address of the destination pump in the update software, great, simply bridge or NAT each VM onto the Wifi network set up in step 1. Configure each VM to speak to the IP address of each 703N, and perform the update. Done.
* If each VM needs to have the corresponding IP to the pump's, things get a little trickier, and you may need to have another layer of NAT to get this to work. I suspect that you would run into issues with the number of private networks that your Virtualisation software supports, in this case.
Am I the only one wondering how they get a CA to sign the certificate? Seems like an interesting opportunity for someone within CloudFlare to get their own SSL certs signed, and MITM to their hearts content.
In this context, something like tor or a socks proxy would also qualify as spoofing ones IP address, and could throw an ICBM on the wrong track. Just saying.
Not strictly true. You can do it easily if you are on the path normally taken to get to the spoofed IP. For example, see Linux TProxy.
The main constraint preventing it in the general case is the difficulty of guessing the sequence numbers.
Ah, that would be 0.99p13, I know there was a gap there somewhere.
0.99p30, IIRC
Breathless excitement!
The achievements in the rest of this paper far outweigh the existence of a tablet built on this foundation.
They've created their own 64-bit processor! They've implemented a compiler for it! They've ported FreeBSD to it! That's some seriously impressive stuff!
But the leader has to be the laser cut tablet assembly. :-(
Noone has to intercept anything, or maintain a session. Just TCPdump the lot, and look at it later.
That is, unless they are trying to intercept SSL, which they COULD do, as a CA cert controlled by a Chinese company has been added to most browsers already.
Alas, this hack won't do it:
In other words, this design is powered with a power source that isn't even available until the iPhone/iPod is booted up.
I guess you could fix that with an appropriate external power supply; a little wall-wart and some appropriate voltage regulation.
A USB-serial adapter like the CA-42 (powered from the PC on the other end) would be perfect for that purpose. Check out all the OpenWRT or similar "serial console" articles.
Amongst other things, I suppose.
It would be interesting to try listen on this serial port to see if the device emits any messages while booting up. Some trial and error on the baud rate may be required, of course.
Dominic chose to start his efforts to remove the evercookie with Safari. Others have tried with Chrome and FF, etc. No browser is immune, although those that do not support HTML5, or flash are a lot better off.
I recently bought an HP 6730b laptop on auction. I took it out of the container, and turned it on (without attaching the power supply). It's pretty snappy, and seems to be in good nick.
Perfect for my mother, I thought.
I plugged the charger in, and started installing Ubuntu. Good God! It's taking an AGE to even go through the POST, never mind running the OS. Shit! And the auction specified no returns if the OS has been changed! Now what?
Xorg is taking 80% of the CPU, just moving the mouse around. WTF!?
Long story short, it turns out it is the aftermarket power brick that is to blame. Unplug it, run it on battery, works like a dream. Plug it in, and it all goes to shit.
Check the voltage on the brick - all according to spec.
Looks like it is time to get a genuine brick for my mom.
My only thought is that the laptop is spending more time cycling between power saving (C3?) states that it actually does executing the instructions it has been given. Can anyone explain this behaviour better?
I have bought a Buffalo WZR-HP-G300NH, and couldn't be happier with it.
4 GbE ports (plus one GbE downstream to an ADSL modem in bridged mode), 32MB flash, 64MB RAM, 1 USB port. Supported by OpenWRT.
While ideally I'd also prefer an integrated ADSL + all of the above, the reality is that they are few and far between (meaning: I couldn't find one!) The advantage of the separated configuration is that should the ADSL modem be fried (e.g. by lightning), with any luck, the more expensive router might survive.
One thing that a lot of people are ignoring is that Thawte FreeMail certs are used by a lot of small developers to publish Java apps, and this would kill off that ability quite quickly.
That said, I have not seen a word of this on the Thawte web site, which makes me wonder if the submitter is trying to perform a DoS on Thawte for some reason, and are tricking the slashdotters into being that DoS. The page linked takes an enormous amount of time to decide that there is nothing to return, meanwhile slashdotters are beating on the server over and over. Sorry for the OP, though. The rest of their site still seems to be just fine.
Care to elaborate a little?
What do you consider a "proper OS"?
I did some work for a local bank, and their ATM's were running Windows XP (not embedded), IIS (can't remember the version), and IE. This was to allow them to serve "rich content" (movies, images, animations, etc), without having to write it all themselves. The ATM just had IE talking to IIS, and displaying the results in "kiosk mode". The buttons on the sides of the screen were mapped to keys on the keyboard (I think), and that's how it ran.
I specified a full set of ports that needed to be accessible to the ATM controllers, and that was all that was supposed to be accessible from the network.
However, if you can get access to the back of the machine, it has a second monitor, keyboard and mouse, and you can access the OS, and do whatever you want to do. I *THINK* that the keyboard and mouse were locked away in the vault (or at least behind a door), but the hardware itself is pretty standard PC, so I don't imagine that it would be particularly difficult to add a USB keyboard or mouse and gain access when rebooting the device. Maybe even boot from a USB disk or similar.
The reality is that if you have physical access to practically anything, it is game over.
Personally, I would have been a lot happier to see a stripped down Linux kernel + minimal OS, BIOS passwords, bootloader passwords, etc than the entire Windows stack. Less to verify == more security.
Yes, the example cited is "RESOLVED INVALID", because the bug reporter thought there was a problem in FF, which really turned out to be a real live MITM attack, which is exactly what the link was provided as.
The one difference (at least, as I understand it), is that Comcast owns the tail. In this case, the homeowner/HOA owns the tail, and can tell whomever is operating the tail to get lost if they don't match up to expectations.
And which version of Windows would you run on that processor, then? Oh, right!
1. A firewall is not the be-all and end-all of security. But it certainly is a good starting point. You are making the assumption that the majority of people deploy systems with secure configurations. History has shown is that they do not.
2. Ok, if they *do* have a firewall, then the implication is that the firewall admins are incompetent. Better? I find it difficult to believe that that many databases *need* to be exposed to the random Internet.
3. Open port != DB Server, agreed. But if you connect to the port using the DB protocol, and get a response indicating the version of the DB in question, the odds are good that it *is* a DB. Read the article. He checks to see which versions they are, too.
4. Fair enough. Not too many install Oracle, though.
5. As you say in 6, some people just need to get their shit together.
No, duh?!
That's the exact same link that the original poster provided.
Yes, an article from September is hardly "news".
Move along, nothing to see here.
Nice in theory.
But the phisher probably works as such:
1. You enter your username and password
2. The phisher uses a botnet[1] to fetch the picture from the real bank site
3. You verify the picture
4. You enter the answers to your personal questions
5 The phisher gains access to your account.
Game over. Thanks for playing.
[1] Use of a botnet prevents the bank from spotting lots of requests from a single location.
But at this point, it is TOO LATE!!
.
.
You have typed in your password, and the phisher already has it . .
Anyway, how difficult is it for the phisher to fetch the picture from the eral site, and show it to you . .
I still reckon the NetCraft toolbar (or similar) is one of the best solutions available. Show the history of the site, for the user to check.
Now, I've heard that it is trivial to fake by framing the untrusted site, but that is an implementation detail, which can be fixed. The concept is still good.
In fact, I think they registered com.net, and simply created a wildcard DNS result for anything under that, which points to their search page.
.net to google.com, and ended up at *.com.net.
.net was appended, but left the original URL in the location bar.
As the parent says, it is common behaviour for browsers to try appending common TLD's to the end of an URL that is not found verbatim. When Google went away, the browser appended
A bug that people seem to be ignoring is that whatever browser is shown in the screenshot did not show the correct URL after the