Should use nullptr :P
i guess nil wouldn't work either - it probably worked because of sql NULL keyword.
https://en.wikipedia.org/wiki/Null_(SQL)
NULL license plate not such a bright idea
211–220 of 484 posts
Re: NULL license plate not such a bright idea
#212Earlier quoted context omitted.
It reminds me of the guy who owns nissan.com, who probably blew his life savings on lawyers defending himself from Nissan Motors lawyers for decades.
I wonder how much you could sell that to them for if you were really good at negotiating. Maybe as much as $100k?
Multiply that by a thousand or more if they had already accrued $10 million in "damages" by 1999 as they claimed. Apparently it would be extremely valuable to them.
Re: NULL license plate not such a bright idea
#213Earlier quoted context omitted.
You obviously still don’t know what the phrase “choosing to die on a hill” means.
Yeah, just b/c he is stubborn enough and doesn't wish to give up his vanity plate instead of folding. Pretty much nothing that hard/uphill battle has happened to him.
There are two options: die on the hill, or retreat. He is not retreating. Therefore he has chosen to die on the hill.
Re: NULL license plate not such a bright idea
#214I own a rare collector car with a three-digit VIN. This has caused endless hassles at the DMV as well as the insurance office. Sometimes we find success by prepending the necessary number of zeros, before the VIN. Other instances in the same system require appending zeros after the VIN. The true VIN has a hyphen but that never makes it into the DMV's system. One time I got stuck in a particularly nasty loop where the…
I had a car—a 1971 Toyota Landcruiser FJ55–that technically had a tilde(~) in the VIN. It was in the format: FJ55~123456. When I bought it, the title had the VIN as FJ550123456. I just accepted and ignored it for a while, but when I decided to sell the car, given that most of my potential buyers were out of state (and in most states, out of state purchases require a VIN inspection) I tried to get it fixed. After six months of working The motor vehicles department here, getting an inspection by state police, and everything else, I found out that their software couldn’t handle and non-alpha numeric characters. In the end they decided to change the title to FJ55123456 so it skipped the tilde but didn’t replace it with a character that didn’t exist on the vehicle.
Re: NULL license plate not such a bright idea
#215Could someone devise a SQL injection attack using a custom-made license plate? I'm imagining someone printing up x'; DROP TABLE drivers; -- on a plate, and driving up and down the highway past automated license-plate readers.
I have DBA registered in my local county. The DBA name is:
' or 1=1; drop table sys.systable; -- Computer Services
Re: NULL license plate not such a bright idea
#216Similarly I used to wonder how awful it would have been to own example.com ... until I found out it was an IANA special-use domain.
But someone still owns test.com, and I can't imagine what that mail server goes through.
Re: NULL license plate not such a bright idea
#217Earlier quoted context omitted.
All we had to do was register our cars in each others names. When I was married, my car was registered to her and vice versa. The redlight/photoradar laws in my state required that the company operating the devices had to match the pic of the driver violating the law, to the pic of the registered owner via the license plate. If they couldn't match them, no ticket was issued as you can't prove who was driving. That's…
Where i am from the ticket is issued to the vehicle owner, doesn't matter who was driving. On the plus side it means that you can get a photoradar ticket for driving 300km/h and not lose your licence, just pay the fine. P.S. If the driver must be recognized does it mean that motorcyclists are exempt from photoradar fines?
I thought that motorcycles already didn't really show up on the photoradar scanners. That's the way it is here, but I can totally see that being a jurisdiction by jurisdiction thing.
Re: NULL license plate not such a bright idea
#218Reminds me of the story of Ireland's worst Polish driver who never got caught: http://news.bbc.co.uk/2/hi/uk_news/northern_ireland/7899171....
I've also heard a similar story of a Finnish man who got a ticket in the UK, and on closer inspection found his name on the ticket listed as Mr. Ajokortti Körkort. Thats "driver's licence", first in Finnish, then Swedish, and is written at the top of the driver's license card. That said, I find these stories a little hard to credit, since you'd expect police officers in the EU to be fairly familiar with the standard…
Irish driving licences didn't start to use the standard credit-card-sized EU format until a few years ago. They were paper booklets which had long since been phased out in the rest of Europe.
Re: NULL license plate not such a bright idea
#219Earlier this summer I decided that I'd found a loophole and ordered 'N0 TAG' and 'N0NE' (zeros) for my motorcycles. The license plate font doesn't distinguish between 0 and O but the computers seem to account for visually similar characters -- I could not order the same plates with Os after they'd issued.
Haven't caught anyone else's tickets so far. SunPass won't accept 'N0 TAG' being associated with my transponder tho (have not tried 'N0NE' yet).
I did get pulled over on my very first ride with 'N0 TAG' and the first words out of the cop's mouth were 'Is that tag legit?' That may or may not have been a factor in catching a warning instead of a ticket that I absolutely earned.
Re: NULL license plate not such a bright idea
#220Earlier quoted context omitted.
>Avoid backticks in passwords. Is there even a reason to include special characters in passwords? They add 10% more security[1] but cause all sorts of issues with systems. Just use an alphanumeric password that's 10% longer, and if special characters are mandatory, use a safe character at the end like _ or -. [1] 6.55 bits per character (all printable ascii characters) rather than 5.95 (only alphanumeric)
Based on your numbers they add 10% entropy per character. Which compounds into an increase of 210% over a length of 12 characters. Thus you'd need the password to be at least 3 times longer with only alphanumeric characters to have the same entropy.
no, check your math.
number of characters required for 128 bit entropy password using alphanumerics: 21.49[1]. round off to 22
number of characters required for 128 bit entropy password using all printable characters: 19.5[2]. round off to 20.
22/20 = 110%
[1] https://www.wolframalpha.com/input/?i=solve+log_2(62%5Ex)%3D... (under "real solution", click on "approximate form")
[2] https://www.wolframalpha.com/input/?i=solve+log_2(94%5Ex)%3D...