Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Encoding your WiFi access point password into a QR code

feeding.cloud.geek.nz

Post reply on HN
Print view View original

161–170 of 234 posts

Re: Encoding your WiFi access point password into a QR code

#161

Post by mFixman »

kachnuv_ocasek wrote: post #73
jopsen wrote: post #39

I painted my wifi password as a QR code on 40x40cm canvas.. Painted as in with a brush and paint, it was a bit of work, but now it's both pragmatic and pretty :)

Did something similar for my roommates recently. We have no printer in our flat, so I grabbed a piece of graph paper, redrew the QR code and taped it onto the fridge. Now our guests can simply scan the picture instead of strenuously rewriting the complicated password.

What's the problem with using a long but humanly readable password, like several concatenated words? It's not like you are trying to protect against large scale attacks.

Re: Encoding your WiFi access point password into a QR code

#162

Post by debt »

sirsuki wrote: post #107

I do this in our house and it works great. I discovered one flaw though. When I say scan the QRCode I am immediately told “i don’t knows how” Or asked “the what?” Or disapproved of with “I hate those things.” Fun fact no one has ever actually scanned the code... ever! Maybe if I was a cafe but not for house guests.

Okay so you don’t live in China then I take it

Re: Encoding your WiFi access point password into a QR code

#164

Post by jlgaddis »

michaelt wrote: post #123
BiteCode_dev wrote: post #53

Earlier quoted context omitted.

7kb for a supermarket bill is plenty, and you can have several of them. Forms and legal documents should all have an immutable official url and uuid anyway to point to their legal and administrative context.

The largest QR code in the standard, "version 40" - can only store 3 kilobytes at the lowest level of error correction and 1.2 kilobytes at the highest level [1]. And that's a pretty huge QR code [2] My back-of-the-envelope calculations say you'd need 61 bits per line on a receipt just to encode UPC, quantity and price. So the largest QR code would only allow 19-50 lines. And that's without including data like the st…

Seems like the obvious thing would be to have the QR code contain a "receipt ID" (UUID?) in a URL.

When the QR code is scanned, the browser opens to the URL, the remote side takes your "receipt ID", and presents you with a list of all the items you purchased.

I can't imagine any decent-sized retailer isn't already maintaining records like this.

Re: Encoding your WiFi access point password into a QR code

#165

Post by madsbuch »

Normal_gaussian wrote: post #41
madsbuch wrote: post #36

Earlier quoted context omitted.

Or is it extra safety to use the CLI? Arguably it is easier to verify that a webapp is not sending the data to a 3rd party, than it is to verify that the CLI tool doesn't (easy network inspection from the developer tools).

Its also very easy to put a webapp into offline mode

Indeed it is! But we still need to reset the web app entirely after having used it. Service worker might cache messages.

Re: Encoding your WiFi access point password into a QR code

#167

Post by nkrisc »

SlowRobotAhead wrote: post #152
Spare_account wrote: post #145

Earlier quoted context omitted.

For comparison, my phone shows me the URL that the QR code decoded to, and prompts me to confirm that I want to browse to it

Remember bitly, AMP, CDNs? Also, as to something like a javascript exploit in a URL itself, QRs can hold a surprising amount of data, enough to max out most URL browser limits around 2,048 bytes.

Ok but if it's a bitly link then I'm still not clicking. Just like it an email includes an obviously shortened email.

Re: Encoding your WiFi access point password into a QR code

#168

Post by jlgaddis »

MrStonedOne wrote: post #110

If you are going to write an article about this on a website with geek in the domain name, and post it to hacker news, you are going to have to get more technical than that. Explaining the "WIFI:T:WPA" bit would have been nice to see. At the bare minimum a link to an article that explains it would be necessary to meet the bar. In the current state this article is a users level how to document, and fails to met the ba…

If you are going to comment on threads on a website, how do you know where the "bar" is?

By reading the "Guidelines" [0], of course!

In fact, the very first item on that page is titled "What to Submit" and explains exactly where that bar is:

> On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.

Apparently enough of us found it "interesting" for it to show up on the front page.

(The time you spent writing your comment would have been better spent banging your head against the wall -- at least you might have something (a bruise) to show for it!)

[0]: https://news.ycombinator.com/newsguidelines.html

Post reply on HN