Issue creating chroot

[ruyrybeyro]

Issue creating chroot

[ruyrybeyro]

Hi, You have root into an error in a previous try. Please run: sudo rm -rf /opt/chroot and do again: vpn.sh -i --vpn=full_DNS_name_of_your_vpn If that doesn't work, please let me know the distribution name and version/commands being used/output/errors. Regards

…

On Fri, 19 Aug 2022 at 12:50, philiasf ***@***.***> wrote: Hi, I'm having an error while running the installation: chroot /opt/chroot unsucessful creation InstallChroot->createChroot: run sudo rm -rf /opt/chroot and do it again I don't know what to do next. Any advice? Thank you!! :) — Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPDBP7XYCGXJUJNM3T4K6DVZ5YIPANCNFSM57AO4KZA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

[philiasf]

Hi,

Yes, I've tried several times to run:

sudo rm -rf /opt/chroot and vpn.sh -i vpn=.....

But no luck.

I'm using Ubuntu LTS 18.04 server and this is the ouput when I run: sudo vpn.sh -i --vpn=full_DNS_name

`
Debian family setup
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:2 http://ppa.launchpad.net/flexiondotorg/audio/ubuntu bionic InRelease
Hit:3 http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic InRelease
Hit:4 http://es.archive.ubuntu.com/ubuntu bionic InRelease
Hit:5 http://ppa.launchpad.net/xubuntu-dev/staging/ubuntu bionic InRelease
Hit:6 http://es.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:7 http://es.archive.ubuntu.com/ubuntu bionic-backports InRelease
Get:8 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [55.2 kB]
Get:9 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [61.1 kB]
Get:10 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2464 B]
Fetched 207 kB in 2s (92.5 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
x11-xserver-utils is already the newest version (7.7+7build1).
jq is already the newest version (1.5+dfsg-2).
ca-certificates is already the newest version (20211016~18.04.1).
curl is already the newest version (7.58.0-2ubuntu3.19).
debootstrap is already the newest version (1.0.95ubuntu0.11).
dpkg is already the newest version (1.19.0.5ubuntu2.4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
resolvconf is already the newest version (1.79ubuntu10.18.04.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
please wait...
slow command, often debootstrap hangs talking with Debian repositories
do ^C and start it over again if needed
I: Retrieving InRelease
I: Checking Release signature
E: Release signed by unknown key (key id xxxxxxxxxx)
chroot /opt/chroot unsucessful creation
InstallChroot->createChroot: run sudo rm -rf /opt/chroot and do it again

`

Thank you!

[ruyrybeyro]

I am not able to replicate your issue with a clean stock Ubuntu 18.04 LTS. For the sake of debugging, would you please confirm if you still have the same error running: sudo debootstrap --no-check-gpg --variant=minbase --arch i386 bullseye /opt/chroot "http://deb.debian.org/debian/"

…

On Fri, 19 Aug 2022 at 13:18, philiasf ***@***.***> wrote: Hi, Yes, I've tried several times to run: sudo rm -rf /opt/chroot and vpn.sh -i vpn=..... But no luck. I'm using Ubuntu LTS 18.04 server and this is the ouput when I run: sudo vpn.sh -i --vpn=full_DNS_name ` Debian family setup Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:2 http://ppa.launchpad.net/flexiondotorg/audio/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic InRelease Hit:4 http://es.archive.ubuntu.com/ubuntu bionic InRelease Hit:5 http://ppa.launchpad.net/xubuntu-dev/staging/ubuntu bionic InRelease Hit:6 http://es.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:7 http://es.archive.ubuntu.com/ubuntu bionic-backports InRelease Get:8 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [55.2 kB] Get:9 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [61.1 kB] Get:10 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2464 B] Fetched 207 kB in 2s (92.5 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done x11-xserver-utils is already the newest version (7.7+7build1). jq is already the newest version (1.5+dfsg-2). ca-certificates is already the newest version (20211016~18.04.1). curl is already the newest version (7.58.0-2ubuntu3.19). debootstrap is already the newest version (1.0.95ubuntu0.11). dpkg is already the newest version (1.19.0.5ubuntu2.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Done Building dependency tree Reading state information... Done resolvconf is already the newest version (1.79ubuntu10.18.04.3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. please wait... slow command, often debootstrap hangs talking with Debian repositories do ^C and start it over again if needed I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id xxxxxxxxxx) chroot /opt/chroot unsucessful creation InstallChroot->createChroot: run sudo rm -rf /opt/chroot and do it again ` Thank you! — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPDBPYCM5VPLMTFLG26N6LVZ53RZANCNFSM57AO4KZA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

