hbsd-update - could not get the version number

[vermad...@gmail.com]

Hi,

this is the problem.

root@hbsd:~ # hbsd-update

[*] Could not get the version number

root@hbsd:~ # freebsd-version -k

11.2-PRERELEASE-HBSD

root@hbsd:~ # freebsd-version -u

11.2--HBSD

root@hbsd:~ # sysctl hardening.version
hardening.version: 1100055

Any hints?

[Shawn Webb]

On Mon, Jul 02, 2018 at 04:10:38AM -0700, vermad...@gmail.com wrote:
> Hi,
>
> this is the problem.
>

> root@hbsd:~ # *hbsd-update*

> [*] Could not get the version number
>

> root@hbsd:~ # *freebsd-version -k*
> 11.2-PRERELEASE-HBSD
>
> root@hbsd:~ # *freebsd-version -u*
> 11.2--HBSD
>
> root@hbsd:~ # *sysctl hardening.version*
> hardening.version: 1100055
>
> Any hints?

Hey vermaden,

What happens if you pass the -d option to hbsd-update?

Thanks,

--
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal: +1 443-546-8752
Tor+XMPP+OTR: lat...@is.a.hacker.sx
GPG Key ID: 0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE

[bryn1u85]

Should work with -d option. I had the same problem and -d option has resolved that problem. I asked about the same "issue" Shawn long time ago.

--
You received this message because you are subscribed to the Google Groups "HardenedBSD Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@hardenedbsd.org.

[vermad...@gmail.com]

Now its different:

root@hbsd:~ # hbsd-update -d
/tmp/tmp.SK0aDX17/update.tar                  100% of  300 MB  143 kBps 35m42s
[*] Public key failed to validate.

root@hbsd:~ #

On Monday, July 2, 2018 at 1:46:49 PM UTC+2, Shawn Webb wrote:

On Mon, Jul 02, 2018 at 04:10:38AM -0700, vermaden wrote:
> Hi,
>
> this is the problem.
>
> root@hbsd:~ # *hbsd-update*
> [*] Could not get the version number
>
> root@hbsd:~ # *freebsd-version -k*
> 11.2-PRERELEASE-HBSD
>
> root@hbsd:~ # *freebsd-version -u*
> 11.2--HBSD
>
> root@hbsd:~ # *sysctl hardening.version*
> hardening.version: 1100055
>
> Any hints?

Hey vermaden,

What happens if you pass the -d option to hbsd-update?

Thanks,

--
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:    +1 443-546-8752

Tor+XMPP+OTR:        lattera@

[Shawn Webb]

Is the date/time correct on your system?

By the way, I plan to overhaul bits of hbsd-update to make for more
meaningful error messages. This will be my first priority after this
OpenSSL switch is 100% done.

Tor+XMPP+OTR: lat...@is.a.hacker.sx

[vermad...@gmail.com]

Yes, time/date was wrong, after set right its now this one :)

root@hbsd:~ # hbsd-update -d

/tmp/tmp.NGXqEnNw/update.tar                  100% of  300 MB  539 kBps 09m32s
******************
* IMPORTANT NOTE *
******************

This update includes the PTI patch. Third-party kernel modules (such
as x11/nvidia-driver and hardenedbsd/secadm-kmod) will need to be
recompiled/reinstalled.

If you wish to postpone installing this update, please hit Control-C
within the next ten (10) seconds.
./usr/libexec/dwatch/proc-status: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-exec: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-signal: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-signal-send: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-signal-clear: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-signal-discard: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-exec-failure: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-exit: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-create: Hard-link target './usr/libexec/dwatch/proc' does not exist.
./usr/libexec/dwatch/proc-exec-success: Hard-link target './usr/libexec/dwatch/proc' does not exist.
tar: Error exit delayed from previous errors.
root@hbsd:~ #

On Monday, July 2, 2018 at 11:24:00 PM UTC+2, Shawn Webb wrote:

Is the date/time correct on your system?

