tauzero

Which seems primarily concerned with making passwords hard to guess - which would be irrelevant if the primary form of attack was brute force. After all, "Pa$$word" and "Grea7 Gr33n 4rke$eizure£" would be equivalent in terms of a brute force attack, but I would guess that the NCSC would be rather more critical of the first than the second. For brute force attacks to be successful, the attacker needs two things - first, the actual password hash file, and second, enough time before the leaking of the hash file is discovered to go through the file and generate the hashes. If the organisation being attacked is honest and releases the information that the password file is out there as soon as it knows, the time between the initial leak and users changing their passwords is all that the hacker has. As an extra precaution to slow down the attacker, the hash file could also contain a high proportion of dummy users with password hashes generated at random. That would throw an extra bit of grit in the hacker's works.

The second piece has a very high infill and lots of perimeters which presumably why it would take so long to print. TBH it seems more like a "because I can" than "because it's a good idea" project. You could drill honeycomb holes in a piece of wood in much less than four days if it was the look you were after.

I don't use mine much - we've just started gigging, target is around 20-30 gigs a year, so when I do play around with it at home I want to operate it as I would at a gig. It takes about 30 seconds to switch network to either the X-Air itself or the Mikrotik.

I think you must have changed it or it's not the hAP mini that I'm using [1] - the default WAP IP address is 192.168.88.1 ( just checked the manual to make sure I'd got it right this time). [1] Well, obviously it's not the one I'm using, but YKWIM

Apologies, the 192.168.88.x was because I'm using a Mikrotik mini WAP.

Isn't it 192.168.88.x?

Tuning using harmonics is actually very slightly inaccurate, as the equal temperament fifth isn't 1.5 times the frequency of the fundamental (it's 1.49831 times). It's only a slight inaccuracy but carried across all five strings then it builds up. If you only play a 4-string then it doesn't matter, of course.

What BRX said. Odds are it will be a stereo barrel jack. These should be regarded as consumables. You will find life simpler if the leads are long enough to be able to pull the socket far enough out of the bass body to get to the terminals (but don't forget to thread the nut onto the leads before reassembly), and if they're not, consider extending them a bit for future convenience. Switchcraft are often recommended but they do cost an absolute fortune.

The battery positive isn't connected to the signal. There would generally be a capacitor on the preamp output to block DC anyway. With a SPDT switch, the ground could be connected to either the battery negative or the signal via the switch, which would mean the battery wouldn't drain if it was left plugged in with the switch switched to off.

"Here's one I did earlier"

Ah, @MartinB has already put the chart up on the previous page.

I had a bit of a dig around. Brute force attacks will depend on the method used to hash the password entries - https://en.wikipedia.org/wiki/Crypt_(C) has some information on that. Apparently bcrypt is better than SHA-based hashes as it takes longer to work out the hash. This is worth looking at too: https://www.komando.com/security-privacy/check-your-password-strength/783192/ It has a chart of how long a brute force attack would take on a password. When Chrome generates a password for you, it's 15 characters, mixed numbers, upper-case, lower-case, and special characters, which according to that chart would take 15bn years to crack. If I'm making up my own password that I can leave myself clues to (rather than writing it down in plain text), it will be 9 or more characters from that same set, so would take three weeks or five years to crack.

Out of context quote. "If a hash of the target password is available to the attacker, this number can be in the billions or trillions per second, since an offline attack is possible. If not, the rate depends on whether the authentication software limits how often a password can be tried, either by time delays, CAPTCHAs, or forced lockouts after some number of failed attempts. Another situation where quick guessing is possible is when the password is used to form a cryptographic key. In such cases, an attacker can quickly check to see if a guessed password successfully decodes encrypted data." If you're trying to access an account from outside, by logging in, you'll never do it.

There are 28 letters in the alphabet? Dammit, I've only been using 26 all my life. I was giving a second a go on the basis of a computer doing it and that being the time between sending and response. It would take quite a bit longer if somebody was typing them in.

When the interval between attempts is automatically increased each time you get it wrong, or where the username is locked out after a number of failed attempts, it becomes an even larger difference between generating the list and cracking the login.

If you're logged in to a Google account on both phone and PC, and using the same browser, and you've got the sync settings, er, set (in the Settings menu), it should synchronise.

Really? On the basis of taking a second for each try, using 10-character passwords composed of any upper-case, any lower-case, any number, and any of the non-alphanumeric characters on a computer keyboard (I used 30 for the number), it would take 12,066,345,950,656,448 hours to do all combinations. That's a bloody long day.

Looks like I'm down with the kids then.

The leads for the PA (5x mains lead, 2x 2-way extension, 4-way extension, 10-way extension, FOH XLR cables, foldback XLR cables, a few spare XLR leads) go into a wheelie suitcase. My gigbag (also used for rehearsals) came free from the Motorcycle Show one year, and holds a couple of jack-jack leads for if my pedalboard wireless dies, a few rechargeable AA batteries, a Zoom MS-60B, pair of Lekato wireless bugs, and for gigs an Android tablet plus spare, a towel, and a spare T-shirt.

But androids may dream of electric sheep.

Which tonewood is right for metal?

Mrs Zero is in a duo with a guitarist using backing tracks, hence playing at set tempo. Their performances aren't lifeless and robotic in the slightest. A lifeless and robotic performance will only be produced by a lifeless and robotic band.

That may well be where he's put it.

I'm another happy purchaser. After measuring one or two current straps, and translating to primitive measurements, I decided that the 42" to 58" one would be right for me. After hammering a 10mm punch through it and fitting Schaller straplocks, then shortening the neck side and lengthening the body side a bit, it got used in my first gig for 18 months and worked well. I don't think I had to shuffle it round on my shoulder at all, which is something I do find myself doing on occasion with other straps. I have shortened the neck end a bit more since then as it was a bit close to running out of padding - at the minimum length of the neck end of the strap, there's about an inch more padding over my left shoulder than in the photo below.

So don't throw away the 2.4GHz ones, eventually they'll be the ones using the unused frequencies. I didn't adequately test the power supply on my pedalboard prior to the first gig in a long time and the first use of the pedalboard, so the Line 6 G50 didn't work at all. I will say that the Lekato cheapie 5GHz ones I've been using in rehearsals have been fine, although we're talking months and not years of use.