awda

Is 16-byte Poly1305 more secure than 16-byte HMAC-SHA1? (Actually curious. Citation: I've done all the matasano crypto challenges, and all of the stripe µctf stuff :).)

> Poly1305 also saves network bandwidth, since its output is only 16 bytes compared to HMAC-SHA1, which is 20 bytes.

You could also just truncate HMAC-SHA1 to 16 bytes, right?

If anyone wants to read 1985-era MSDOS 1.x floppies in Linux, support is coming in 3.16[0] ;-).

[0]: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next...

I don't know anything about ACH, but the author could be referring to FTP-over-TLS ("FTPS") or SFTP (unrelated protocol over SSH), both of which use the initials FTP but aren't as wholly insecure as vanilla FTP.

Me either. But to scrape off 80% of memory use, you had to be wasting 400% of the lower limit -- which seems dumb in retrospect.

It seems more like they were doing something really dumb before to waste 11.5GB unnecessarily, but potato poh-tat-oh. I'm just happy it keeps getting better. :)

And you can be tried as an adult at 15 or 16 years old, but you can't vote until you're 18. What kind of bullshit is that?

Most higher-level politicians are independently wealthy. Lowering congressional pay would just serve to further weed out non-super-affluent candidates. I guess it depends on how you like your politics, so I won't pass judgement either way.

You're right, I looked up Bud Light and it was 4.2 and I was confused :/.

Not sure on if 3.2 and ABW applies in all 3.2 states. My only knowledge of this comes from my ~75 year old uncle, who told me that you used to be able to buy 3.2 beer when you were 18 (depending on the state; he was probably in CA or WA).

I don't drink anymore, but when I did, it was all craft / microbrews, which are typically 5-7% ABV ;). The lowest I've seen is 4.7% (Founder's All Day IPA, a session IPA). And some of the DIPAs and Imperial stouts and wild ales / Belgian trippels/quads go to 8-12% ABV.

They say there was no evidence of gender-based harassment, but I don't see them claiming "there was no evidence of harassment" either. Don't know enough to pass judgement.

Business relationships are different from personal relationships, and "solicit," in this case, does not mean literally request the email. It is perfectly reasonably to describe unexpected email from a friend as solicited and unexpected product email from a business as unsolicited (even if you've had contact with them previously).

It is unlikely that the business is your friend ;-).

Ah, did not realize that. Thanks for clarifying.

It dumbed down the malloc() interface, for example (no tags).

At landing? Don't believe so. I think if they had that, they would have been able to say more than they did. And I think they mentioned not great weather?

It would be cool if they did :).

Well, also according to Musk, its last reported velocity was 360 m/s. That's a pretty hard landing.

Maybe education, but I haven't heard of that use. NetBSD tends to go for simplicity of code over everything else.

Right. There is a lot of old / stale / bad material out there from 2.6, 2.4, and even earlier kernels... that just doesn't apply or work anymore in 3.x. It's frustrating.

You end up adding a minor feature to the FAT filesystem.

They are exaggerating :).

Thanks, this was very helpful. Here's what I did (converting VMware Workstation VM):

  1) Followed rwmj's guide to setting up a br0 device for libvirt in Fedora.
  2) Deleted all vmware snapshots. sync. sync.
  3) Grabbed vmware2libvirt from Ubuntu (it's just a standalone python script) and
     used it with --bridge br0 -f foo.vmx > foo.xml.
  4) Converted my vmdk to raw with qemu-img, moved it to /var/lib/libvirtd per your
     instructions
  5) Edited my xml to point to the right disk, use the qemu/raw driver, use the right
     path for kvm (/urs/bin/qemu-kvm on Fedora).
  6) Import into libvirt with virsh define foo.xml
  7) virsh start foo

It just works! Great. And virt-viewer over qemu+ssh is great; I run this VM on a headless box on the LAN from my desktop.

I finished this, but I still have no idea where I can actually help (aside from janitorial code cleanups and some vague notion of improving the documentation).

Bud light and other light beers tend to land in 3.2% territory, I think. And some brands specifically make 3.2 beer catering to the PA market (it may not even be available in your area if your state doesn't have weird restrictions around 3.2%, like PA or UT).

I'm not sure you can't get halfway decent public schools in the cities, but they tend to be local to wealthier neighborhoods. And suburbs in the area I'm from tend to at least have apartments and townhomes, which are a nice middle ground (at least as far as saving on heating, cooling, cleaning, space, cost). The commute still sucks, of course.

Thanks, this looks very helpful.

Ok, that gets me the disk image :). What about configuration?

Ok, but what about everything else in a .vmx (memory configuration, network configuration, serial device configuration)?

Anyone know if there are good tools for migrating a VMware .vmx and accompanying files to a QEMU machine? Or is this more complicated than I imagine? I'd like to ditch the VMware crap modules that break with every kernel upgrade in favor of KVM.

This is also bad information. Kernel taint is a bitmap that represents a number of things:

  - Proprietary software (non-gpl-compatible, as you say. ex: vmware)
  - Crap (drivers/staging)
  - Out-of-tree modules (virtualbox)
  - whether the kernel has hit a BUG already
  - ...
  - lots of stuff

VirtualBox taints the kernel because it is out-of-tree, not because it is GPL-incompatible. Why is a GPL compatible kernel module(s) not merged yet?

Because the code quality is crap.

I was mostly aiming for unique -> no hash collisions.

If 'select min(keycolumn) from footable' is relatively stable and keys are created ascending (databases do this, right?), a resizing slice (with 0-min() elided from the bottom) seems like a good alternative to a hashing structure.

If the key-space is relatively sparse, this will waste more memory than the hash, of course.