![]() The moment you build a new qt5 base package, all the other qt5 packages must be rebuilt. Packages also have cases where they specifically say “yes we require this specific library and version” as a result of AutoReqProv, which long story short helps determine some of the dependencies it needs. Not only that, this is what can cause a “compat” package to appear for some scenarios, for stuff that can’t be compiled on the newer version because of all the heavy changes (and thus requires a rewrite), so there’s a compatibility layer somewhere instead. (Ironkey USB works too.) The only other weakness I can think of is physical attacks (people break into your house and rubber ducky the USB ports etc.) For your point 4, a 39 character password is sufficient. First, make sure that the computer you are using is connected to the internet. If you are using = you are saying that it is exact and must be recompiled at some point, because there’s a chance the new version must be recompiled (note that this isn’t the only case). Instead of a USB, use an SD card with write protection or disk to transfer from your air gap to another PC. ![]() Some software and libraries are API stable like that. Another possibility as mentioned would be to use the portable version and have everything on the USB-stick. ![]() If you are using >= you are taking a gamble that the new versions of those libraries will not have API changes that will affect what you’ve built. I assume that when installing the version which stores everything on the computer, I might be able to transfer a certain file (s) via a USB-stick to the new computer and paste it into the correct KeePass folder. To add on to this, it really depends on the software.
0 Comments
Leave a Reply. |