[ruyrybeyro]

I am not able to replicate your issue with a clean stock Ubuntu 18.04 LTS.

You seem to have an old debian keyring.

I ended up modifying vpn.sh already with --no-check-pgp, please download it again from https://raw.githubusercontent.com/ruyrybeyro/chrootvpn/main/vpn.sh

[philiasf]

Hi,

I tried that and I got: I: Base system installed successfully.

Then again:

sudo rm -rf /opt/chroot vpn.sh -i --vpn=full_DNS_name_of_your_vpn

Same result: chroot /opt/chroot unsucessful creation

Any ideas?

Thank u!!

[ruyrybeyro]

Launched a new version that should work, ignoring your old Debian keychain. Please run sudo rm -rf /opt/chroot vpn.sh selfupdate vpn.sh -i --vpn=full_DNS_name_of_your_vpn

…

On Fri, 19 Aug 2022 at 15:08, philiasf ***@***.***> wrote: Hi, I tried that and I got: I: Base system installed successfully. Then again: sudo rm -rf /opt/chroot vpn.sh -i --vpn=full_DNS_name_of_your_vpn Same result: chroot /opt/chroot unsucessful creation Any ideas? Thank u!! — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPDBP7KY37KW5NC2R52ISTVZ6IMHANCNFSM57AO4KZA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

[philiasf]

When I run sudo ./vpn.sh selfupdate

I get: main->PreCheck: Run vpn.sh -i --vpn=FQDN or fill in VPN and VPNIP with the DNS FQDN and the IP address of your Checkpoint VPN server

Nothing else happens. And then vpn.sh -i --vpn=full_DNS_name_of_your_vpn and get the same error.

I think the command selfupdate is not working.

Thx!

[ruyrybeyro]

ah, another bug. selfupdate only running after successful setup.

Please download new version from https://raw.githubusercontent.com/ruyrybeyro/chrootvpn/main/vpn.sh

[philiasf]

I'm a bug finder! lol

OK, so now it's installed... but when I access https://localhost:14186/id I get the following:

So I can't accept the certificate :/

Thx!

[ruyrybeyro]

The script installs a global policy for firefox. The browser screen you are showing me means the policy was well installed, is working, so the certificate wont have to be accepted manually. It also means you are ready to authenticate and use the VPN. I already fixed the issues discussed on this thread.

…

On Fri, 19 Aug 2022 at 15:46, philiasf ***@***.***> wrote: I'm a bug finder! lol OK, so now it's installed... but when I access https://localhost:14186/id I get the following: [image: localhost-error] <https://user-images.githubusercontent.com/70553255/185644878-861ec1f4-27df-45a0-9302-ed436df408f1.png> So I can't accept the certificate :/ Thx! — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPDBP3RDRWDRUMNU3XZPETVZ6M5TANCNFSM57AO4KZA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

[philiasf]

OK, so. When I access the Check Point I get this error:

Check Point Deployment Shell internal error

Is it related to the installation or the certificate? thank you!

[ruyrybeyro]

Seems to suggest Java Agent downloaded from the appliance/hw/Checkpoint is corrupted. Try: vpn uninstall vpn -i If it doesn't work, I am afraid the problem is on the VPN side. Regards

…

On Fri, 19 Aug 2022 at 15:54, philiasf ***@***.***> wrote: OK, so. When I access the Check Point I get this error: Check Point Deployment Shell internal error Is it related to the installation or the certificate? thank you! — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPDBP3NCCHR2UA37YXM6KDVZ6N2NANCNFSM57AO4KZA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

[philiasf]

OK, thank you so much for your help!

[ruyrybeyro]

Sorry, forget the .sh Seems to suggest Java Agent downloaded from the appliance/hw/Checkpoint is corrupted. vpn.sh uninstall vpn.sh -i If it doesn't work, I am afraid the problem is on the VPN side.

…

On Fri, 19 Aug 2022 at 15:57, Rui Ribeiro ***@***.***> wrote: Seems to suggest Java Agent downloaded from the appliance/hw/Checkpoint is corrupted. Try: vpn uninstall vpn -i If it doesn't work, I am afraid the problem is on the VPN side. Regards On Fri, 19 Aug 2022 at 15:54, philiasf ***@***.***> wrote: > OK, so. When I access the Check Point I get this error: > > Check Point Deployment Shell internal error > > Is it related to the installation or the certificate? thank you! > > — > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACPDBP3NCCHR2UA37YXM6KDVZ6N2NANCNFSM57AO4KZA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Regards, -- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434

-- Regards,

-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434