Downloads:

588

Downloads of v 1.0.0:

588

Last Update:

01 Oct 2017

Package Maintainer(s):

Software Author(s):

  • Marcus Lum

Tags:

chrome cookie backup

ChromeCookieBackup

1.0.0 | Updated: 01 Oct 2017

Downloads:

588

Downloads of v 1.0.0:

588

Maintainer(s):

Software Author(s):

  • Marcus Lum

Tags:

chrome cookie backup

ChromeCookieBackup 1.0.0

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install ChromeCookieBackup, run the following command from the command line or from PowerShell:

>

To upgrade ChromeCookieBackup, run the following command from the command line or from PowerShell:

>

To uninstall ChromeCookieBackup, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade chromecookiebackup -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade chromecookiebackup -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure chromecookiebackup installed
  win_chocolatey:
    name: chromecookiebackup
    state: present
    version: 1.0.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'chromecookiebackup' do
  action    :install
  version  '1.0.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: chromecookiebackup,
    Version: 1.0.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller chromecookiebackup
{
   Name     = 'chromecookiebackup'
   Ensure   = 'Present'
   Version  = '1.0.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'chromecookiebackup':
  provider => 'chocolatey',
  ensure   => '1.0.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install chromecookiebackup version="1.0.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator flcdrg on 15 Oct 2017.

Description

Summary

This tool creates a decrypted SQLite backup file of the Cookies file in the Chrome User Data Profile folder, using the credentials of the logged on user's profile. The tool can restore from this backup file back into a Chrome User Profile Cookies using a different user account or domain or Windows installation, by re-encrypting the data using the other user's credentials.

Usage

  1. Run ChromeCookieBackup.exe using the Windows user account of the source user/computer and save a backup file
  2. Move the User Data folder in its entirety to a different user account or Windows installation, or simply create a new profile on the target computer.
  3. Run the tool on the target computer using the target user account, and restore the backup to the desired Chrome profile(s). You may map Chrome profiles from the backup file to profiles on the target computer.

Screenshot

Notes:

tools\ChromeCookieBackup.exe 
md5: 786C674581AD2065042E3A51AB67BDD0 | sha1: B8FA947208B9951D4849BF700B5D0048F6D20945 | sha256: 7ED9F271AB701B94E853A663369FED593E5A40AF04854A4D122EE239ACD474B1 | sha512: EE56E15A7B11CC1EBC67F8CD20AD31E7DD5D44D077309DCE23FAC31786CB5C305F653F2D01939B8ED9EB1C8E89D0816650B79FC048AA67A9FA5F9806810A50B1
tools\ChromeCookieBackup.exe.config 
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2" />
    </startup>
</configuration>
tools\ChromeCookieBackup.pdb
tools\LICENSE.txt 
Copyright (c) 2017 Marcus Lum

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
tools\Newtonsoft.Json.dll 
md5: C53737821B861D454D5248034C3C097C | sha1: 6B0DA75617A2269493DC1A685D7A0B07F2E48C75 | sha256: 575E30F98E4EA42C9E516EDC8BBB29AD8B50B173A3E6B36B5BA39E133CCE9406 | sha512: 289543F5EEA472E9027030E24011BEA1E49E91059241FE6EB732E78F51822313E47D1E4769FA1C9C7D6139F6A97DCFEF2946836B3383E8643988BF8908162FB9
tools\System.Data.SQLite.dll 
md5: F9418C91C218B3F03809E24C93B79FE2 | sha1: F4597869407F2B62E50E64E88865FC07AA344CBF | sha256: DC72EA4FCC2633D65DFD80EEF3509C6961E68995B96A3ED1668401574DF77436 | sha512: 4B042297A60F75783693110448E71B491BE1DE615637CAE78F44056D36380A0D7B340CA4D09889852EA5166C705A3B7FFBE0ADAA8007881699AF4A882B19F368
tools\System.Data.SQLite.dll.config 
<?xml version="1.0"?>
<!--
 *
 * System.Data.SQLite.dll.config -
 *
 * WARNING: This XML configuration file is intended for use within the NuGet
 *          package directories only.  Please do not copy this file to any of
 *          the build output directories because it could interfere with the
 *          native library pre-loading feature.
 *
 * Written by Joe Mistachkin.
 * Released to the public domain, use at your own risk!
 *
-->
<configuration>
  <appSettings>
    <add key="PreLoadSQLite_BaseDirectory"
         value="%PreLoadSQLite_AssemblyDirectory%\..\..\build\%PreLoadSQLite_TargetFramework%" />
  </appSettings>
</configuration>
tools\VERIFICATION.txt 
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The tool was downloaded from the release page 
<https://github.com/Marcus-L/chrome-cookie-backup/releases>. 
To verify the exe:

1. Download <https://github.com/Marcus-L/chrome-cookie-backup/releases/download/v1.0.0/ChromeCookieBackup-1.0.0.zip>
   to download the released binary archive which includes "ChromeCookieBackup.exe"
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum: 7ED9F271AB701B94E853A663369FED593E5A40AF04854A4D122EE239ACD474B1
tools\x64\SQLite.Interop.dll 
md5: 7BA0F41C37F7835094D4BD1AEF92EDA4 | sha1: 81AF2D7FFEC9D99FC0F54AE765FE8EC8F32AACF3 | sha256: 9DB8E965935BE690988BF290AC11B01CE5508ADB9945B4BD74F033A178F40F06 | sha512: 9ED64C83222007E8ACE264C930606E861EE05C53F2D0B5A6C252C116A2426DCCE7929CED0C0FFC4D260B3D440619E31E8BD3E0A77A8B5F7FE7CE0E81E4CD621E
tools\x86\SQLite.Interop.dll 
md5: 544EF841728185F7A4766E5F12B290F2 | sha1: 744C3032C5D6B2BCE2883A9F937AC1F4D941DA00 | sha256: 2FE073D8B5B42F18B4009340538148B12AED7E4903C6A62822F7CEDFB558FA8B | sha512: 65201C85E7FB7ADEFCD57692FD68DD5625C88A58D59C8344C29D8F28255D173BFE8846E794BB9A30C8F9E0599F38DBF482FE5235431E1C4E86B86A78BC1203FC

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
ChromeCookieBackup 1.0.0 588 Sunday, October 1, 2017 Approved

Release notes are available on GitHub: https://github.com/Marcus-L/chrome-cookie-backup/releases

Discussion for the ChromeCookieBackup Package

Ground Rules:

  • This discussion is only about ChromeCookieBackup and the ChromeCookieBackup package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ChromeCookieBackup, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus