Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "passports"
-
May be when the first human is born on Mars, we'll have to add "Planet of Birth" to our passports.😂11
-
10 years ago, I found a vulnerability in the connection between an insurer I was working for, and the network of databases of municipalities. I was only a hacker in so far as kids who watched Hak5 are considered hackers, so I always carried this laptop with a fake access point, package sniffer, wep crack, sslstrip, etc with me.
The vulnerabilities allowed me to register a new identity, for which I requested a passport.
Walking up to the town hall desk with two passports with different names, both mine, was pretty cool.
I did not do anything malicious, and was hired to fix the issues (wep encryption on insurers trusted wifi, and municipality postgres gave write access to all third parties)
For a few days I was the coolest kid in school though!2 -
On March 10th russian government tried to block or at least slow down twitter because twitter refused to delete some posts that russian govt wanted to be deleted.
Things that were down that day in russia:
- rostelecom (largest russian isp)
- FSB (russian CIA)
- SKRF (russian FBI)
- RKN (russian FBI but for internet control)
- gosuslugi (basically the govt website for all utilities imaginable including but not limited to medical help, taxes, passports, everything)
- kremlin website
Things that were up that day in russia, operating at a regular speed:
- twitter3 -
I've been using Firefox focus for a while, and for the most part, I like it. But why the hell won't it let me go to government websites (taxes, passports, etc)?
Regular Firefox has no issues with it, why does focus?3 -
One of our projects migrated their file-repository to another one during a major release.
Instead of giving this task to an experienced programmer, they gave it to the head of the respective dev department due to the usual release panic.
Soo.... He wrote the migration tool. It was executed during the release. Everything seemed fine so far.
A few days later. Someone from the above project came to my team due to some "strange behaviour on the production database".
They reported that they couldn't download some of the user's documents due to unknown reasons.
After quickly analyzing the current state of the new file-repository, we concluded that the affected documents did not exist in the new repository.
Then we took a look at the so called migration tool...
Well.. After nearly 30 min. we knew the root cause for that.
They only migrated the first 4 levels of the folder structure. Due to the assumption that "we don't use deeper nesting". (Facepalm)
As the head of their department wrote it, no one seems to questioned it either. Nor did they made a code review and ended up with a tool with hard coded urls to the production db, no version control, no build tool, no ci, nothing. Breaking nearly every possible company standard.
However.. That's not it. When analyzing their migration tool we noticed another even more dangerous thing.
They mixed up the id generation of the migrated documents resulting in a random assignment between customers and documents. Which is quite bad as this contains sensitive information. E.g. passports
They offered us quite a nice amount of money to fix this until EOB. We declinded as it was simply not possible in that time, but agreed to support them with the new tool.
After some time I heard that they migrated production again. And they fucked it up again. They never talked to us after we offered them support...
The third and final migration was written by us. Not only migrated it correctly. It was also way faster. By factor 20.
In the end we haven't gained anything from this rushed project as the penalties were piling up due to this fucked up migration.
After all this time I'm not sure who is to blame. In my opinion, partly all of them.
Head of department who can't and shouldn't code.
Seniors who didn't review the code and didn't ask for help.
Release mgmt who put way too much pressure on the devs. -
Fucking hell. So, I had an interview with market research company and in said interview I got told to bring my passport to my first shift training and it was ok if it was 5 years out of date. Additional info, they were supposed to call us on Thursday to book said shift and send us an email with a information pack. They never did.
Ok, day of shift comes along. After I booked it because no one fucking bothered to call any of us. Email never arrived but whatever. I go to the place and bring my 3 years out of date polish passport... Big fucking mistake. They don't seem to like polish passport seeing as how it's only the British ones that get the out of date is okay thing. So I'm sitting there still calm because sure, company policy, they have to do it. The training guy was nice and all, offered to get me to their office to speak to them about it. I accept and off we go.
At the office, I basically get the information that it's only British passports that get it and I basically can't use anything else as proof of ID, which is funny seeing as I have a polish identity card that I can leave and enter the country on within the EU. I suppose I'm going to try looking for a job that doesn't require passports for now and if I find a good one then they can go get fucked by a bull for all I care.
In conclusion, I get to wait till I'm 18 (thankfully only a month) to apply for a new passport in the local polish consulate. Brilliant. All thanks to some cunt that decided they require fucking passports with such beautiful (note the sarcasm) rules. The fucktards.
Hoping the apocalypse comes early for these cocksuckers,
BadFox