Live data from Hacker News

Show HN: Print a WiFi Login Card

wificard.io

341–347 of 347 posts

Re: Show HN: Print a WiFi Login Card

#341

Earlier quoted context omitted.

Can confirm. Zero problems in seven years. Though go for a model with wired Ethernet, still cheap and even more bulletproof.

Had zero issues with wifi so far. I can even directly print from my iPhone. Being able to place the damn thing anywhere and hide it in a closet is great.

It's good to hear that the situation is improved. Even so, I'd still try to wire it up whenever possible because diagnosing printer problems are the most boring kind of problem ever in the history of mankind. If I ever have printer problems I want to minimise the variables.

Re: Show HN: Print a WiFi Login Card

#342
post #170

Earlier quoted context omitted.

> To be fair it’s fairly easy to check that it didn’t send any data over the wire ... after the fact ... ... for a user of the web app who watches the network panel from their browser's developer tools

You just send false info first.

"just"? The above comment is overconfident.

Re: Show HN: Print a WiFi Login Card

#343

Earlier quoted context omitted.

And once you see them, you do what? Rollback reality?

I'm confused. Are you suggesting you should test with "real" data first?

I'm suggesting that monitoring an application for malicious behavior to detect it after the fact is the wrong approach. Once the data is sent, it's too late to do anything about it.

Oh you first try fake data? That's easy to counter. For example probabilisticly: the app tosses a coin and only sends the data with 50% chance the first time. Now half of people using your approach will think the app is safe and get their data stolen anyway. Or use some side channel, delay activity, ...

Re: Show HN: Print a WiFi Login Card

#344
post #340

Earlier quoted context omitted.

This rule blocks all IP traffic including DNS requests.

It only blocks IPv4 traffic, so on an IPv6 enabled host it can easily be bypassed without even involving DNS. But assuming an IPv4-only host, on a system using nscd, DNS lookup is performed over a Unix socket: Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 23 1445 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 owner UID match 1007 # setuidgid outtest ping -n 1 -4 google.com…

That's interesting. I've never used nscd, but the rule seems to work against both dnsmasq and systemd-resolved which just listen on loopback port 53.

As for IPv6 you can obviously just apply a similar rule using ip6tables (or the newer nftables, which I don't know how to use.)

Re: Show HN: Print a WiFi Login Card

#345

Earlier quoted context omitted.

By generating the QR code locally via JS. You can check the source code https://github.com/bndw/wifi-card/blob/master/package.json#L...

I’m not sure what you think I was asking the previous commenter. This makes no sense as a reply.

I thought you were asking the parent how the QR generation worked, if it didn't send something to a server.

Re: Show HN: Print a WiFi Login Card

#346
post #202
post #67

Earlier quoted context omitted.

Answering as the author who also understands the fundamentals of all of the technologies involved and questions much of what goes on in the minds of today's web developers and designers-- I use Make as the standard way to interact with every repo I own. This allows me to type `make build` instead of `$some-language-specific-command-I-forget-in-2-weeks`. I use Docker for distributing every app I build. If the app is a…

> I use Make as the standard way to interact with every repo I own. After much fussing around with many kinds of solutions, this too is what I have settled on. Download repo and run `make` will "do the needful" to get you going, and all the major entry points are make stanzas.

except that "making" anything, or any commands in a new language he forgot, etc = entirely unnecessary for a single static html page.

Re: Show HN: Print a WiFi Login Card

#347
post #220
post #75

Earlier quoted context omitted.

For WPA3 WIFI:S:SSID;T:WPA3;P:PASSWORD;;

Can you elaborate? Why doesn't the traditional WPA1/WPA2 string work? What happens if a non-WPA3 client scans this new one?

Late reply, but when I was setting up WPA3 a few months ago I used Android 11 as a reference and that is what it spits out from the Settings share screen. Without it iirc, it would search and search and never connect.
Post reply on HN