Remove Password And Merge Pdf

[Coleman John]

Iaccidentally committed a password to a feature branch and synced that branch to remote. I tried to clean the branch commit history with bfg without success and with git-filter-repo I'm having other problems.

That password has been compromised. There is no way for you to trace where it might have gone after you pushed it to the remote. You can't put that genie back in the bottle; the only secure thing to do is to change the password.

That makes the rest of the discussion mostly academic. Either the password won't be changed and removing it from the history is an insufficient measure, or it will be changed and removing it from the history is cosmetic.

Not really. To fully remove the data from your local repo, you would have to make sure that the commit(s) containing it are unreachable from all refs as well as the reflog, and then you would have to force garbage collection. To truly remove it from the remote requires similar procedures, but how that sort of housekeeping is handled varies depending on how the repo is hosted.

It sounds like so far the password is only on your local feature branch and on the remote feature branch. The easiest way to remove it is to get rid of it locally and then force push it back out. Use amend or interactive rebase to rewrite the commit locally without the password, and then force push out your branch. At this point the commit will remain hidden on the server until it is garbage collected, and the amount of time that takes depends on the server. (Some git clients default to 60 days but it's impossible to know what your server defaults to without more info.)

Note if you already created a Pull/Merge Request with the branch that contained the commit with the password, then the server may keep the history of the included commits indefinitely. For this reason I would avoid squash merge at Pull/Merge Request time because it may keep the history of the commits for a long time.

If your repository is public, then you should assume that the password has already been compromised and you should change it immediately. In fact, this is probably the safest option even in a private repo too, unless you're fine with it being shared with your collaborators.

I need to combine two pdf files into one. But one of the file is Password Protected for Page Extraction. It has no other restrctions other than password protection for Page Extraction.

When I try to use File-->Combine-->Merge Files into Single PDF..., it asks for password and so I cannot combine the files.

may be you can try with this web link. 'FREEMYPDF.COM'. if you upload the PDF file which is having protection, that web link will remove all kind of protections and give normal PDF file. so that you can combine with your another PDF file. hope this will helpful...

Yes, this worked for me. If you downloaded it as a PDF go to the drop, click on 'Export a PDF,' Microsoft word, save it. Then open the Word document and click 'Save As' then switch it back to a PDF. I was able to combine the new file. A lot of steps, but it got the job done.

I set up a Facebook account with a school email address long ago, when only school email addresses were allowed. I graduated and no longer have that email address, nor access to it. I have also forgotten my password to that Facebook account.

I once tried emailing a Facebook Support on this, and they replied saying they would merge it with my existing account I have access to, but they never did. Are accounts like these doomed to exist on Facebook forever?

You should be able to regain access to old account via !/help/contact.php?show_form=hack_nologin_access - I've never used this and I don't know what they procedure is however. I guess once you have convinced them your are who you say you are, they will change the account email address, which will let you reset the password as normal.

@cachanco: 1Password doesn't create duplicates on its own; it only saves what you tell it to. So if you save a login at a website, and then later save another one there, you'll have two, and so on. The best thing to do is to determine which one you want to keep and delete the others. This isn't something 1Password can decide for you though, as it has no way of knowing your preference.

I can't say for sure what's happening, but I have a LOT of duplicates that showed up in the last several weeks/months. I know I didn't create all of them, so this feels like buggy behavior on the part of 1Password to me.

A "contacts" app is not even a remotely relevant comparison, as that data is not encrypted. "Merging" plaintext data is fairly easy, but not really feasible with encrypted data. I don't see what benefit would be had by merging duplicates though. Then instead of two items, you have one with two sets of duplicate details in it.

No matter the cause, I think the real issue is a lack of merge functionality. Duplicates will happen. Manually merging is so laborious that most people won't bother. 1Password would be better if it included a merge duplicates feature.

I brought up Contacts+ for:

1. Their UI for listing possible duplicates, allowing the user to browse through to make sure there's nothing unexpected before committing all of the merges

2. Their logic for deciding when to keep all values across duplicate contacts and when to keep one value.

Welcome to the forum, @chriscalo! We don't have a "merge" feature other than what you see with the existing Tools > Clean up Duplicate Items tool. The reason for this (historically) is that we've always erred on the side of having 1Password be very conservative with your data. The Duplicates tool doesn't merge/remove unless it's absolutely clear that the items are duplicates. We never want an AI being in a position to make decisions about which slightly-different version of your data is the "correct" one, since we're talking about some of your most valuable data. That means any non-automatic merge/"dupe"-removal is essentially a manual process anyway, and as a result, creating a specific interface for it is something that's just not risen to the top of our to-do list so far. It's something we've kept on the "someday, maybe" list for when we have spare developer cycles, but so far that's not yet happened. Thanks for letting us know you'd like such a feature; I've relayed your wishes to the development team.

@chriscalo - sounds good. FWIW, although I agree in general with your statement that "duplicates will happen," I also know from working with 1Password daily that they aren't entirely inevitable. Especially if you have a 1password.com membership, those days should be behind you unless you're doing a lot of migrating/copying/moving of data from other places. That's actually one of the benefits of a 1password.com membership -- a central repository where you don't have to worry about multiple sync keychains, some outdated, some new, in Dropbox or wherever. Point being: once you go through this process a single time, unless something odd happens, you shouldn't have to do it again. :)

Such a feature would be great. I have a lot of duplicates, because of different login domains. A manual merge command would be so helpful: Select 2 items, check if username + password match => merge by combining the "website" entries

Hi, I am a new subscriber to 1Password. I like it very much, but I also seem to end up with a number of entries for the same website: one will have the password, and the other the username. It usually seems to occur when I have saved the password for a site once, and then another time I come into the same site, redirected, from a different URL, and I end up at a screen which has just a username entry field. Then when I enter that username, and select "Save in 1Password" - there is a second entry created. Amazon.com and Amazon.co.uk seem to create this situation (e.g. if I click on an Amazon.com link, I initially go to that site, but then when I go to buy a kindle book, I am told that I need to buy it from Amazon.co.uk because I live in the UK. Then I am redirected to a page on Amazon.co.uk with just the username... but for some reason 1Password doesn't have the username stored against the Amazon.co.uk login. So I end up with 2 logins on 1Password - one with just the username, the other with just the password - both pointing to amazon.co.uk)

That's just an example that happened this morning. I can fix it manually by going through my logins in 1Password and finding those entries and deleting one - say the username one - and copying its value into the empty username field of the password one.

Thanks for taking the time to share your experience with this @Unbelievabl. I have seen what you've described, but fortunately only rarely. I can see how it might become an annoyance if it were happening a lot. Sites not splitting the login process across multiple pages, which I'd argue offers no real security benefit, would be a good start. We'll keep an eye out for it, and see if there are ways in which we can help improve the situation from our end.

Would it be impossible to do a feature, where I can select two entries, and choose "Merge" from the tools menu, and then 1password would merge them automatically if possible. And if there are conflicts for fields (different passwords) allow me to choose which one to take. URLs, sign-in pages, linked apps and such could just create duplicate fields which I could then prune as I see fit.

Not impossible, no. We do need to be careful about merging logins that have completely different URLs on them though. It isn't an unsolvable problem, so hopefully we'll be able to address it in the future.

I'd just like to add that merging logins would be a great feature. 1Password currently tell me I have 156 reused passwords. Most of the reused passwords aren't actually reused; they just ended up as two separate logins in 1Password. Almost always because of using the same account on different subdomains, but 1Password also sometimes creates a second entry for a login with no username. Some sites also allow the username to be an email address or a username, and 1Password will save each as a separate login.

3a8082e126