By the way, I plan to overhaul bits of hbsd-update to make for more
meaningful error messages. This will be my first priority after this
OpenSSL switch is 100% done.

[bryn1u85]

Vermaden,
This is known problem. Here should be solution: https://groups.google.com/a/hardenedbsd.org/forum/#!forum/users
You need to review.

--

[bsd...@gmail.com]

Tried to follow the directions that I posted for working in current on a new stable build has resulted in the same error still. Tried deleting the directory entirely and that didn't work. Also moved the dwatch directory out of /tmp/tmp.<randstring>/usr/libexec into my /usr/libexec and that didn't help either. 

[Shawn Webb]

Looping in Devine Teske again. I think I'm going to disable the dwatch
build entirely until we figure out what's causing tar to become
confused.

On Tue, Jul 03, 2018 at 01:11:31PM -0700, bsd...@gmail.com wrote:
> Tried to follow the directions that I posted for working in current on a
> new stable build has resulted in the same error still. Tried deleting the
> directory entirely and that didn't work. Also moved the dwatch directory
> out of /tmp/tmp.<randstring>/usr/libexec into my /usr/libexec and that
> didn't help either.
>
> On Tuesday, July 3, 2018 at 11:02:55 AM UTC-5, bryn1u wrote:
> >
> > Vermaden,
> > This is known problem. Here should be solution:
> > https://groups.google.com/a/hardenedbsd.org/forum/#!forum/users
> > You need to review.
> >

> > wt., 3 lip 2018 o 17:58 <vermad...@gmail.com <javascript:>> napisa??(a):

> >> email to users+un...@hardenedbsd.org <javascript:>.

> >>
> >
>


--
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal: +1 443-546-8752

Tor+XMPP+OTR: lat...@is.a.hacker.sx

[Shawn Webb]

I think I see what's going on. I'm not invoking mtree prior to
untarring the base.txz distset. tar is getting confused because
/usr/libexec/dwatch doesn't exist, yet.

What I need to do is integrate mtree support into hbsd-update-build
and hbsd-update. I'll do that soon.

Thanks,

--
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal: +1 443-546-8752

Tor+XMPP+OTR: lat...@is.a.hacker.sx
GPG Key ID: 0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE

[Devin Teske]

Here's the specific invocation that FreeBSD release engineering has been using for decades:

mtree -eU -f repos/distname.mtree -p destdir

For example:

mtree -eU -f base.mtree -p /

--
Devin

[vermad...@gmail.com]

I have solved it this way:

root@hbsd:~ # ls -l /usr/libexec/dwatch/proc*

ls: No match.

root@hbsd:~ # touch /usr/libexec/dwatch/proc-status
root@hbsd:~ # touch /usr/libexec/dwatch/proc-exec
root@hbsd:~ # touch /usr/libexec/dwatch/proc-signal
root@hbsd:~ # touch /usr/libexec/dwatch/proc-signal-send
root@hbsd:~ # touch /usr/libexec/dwatch/proc-signal-clear
root@hbsd:~ # touch /usr/libexec/dwatch/proc-signal-discard
root@hbsd:~ # touch /usr/libexec/dwatch/proc-exec-failure
root@hbsd:~ # touch /usr/libexec/dwatch/proc-exit
root@hbsd:~ # touch /usr/libexec/dwatch/proc-create
root@hbsd:~ # touch /usr/libexec/dwatch/proc-exec-success

root@hbsd:~ # ls -l /usr/libexec/dwatch/proc*
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-create
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-exec
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-exec-failure
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-exec-success
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-exit
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-signal
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-signal-clear
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-signal-discard
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-signal-send
-rw-r--r--  1 root  wheel  0 Jul  4 10:57 /usr/libexec/dwatch/proc-status

root@hbsd:~ # hbsd-update -d

(this time worked)

Thanks for help.

Regards,

vermaden

[Franco Fichtner]

Hi,

It doesn't seem to be an mtree issue at all...

https://github.com/libarchive/libarchive/issues/1071


Cheers,
Franco