1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] google-chrome-103.0.5060 - choose password for new keyrin

    From thelma@sys-concept.com@21:1/5 to All on Fri Jul 8 04:20:01 2022
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc. Is it needed?

    Was it discuss before?

    --
    Thelma

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to thelma@sys-concept.com on Fri Jul 8 04:30:01 2022
    thelma@sys-concept.com wrote:
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc.  Is it needed?

    Was it discuss before?



    I don't use Chrome but google found this.

    https://forums.linuxmint.com/viewtopic.php?t=312289

    This may help too.

    https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups

    Does one of those help?  They seem to address the problem in slightly different ways. 

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to thelma@sys-concept.com on Fri Jul 8 05:30:01 2022
    thelma@sys-concept.com wrote:
    On 7/7/22 20:23, Dale wrote:
    thelma@sys-concept.com wrote:
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc.  Is it needed?

    Was it discuss before?



    I don't use Chrome but google found this.

    https://forums.linuxmint.com/viewtopic.php?t=312289

    This may help too.

    https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups >>

    Does one of those help?  They seem to address the problem in slightly
    different ways.

    Dale

    :-)  :-)

    Thanks,  there is a lot of information how to by-pass it but very
    little explanation which application request it or why is it there.
     




    One thing I read makes it sound like it is for a built in password
    remembering tool. I know Firefox and Seamonkey has the same but I
    disable those since I use BitWarden anyway.  One would think there would
    be a setting in preferences to just disable all that.  I suspect few use
    them given the popularity of LastPass, BitWarden and other tools that
    are much more secure and portable.  Maybe looking for a password tool
    setting would help.  I tried Chrome ages ago, didn't like it at all. 
    That was several years ago so I'm clueless on it now.  Just thought
    those suggestions might help. 

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From thelma@sys-concept.com@21:1/5 to Dale on Fri Jul 8 05:50:01 2022
    On 7/7/22 21:28, Dale wrote:
    thelma@sys-concept.com wrote:
    On 7/7/22 20:23, Dale wrote:
    thelma@sys-concept.com wrote:
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc.  Is it needed?

    Was it discuss before?



    I don't use Chrome but google found this.

    https://forums.linuxmint.com/viewtopic.php?t=312289

    This may help too.

    https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups >>>

    Does one of those help?  They seem to address the problem in slightly
    different ways.

    Dale

    :-)  :-)

    Thanks,  there is a lot of information how to by-pass it but very
    little explanation which application request it or why is it there.





    One thing I read makes it sound like it is for a built in password remembering tool. I know Firefox and Seamonkey has the same but I
    disable those since I use BitWarden anyway.  One would think there would
    be a setting in preferences to just disable all that.  I suspect few use them given the popularity of LastPass, BitWarden and other tools that
    are much more secure and portable.  Maybe looking for a password tool setting would help.  I tried Chrome ages ago, didn't like it at all.
    That was several years ago so I'm clueless on it now.  Just thought
    those suggestions might help.

    Dale

    :-)  :-)

    Starting chrome with "--password-store=basic" solved the problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to thelma@sys-concept.com on Fri Jul 8 06:00:01 2022
    thelma@sys-concept.com wrote:
    On 7/7/22 21:28, Dale wrote:
    thelma@sys-concept.com wrote:
    On 7/7/22 20:23, Dale wrote:
    thelma@sys-concept.com wrote:
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc.  Is it needed?

    Was it discuss before?



    I don't use Chrome but google found this.

    https://forums.linuxmint.com/viewtopic.php?t=312289

    This may help too.

    https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups



    Does one of those help?  They seem to address the problem in slightly >>>> different ways.

    Dale

    :-)  :-)

    Thanks,  there is a lot of information how to by-pass it but very
    little explanation which application request it or why is it there.
     



    One thing I read makes it sound like it is for a built in password
    remembering tool. I know Firefox and Seamonkey has the same but I
    disable those since I use BitWarden anyway.  One would think there would
    be a setting in preferences to just disable all that.  I suspect few use
    them given the popularity of LastPass, BitWarden and other tools that
    are much more secure and portable.  Maybe looking for a password tool
    setting would help.  I tried Chrome ages ago, didn't like it at all.
    That was several years ago so I'm clueless on it now.  Just thought
    those suggestions might help.

    Dale

    :-)  :-)

    Starting chrome with "--password-store=basic" solved the problem.
     




    You found a solution that works.  That's great.  Now you can get back to doing more important things.  ;-)

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From thelma@sys-concept.com@21:1/5 to Dale on Fri Jul 8 07:20:01 2022
    On 7/7/22 21:50, Dale wrote:
    thelma@sys-concept.com wrote:
    On 7/7/22 21:28, Dale wrote:
    thelma@sys-concept.com wrote:
    On 7/7/22 20:23, Dale wrote:
    thelma@sys-concept.com wrote:
    After update to new chrome browser "google-chrome-103.0.5060"
    A popup shows up:

    "choose password for new keyring"

    No explanation what is it, how to change it etc.  Is it needed?

    Was it discuss before?



    I don't use Chrome but google found this.

    https://forums.linuxmint.com/viewtopic.php?t=312289

    This may help too.

    https://superuser.com/questions/890150/completely-stop-gnome-keyring-popups



    Does one of those help?  They seem to address the problem in slightly >>>>> different ways.

    Dale

    :-)  :-)

    Thanks,  there is a lot of information how to by-pass it but very
    little explanation which application request it or why is it there.




    One thing I read makes it sound like it is for a built in password
    remembering tool. I know Firefox and Seamonkey has the same but I
    disable those since I use BitWarden anyway.  One would think there would >>> be a setting in preferences to just disable all that.  I suspect few use >>> them given the popularity of LastPass, BitWarden and other tools that
    are much more secure and portable.  Maybe looking for a password tool
    setting would help.  I tried Chrome ages ago, didn't like it at all.
    That was several years ago so I'm clueless on it now.  Just thought
    those suggestions might help.

    Dale

    :-)  :-)

    Starting chrome with "--password-store=basic" solved the problem.





    You found a solution that works.  That's great.  Now you can get back to doing more important things.  ;-)

    Dale

    :-)  :-)

    By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge:
    [ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux) -systemd -test"
    Upgrading just "chrome" did not ask me for any keyring password.

    I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dale@21:1/5 to thelma@sys-concept.com on Fri Jul 8 08:50:01 2022
    thelma@sys-concept.com wrote:
    On 7/7/22 21:50, Dale wrote:


    You found a solution that works.  That's great.  Now you can get back to >> doing more important things.  ;-)

    Dale

    :-)  :-)

    By upgrading one of my system, I've just noticed this behaviour is
    enforced (I think) by new package that was pulled by emerge:
    [ebuild  N    ] gnome-base/gnome-keyring-42.1  USE="pam ssh-agent (-selinux) -systemd -test"
    Upgrading just "chrome" did not ask me for any keyring password.

    I don't use gnome, I use XFCE but I guess one of the package pull this
    as a dependency.
     




    Could disabling a USE flag remove that dependency?  It may not be google-chrome itself but something else it depends on.  Using the --tree option may help here.  Masking the keyring package may force emerge to
    shine some light on what needs the package as well.  It should grumble
    about it being masked along with what needs it. 

    Sort of odd that something like this pops up all of a sudden with no
    notice of the change. 

    Dale

    :-)  :-) 

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dr Rainer Woitok@21:1/5 to thelma@sys-concept.com on Fri Jul 8 11:10:01 2022
    Thelma,

    On Thursday, 2022-07-07 23:13:47 -0600, thelma@sys-concept.com wrote:

    ...
    By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge:
    [ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux) -systemd -test"
    Upgrading just "chrome" did not ask me for any keyring password.

    I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency.

    Run

    $ emerge --pretend --unmerge gnome-base/gnome-keyring

    to get the list of packages depending on "gnome-base/gnome-keyring".
    Then check each of these packages for a set USE flag causing "gnome- base/gnome-keyring" to be pulled in. At least in many cases such a USE
    flag will be named just "gnome-keyring".

    Sincerely,
    Rainer

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Covici@21:1/5 to Dr Rainer Woitok on Fri Jul 8 11:50:02 2022
    On Fri, 08 Jul 2022 05:01:17 -0400,
    Dr Rainer Woitok wrote:

    Thelma,

    On Thursday, 2022-07-07 23:13:47 -0600, thelma@sys-concept.com wrote:

    ...
    By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge:
    [ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux) -systemd -test"
    Upgrading just "chrome" did not ask me for any keyring password.

    I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency.

    Run

    $ emerge --pretend --unmerge gnome-base/gnome-keyring

    to get the list of packages depending on "gnome-base/gnome-keyring".
    Then check each of these packages for a set USE flag causing "gnome- base/gnome-keyring" to be pulled in. At least in many cases such a USE
    flag will be named just "gnome-keyring".
    Should not this instruction say emerge --pretend --depclean rather
    than --unmerge ?

    --
    Your life is like a penny. You're going to lose it. The question is:
    How do
    you spend it?

    John Covici wb2una
    covici@ccs.covici.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matt Connell@21:1/5 to All on Fri Jul 8 15:40:01 2022
    By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge:
    [ebuild  N    ] gnome-base/gnome-keyring-42.1  USE="pam ssh-agent (-selinux) -systemd -test"

    I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency.

    Anecdote time from a fellow XFCE user. I previously fought against
    having gnome-keyring and eventually gave up, since more and more things
    wanted to use it. Now, I find it quite useful. Lots of GTK
    applications (and XFCE is GTK based) want to use gnome-keyring, and
    between evolution, dbeaver, nheko, and others, it has become a benefit
    (to me) rather than an annoyance.

    If you decide to give it a try, app-crypt/seahorse is a useful
    companion application for managing the keyring's contents.


    Should not this instruction say emerge --pretend  --depclean rather
    than --unmerge ?

    Since its pretended, the result is the same, ultimately.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arve Barsnes@21:1/5 to Matt Connell on Fri Jul 8 16:10:01 2022
    On Fri, 8 Jul 2022 at 15:34, Matt Connell <matt@connell.tech> wrote:
    Should not this instruction say emerge --pretend --depclean rather
    than --unmerge ?

    Since its pretended, the result is the same, ultimately.


    Actually, none of them gives you any info about why a package is
    installed, and --unmerge doesn't even try to check. Without --pretend
    it's perfectly happy to let you shoot yourself in the foot. What you
    actually need to get portage to tell you what requires the package in
    question is
    # emerge --pretend --depclean --verbose gnome-keyring

    Regards,
    Arve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matt Connell@21:1/5 to Matt Connell on Fri Jul 8 16:10:01 2022
    On Fri, 2022-07-08 at 09:34 -0400, Matt Connell wrote:
    Should not this instruction say emerge --pretend  --depclean rather
    than --unmerge ?

    Since its pretended, the result is the same, ultimately.

    I take this back. You're correct. depclean should show you what
    packages depend on $package which is what is desired.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From thelma@sys-concept.com@21:1/5 to Arve Barsnes on Fri Jul 8 18:30:01 2022
    Thelma
    On 7/8/22 08:02, Arve Barsnes wrote:
    On Fri, 8 Jul 2022 at 15:34, Matt Connell <matt@connell.tech> wrote:
    Should not this instruction say emerge --pretend --depclean rather
    than --unmerge ?

    Since its pretended, the result is the same, ultimately.


    Actually, none of them gives you any info about why a package is
    installed, and --unmerge doesn't even try to check. Without --pretend
    it's perfectly happy to let you shoot yourself in the foot. What you
    actually need to get portage to tell you what requires the package in question is
    # emerge --pretend --depclean --verbose gnome-keyring

    Regards,
    Arve

    OK I think I got to the bottom of this, it is caused by package upgrade: [ebuild U ] app-crypt/gcr-3.41.0 [3.40.0] USE="gtk introspection vala -gtk-doc -systemd% -test"

    All other packages are new and pull-in as a dependency:

    gnome-base/gnome-keyring-42.1 pulled in by:
    virtual/secret-service-0 requires gnome-base/gnome-keyring

    grep secret-service upgrade_07-07-22.txt
    [ebuild N ] virtual/secret-service-0

    virtual/secret-service-0 pulled in by:
    app-crypt/libsecret-0.20.5-r3 requires =virtual/secret-service-0, virtual/secret-service

    grep app-crypt/libsecret upgrade_07-07-22.txt
    [ebuild N ] app-crypt/libsecret-0.20.5-r3 USE="crypt introspection vala -gtk-doc -test -tpm" ABI_X86="(64) -32 (-x32)"

    app-crypt/libsecret-0.20.5-r3 pulled in by:
    app-crypt/gcr-3.41.0 requires >=app-crypt/libsecret-0.20

    And "app-crypt/gcr" was an upgrade.

    So maybe it is better to leave it as it is, instead of fighting the system :-) But it would be nice if there were some notes about it during emerge.
    All of a sudden when starting chrome, a message box pops up "choose password for new keyring" (without any explanation) and all screen is frozen, only option is to enter a password or "cancel it".

    Thelma

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to thelma@sys-concept.com on Fri Jul 8 19:20:01 2022
    On Fri, 8 Jul 2022 10:20:12 -0600, thelma@sys-concept.com wrote:

    gnome-base/gnome-keyring-42.1 pulled in by:
    virtual/secret-service-0 requires gnome-base/gnome-keyring

    grep secret-service upgrade_07-07-22.txt
    [ebuild N ] virtual/secret-service-0

    virtual/secret-service-0 pulled in by:
    app-crypt/libsecret-0.20.5-r3 requires =virtual/secret-service-0, virtual/secret-service

    The secret-service ebuild contains

    RDEPEND="|| (
    gnome-base/gnome-keyring
    app-admin/keepassxc
    )"

    so emerge -1 keepassxc will keep gnome-keyring out, but you need one of
    these password managers.


    --
    Neil Bothwick

    Voting Democrat or Republican is like choosing a cabin in the Titanic.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLIZZoACgkQ92eFu0QS MJg3XA//VlkmpzVw3H6vQ85LA699wdU9eOijgfMDW+XrukZRxqetNnhrJkC62h7I zJqJdqQ8X15rW7pIqK1TFyIcMRyaXMVbIP2tYYfOwoxNoiN6NRW0Y56t9uaOJqP7 juxwJiJFKvKoKcM0kN2jOjrnwyivp3by1O11kHt7CurhZcAyZCh7kPANZZud2ZoJ JYMEO1x/RAeZhSB4CjV3iMq/HjoSZ1cKnkEFXhWoTCWh2TkRJOoTqow3OgHP943D 2uTj+uocQi/L6ilAdaNVsbbN+I4jCUG07Kwmvwq0sdADW5jbIQjqmq6/TFWGrf8P VoT3g4qvE8r9dUkBviKODFdbtRwheDAwKkinVDQEwD99glUtag30nS9v3j9uqZul 8+hKoZVln6+cjxwiE2m2ru9F991WLLUkR81IXl5PYtqsYhSL7adllxZH7qSE68NO +ajHJjkoULPcAqf5+/ZIP461Pj9/Rwc01uci2i02lAz1CdYU2GtHy9jCcMGPXFWZ 3+Yh6d3G/9oM0++vDFbGtMMIdjNbCVlZ8MTk7ydjsOQNI9uVBIIbHgfagQRK1GgQ qLxDnFX++cR6Ip/ZtSCEZZwug9qfmjSkk00PUJy20DbdT0AAuOWcsBsqgkEFnyND 1pX0rrSSWGRwFaRKW8oFiJK2eusgn5XXVnQf8Nz2fm1pMklrz0I=
    =5IDW
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matt Connell@21:1/5 to thelma@sys-concept.com on Fri Jul 8 20:10:02 2022
    On Fri, 2022-07-08 at 11:26 -0600, thelma@sys-concept.com wrote:
    - if I enter password for the keyring, how to change it in the future.

    The aforementioned seahorse will allow you to manage this. I'm certain
    there's a CLI way to access it.

    - do I need to keep that password, will I be ask to use the password

    You'll be asked for this password whenever some application tries to
    read protected secrets from the keyring, eg. Chrome, in this case.

    I believe pam can be configured to allow gnome-keyring to authenticate
    against your X(FCE) session login, but I've never bothered to set this
    up.

    - which application application are using this keyring?

    Lots of things can hook into the keyring optionally. I mentioned a
    few. Chrome, Chromium, Brave, dBeaver, nheko, Evolution.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From thelma@sys-concept.com@21:1/5 to Neil Bothwick on Fri Jul 8 19:30:01 2022
    On 7/8/22 11:12, Neil Bothwick wrote:
    On Fri, 8 Jul 2022 10:20:12 -0600, thelma@sys-concept.com wrote:

    gnome-base/gnome-keyring-42.1 pulled in by:
    virtual/secret-service-0 requires gnome-base/gnome-keyring

    grep secret-service upgrade_07-07-22.txt
    [ebuild N ] virtual/secret-service-0

    virtual/secret-service-0 pulled in by:
    app-crypt/libsecret-0.20.5-r3 requires =virtual/secret-service-0,
    virtual/secret-service

    The secret-service ebuild contains

    RDEPEND="|| (
    gnome-base/gnome-keyring
    app-admin/keepassxc
    )"

    so emerge -1 keepassxc will keep gnome-keyring out, but you need one of
    these password managers.

    I intent to keep it as it is. My question are:

    - if I enter password for the keyring, how to change it in the future.
    - do I need to keep that password, will I be ask to use the password
    - which application application are using this keyring?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dr Rainer Woitok@21:1/5 to you on Sat Jul 9 19:10:02 2022
    Thelma,

    On Friday, 2022-07-08 10:20:12 -0600, you wrote:

    ...
    app-crypt/libsecret-0.20.5-r3 pulled in by:
    app-crypt/gcr-3.41.0 requires >=app-crypt/libsecret-0.20

    And "app-crypt/gcr" was an upgrade.

    This does not happen with the stable version 3.40.0 of "app-crypt/gcr",
    only with the non-stable version 3.41.0 which has this additional dep- endency. But then, as soon as 3.41.0 will become stable you'd have the
    same problem.

    Sincerely,
    Rainer

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wols Lists@21:1/5 to Dale on Sat Jul 9 19:20:01 2022
    On 08/07/2022 07:44, Dale wrote:
    thelma@sys-concept.com wrote:
    On 7/7/22 21:50, Dale wrote:


    You found a solution that works.  That's great.  Now you can get back to >>> doing more important things.  ;-)

    Dale

    :-)  :-)

    By upgrading one of my system, I've just noticed this behaviour is
    enforced (I think) by new package that was pulled by emerge:
    [ebuild  N    ] gnome-base/gnome-keyring-42.1  USE="pam ssh-agent
    (-selinux) -systemd -test"
    Upgrading just "chrome" did not ask me for any keyring password.

    I don't use gnome, I use XFCE but I guess one of the package pull this
    as a dependency.





    Could disabling a USE flag remove that dependency?  It may not be google-chrome itself but something else it depends on.  Using the --tree option may help here.  Masking the keyring package may force emerge to
    shine some light on what needs the package as well.  It should grumble
    about it being masked along with what needs it.

    Sort of odd that something like this pops up all of a sudden with no
    notice of the change.

    So why am I glad my USE= includes "-gnome" :-)

    Although I don't use Chrome, so I wouldn't notice anyways :-)

    Cheers,
    Wol

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Wols Lists on Sat Jul 9 23:40:01 2022
    On Sat, 9 Jul 2022 18:12:51 +0100, Wols Lists wrote:

    Could disabling a USE flag remove that dependency?  It may not be google-chrome itself but something else it depends on.  Using the
    --tree option may help here.  Masking the keyring package may force
    emerge to shine some light on what needs the package as well.  It
    should grumble about it being masked along with what needs it.

    Sort of odd that something like this pops up all of a sudden with no
    notice of the change.

    So why am I glad my USE= includes "-gnome" :-)

    Although I don't use Chrome, so I wouldn't notice anyways :-)

    google-chrome is a binary package, so USE flags won't make any difference
    to its dependencies.


    --
    Neil Bothwick

    We are from the planet Taglinis. Take us to your reader!

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLJ9H8ACgkQ92eFu0QS MJim8hAAgjq11QhhU/24zaRBYcEwYvgAJGzsGsTf8ZgpGslvjA1dGtPCP3RnywuZ UX0SVz1fgXnl5VmRbjhkdSGDGClwXqgAES0fit4ZwY8bT8jy5/MZbYimUGKdi4bn pa+R0sr5iqgexmpkGV2fRNKzBceu7LjhKDNgumxm8SOg73/ayyQlaHZSIfbO7M4/ l+RWflJARTfDzvbd+nkMOLJTaw/y1TtuTKAtzl5Pg0Ks3US+cGsw1xSAZB9KNBUI hgepMa488T+kB6Z7JiOB/m7mbl8B+I7xH3AoiK7EjdRE3FmNcrUfQv201tACPWeG gaWgr3Tj/fCVUAVJtWghIt556dLXR1txMMFc4qcD6AFJTLBIfSk6p870ulHoOnwC Zq8kDotEqjE6kxj/R3G79DKLcvGB00EwzuPsl4FoJRRjdTWhRNI0PpE20MIrWvMv 6+g7p1F7F/FELf8GQr0ba/X5tMcqO9Qwh/hfqqAPBKE9xdHOCqUenlV3UBZbQ3dc 3yiFi+ltPFYss/edYfXfB21T+FMbPejh7wubkE3CH4srk1XwTqjintkyrWHI0mKb Ev2lsWAXqHnH+JVhiRKJ4bUJEYlpAUM9YVXFVU2V63R/mor5PDkNrVOudH7V6ZPU qZ9eoUXH7WPhGAaAeIR0LjNNRC4jLPKvmVGf0qqNSb7u9c+zwdc=
    =XTgS
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)