[NEW] security/plaso

[Remi Pointel]

Hi,

log2timeline is a tool designed to extract timestamps from various files 
found on a typical computer system(s) and aggregate them.
The initial purpose of plaso was to collect all timestamped events of 
interest on a computer system and have them aggregated in a single place 
for computer forensic analysis (aka Super Timeline).


Ok to import?

Cheers,

Remi.


plaso-1.5.1.tar.gz
Description: application/gzip

Re: [UPDATE] devel/py-construct

[Remi Pointel]

On 01/19/17 01:51, Antoine Jacoutot wrote:

On Wed, Jan 18, 2017 at 09:51:03PM +0100, Remi Pointel wrote:

Hi,

Plaso needs py-construct 2.5.3. As construct is not a dependency for a port
(not yet), we could downgrade it.


Is the explicit version a hard requirement for Plaso?
If so then I suppose downgrading would be OK (disclaimer, I don't use this) but
you need to add a comment so that people don't randomly update this...



Yes, it's a hard requirement for Plaso 
(https://github.com/log2timeline/plaso/blob/master/requirements.txt): 
construct >= 2.5.2,<= 2.5.3.


Remi.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 21:28:47

Modified files:
print/cups-filters: Makefile distinfo 
print/cups-filters/pkg: PLIST 

Log message:
Update to cups-filters-1.13.3.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 20:29:05

Modified files:
sysutils/google-cloud-sdk: Makefile distinfo 
sysutils/google-cloud-sdk/pkg: PLIST 

Log message:
Update to google-cloud-sdk-140.0.0.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 20:28:28

Modified files:
net/py-botocore: Makefile distinfo 

Log message:
Update to py-botocore-1.5.2.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 20:28:40

Modified files:
sysutils/awscli: Makefile distinfo 

Log message:
Update to awscli-1.11.39.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 20:24:16

Modified files:
security/libgcrypt: Makefile distinfo 

Log message:
Update to libgcrypt-1.7.6.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 20:08:52

Modified files:
print/cups : Makefile distinfo 
print/cups/patches: patch-backend_ipp_c 
patch-config-scripts_cups-common_m4 

Log message:
Update to cups-2.2.2.

Re: 10GB zipfile

[Juan Francisco Cantero Hurtado]

On Wed, Jan 18, 2017 at 06:33:17PM +0100, Jan Stary wrote:
> I have a big zipfile that I am trying to unzip witn archivers/unzip.
> 
> $ unzip -ql file.zip 
> warning [file.zip]:  6682546438 extra bytes at beginning or within
> zipfile (attempting to process anyway)
>   error [file.zip]:  start of central directory not found; zipfile corrupt.
> 
> $ ls -l file.zip
> -rw-r--r--  1 hans  hans  10977521995 Jan 18 18:24 file.zip
> 
> I am pretty sure the zipfile is OK. Given that the fie size
> minus the "extra bytes" is very near 4GB, could this be
> a 4GB file-size problem? If so, would people please recommend
> an unzipper which can go beyond 4GB?

Maybe this command?

python3.6 -m zipfile -e bigfile.zip output/

I don't have a big file to test the command.

-- 
Juan Francisco Cantero Hurtado http://juanfra.info

Re: [UPDATE] devel/py-construct

[Antoine Jacoutot]

On Wed, Jan 18, 2017 at 09:51:03PM +0100, Remi Pointel wrote:
> Hi,
> 
> Plaso needs py-construct 2.5.3. As construct is not a dependency for a port
> (not yet), we could downgrade it.

Is the explicit version a hard requirement for Plaso?
If so then I suppose downgrading would be OK (disclaimer, I don't use this) but
you need to add a comment so that people don't randomly update this...


> Ok for this diff?
> 
> Cheers,
> 
> Remi.

> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/py-construct/Makefile,v
> retrieving revision 1.2
> diff -u -p -u -p -r1.2 Makefile
> --- Makefile  3 Jan 2017 19:19:48 -   1.2
> +++ Makefile  18 Jan 2017 20:48:52 -
> @@ -2,10 +2,10 @@
>  
>  COMMENT =powerful declarative parser/builder for binary data
>  
> -MODPY_EGG_VERSION = 2.8.5
> +EPOCH =  0
> +MODPY_EGG_VERSION = 2.5.3
>  DISTNAME =   construct-${MODPY_EGG_VERSION}
>  PKGNAME =py-${DISTNAME}
> -REVISION =   0
>  
>  CATEGORIES = devel
>  
> Index: distinfo
> ===
> RCS file: /cvs/ports/devel/py-construct/distinfo,v
> retrieving revision 1.1.1.1
> diff -u -p -u -p -r1.1.1.1 distinfo
> --- distinfo  4 Oct 2016 19:34:44 -   1.1.1.1
> +++ distinfo  18 Jan 2017 20:48:52 -
> @@ -1,2 +1,2 @@
> -SHA256 (construct-2.8.5.tar.gz) = 
> DsBZOQuWpL4nu5ECwc5jLOyHWKB11hMzMrRxg2DCgrE=
> -SIZE (construct-2.8.5.tar.gz) = 696415
> +SHA256 (construct-2.5.3.tar.gz) = 
> siM7x8ak1zgD9YBrwxZ+STXao+qKXNBWy6u9ucPXmjY=
> +SIZE (construct-2.5.3.tar.gz) = 688072
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/devel/py-construct/pkg/PLIST,v
> retrieving revision 1.1.1.1
> diff -u -p -u -p -r1.1.1.1 PLIST
> --- pkg/PLIST 4 Oct 2016 19:34:44 -   1.1.1.1
> +++ pkg/PLIST 18 Jan 2017 20:48:52 -
> @@ -4,68 +4,63 @@ lib/python${MODPY_VERSION}/site-packages
>  
> lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
>  
> lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/SOURCES.txt
>  
> lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/dependency_links.txt
> +lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt
>  
> lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt
>  lib/python${MODPY_VERSION}/site-packages/construct/__init__.py
>  
> ${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}/
>  
> lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
> +lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}adapters.${MODPY_PYC_MAGIC_TAG}pyc
>  
> lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}core.${MODPY_PYC_MAGIC_TAG}pyc
>  
> lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}debug.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}expr.${MODPY_PYC_MAGIC_TAG}pyc
> +lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}macros.${MODPY_PYC_MAGIC_TAG}pyc
>  
> lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}version.${MODPY_PYC_MAGIC_TAG}pyc
> +lib/python${MODPY_VERSION}/site-packages/construct/adapters.py
>  lib/python${MODPY_VERSION}/site-packages/construct/core.py
>  lib/python${MODPY_VERSION}/site-packages/construct/debug.py
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/__init__.py
> -${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/${MODPY_PYCACHE}/
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/__init__.py
> -${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}/
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}cap.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}snoop.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/cap.py
> -lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/snoop.py
> 

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:31:42

Modified files:
multimedia/xine-lib: Makefile 
Added files:
multimedia/xine-lib/patches: patch-src_xine-utils_memcpy_c 

Log message:
memcpy: fix segfault in times(NULL).

from Brad (maintainer)

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:25:00

Modified files:
security/libtasn1: Makefile distinfo 
Removed files:
security/libtasn1/patches: patch-configure_ac 

Log message:
Update to libtasn1-4.10.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:21:12

Modified files:
sysutils/awscli: Makefile distinfo 

Log message:
Update to awscli-1.11.38.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:20:23

Modified files:
net/py-botocore: Makefile distinfo 

Log message:
Update to py-botocore-1.5.1.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:16:19

Modified files:
x11/gnome/py-atspi: Makefile distinfo 
x11/gnome/py-atspi/pkg: PLIST 

Log message:
Update to py3-atspi-2.20.3.

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2017/01/18 17:09:54

Modified files:
www/webkitgtk4 : Makefile distinfo 

Log message:
SECURITY update to webkitgtk4-2.14.3.
CVE-2016-7656, CVE-2016-7635, CVE-2016-7654, CVE-2016-7639, CVE-2016-7645,
CVE-2016-7652, CVE-2016-7641, CVE-2016-7632, CVE-2016-7599, CVE-2016-7592,
CVE-2016-7589, CVE-2016-7623, CVE-2016-7586

CVS: cvs.openbsd.org: ports

[Christian Weisgerber]

CVSROOT:/cvs
Module name:ports
Changes by: na...@cvs.openbsd.org   2017/01/18 16:10:42

Modified files:
shells/yash: Makefile distinfo 
shells/yash/patches: patch-variable_c 
shells/yash/pkg: PLIST 

Log message:
update to 2.44 for various fixes and better POSIX compliance

CVS: cvs.openbsd.org: ports

[Christian Weisgerber]

CVSROOT:/cvs
Module name:ports
Changes by: na...@cvs.openbsd.org   2017/01/18 15:12:32

Modified files:
graphics/png   : Makefile distinfo 

Log message:
maintenance update to 1.6.28; from Brad

CVS: cvs.openbsd.org: ports

[Christian Weisgerber]

CVSROOT:/cvs
Module name:ports
Changes by: na...@cvs.openbsd.org   2017/01/18 14:28:35

Modified files:
archivers/xz   : Makefile distinfo 
archivers/xz/patches: patch-config_h_in 

Log message:
maintenance update to 5.2.3

[NEW] devel/py-hachoir-{core,metadata,parser}

[Remi Pointel]

Hi,

attached are the following ports (needed for Plaso):
- hachoir-core
- hachoir-metadata
- hachoir-parser

Ok?

Cheers,

Remi.


py-hachoir-core_metadata_parser.tar.gz
Description: application/gzip

[NEW] security/py-dfwinreg

[Remi Pointel]

Hi,

attached is dfwinreg: Digital Forensics Windows Registry, provides 
read-only access to Windows Registry objects. It's needed for Plaso.


Ok?

Cheers,

Remi.


py-dfwinreg-20160428.tar.gz
Description: application/gzip

[NEW] security/py-dfvfs

[Remi Pointel]

Hi,

attached is dfvfs: dfVFS, or Digital Forensics Virtual File System, 
provides read-only access to file-system objects from various storage 
media types and file formats. It is needed for Plaso.


Ok ?

Cheers,

Remi.


py-dfvfs-20160918.tar.fz
Description: Binary data

[UPDATE] devel/py-construct

[Remi Pointel]

Hi,

Plaso needs py-construct 2.5.3. As construct is not a dependency for a 
port (not yet), we could downgrade it.


Ok for this diff?

Cheers,

Remi.
Index: Makefile
===
RCS file: /cvs/ports/devel/py-construct/Makefile,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 Makefile
--- Makefile	3 Jan 2017 19:19:48 -	1.2
+++ Makefile	18 Jan 2017 20:48:52 -
@@ -2,10 +2,10 @@
 
 COMMENT =	powerful declarative parser/builder for binary data
 
-MODPY_EGG_VERSION = 2.8.5
+EPOCH =		0
+MODPY_EGG_VERSION = 2.5.3
 DISTNAME =	construct-${MODPY_EGG_VERSION}
 PKGNAME =	py-${DISTNAME}
-REVISION =	0
 
 CATEGORIES =	devel
 
Index: distinfo
===
RCS file: /cvs/ports/devel/py-construct/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 distinfo
--- distinfo	4 Oct 2016 19:34:44 -	1.1.1.1
+++ distinfo	18 Jan 2017 20:48:52 -
@@ -1,2 +1,2 @@
-SHA256 (construct-2.8.5.tar.gz) = DsBZOQuWpL4nu5ECwc5jLOyHWKB11hMzMrRxg2DCgrE=
-SIZE (construct-2.8.5.tar.gz) = 696415
+SHA256 (construct-2.5.3.tar.gz) = siM7x8ak1zgD9YBrwxZ+STXao+qKXNBWy6u9ucPXmjY=
+SIZE (construct-2.5.3.tar.gz) = 688072
Index: pkg/PLIST
===
RCS file: /cvs/ports/devel/py-construct/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -u -p -u -p -r1.1.1.1 PLIST
--- pkg/PLIST	4 Oct 2016 19:34:44 -	1.1.1.1
+++ pkg/PLIST	18 Jan 2017 20:48:52 -
@@ -4,68 +4,63 @@ lib/python${MODPY_VERSION}/site-packages
 lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
 lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/SOURCES.txt
 lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/dependency_links.txt
+lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt
 lib/python${MODPY_VERSION}/site-packages/construct-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt
 lib/python${MODPY_VERSION}/site-packages/construct/__init__.py
 ${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}/
 lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}adapters.${MODPY_PYC_MAGIC_TAG}pyc
 lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}core.${MODPY_PYC_MAGIC_TAG}pyc
 lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}debug.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}expr.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}macros.${MODPY_PYC_MAGIC_TAG}pyc
 lib/python${MODPY_VERSION}/site-packages/construct/${MODPY_PYCACHE}version.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/construct/adapters.py
 lib/python${MODPY_VERSION}/site-packages/construct/core.py
 lib/python${MODPY_VERSION}/site-packages/construct/debug.py
-lib/python${MODPY_VERSION}/site-packages/construct/examples/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/__init__.py
-${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/${MODPY_PYCACHE}/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/__init__.py
-${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}cap.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/${MODPY_PYCACHE}snoop.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/cap.py
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/data/snoop.py
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/executable/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/executable/__init__.py
-${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/executable/${MODPY_PYCACHE}/
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/executable/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/construct/examples/formats/executable/${MODPY_PYCACHE}elf32.${MODPY_PYC_MAGIC_TAG}pyc

[NEW] devel/libvslvm

[Remi Pointel]

Hi,

attached is libvslvm: library and tools to access the Linux Logical 
Volume Manager (LVM) volume system format, needed for Plaso.


Ok?

Cheers,

Remi.


libvslvm-20160110.tar.gz
Description: application/gzip

[NEW] devel/libsigscan

[Remi Pointel]

Hi,

attached is libsigscan: library for binary signature scanning, needed 
for Plaso.


Ok?

Cheers,

Remi.


libsigscan-20160312.tar.gz
Description: application/gzip

[NEW] devel/libvshadow

[Remi Pointel]

Hi,

attached is libvshadow: library and tools to access the Volume Shadow 
Snapshot (VSS) format, needed for Plaso.


Ok?

Cheers,

Remi.


libvshadow-2016.tar.gz
Description: application/gzip

[NEW] devel/libvmdk

[Remi Pointel]

Hi,

attached is libvmdk: library and tools to access the VMware Virtual Disk 
(VMDK) format, needed for Plaso.


Ok?

Cheers,

Remi.


libvmdk-20160119.tar.gz
Description: application/gzip

[NEW] devel/libesedb

[Remi Pointel]

Hi,

attached is libesedb: library and tools to access the Extensible Storage 
Engine (ESE) Database File (EDB) format, needed for Plaso.


Ok?

Cheers,

Remi.


libesedb-20160622.tar.gz
Description: application/gzip

[NEW] devel/libvhdi

[Remi Pointel]

Hi,

attached is libvhdi: library and tools to access the Virtual Hard Disk 
(VHD) image format, needed for Plaso.


Ok?

Cheers,

Remi.


libvhdi-20160424.tar.gz
Description: application/gzip

[NEW] devel/libsmraw

[Remi Pointel]

Hi,

attached is libsmraw: library and tools to access the (split) RAW image 
format, needed for Plaso.


Ok?

Cheers,

Remi.


libsmraw-20160424.tar.gz
Description: application/gzip

[NEW] devel/libsmdev

[Remi Pointel]

Hi,

attached is libsmdev: library to access to storage media devices, needed 
for Plaso.


Ok?

Cheers,

Remi.


libsmdev-20160320.tar.gz
Description: application/gzip

[NEW] devel/libscca

[Remi Pointel]

Hi,

attached is libscca: library and tools to access the Windows Prefetch 
File (SCCA) format, needed for Plaso.


Ok?

Cheers,

Remi.


libscca-20170105.tar.gz
Description: application/gzip

[NEW] devel/libregf

[Remi Pointel]

Hi,

attached is libregf: library and tools to access the Windows NT Registry 
File (REGF) format, needed for Plaso.


Ok?

Cheers,

Remi.


libregf-20160424.tar.gz
Description: application/gzip

[NEW] devel/libqcow

[Remi Pointel]

Hi,

attached is libqcow: library and tools to access the QEMU Copy-On-Write 
(QCOW) image format, needed for Plaso.


Ok?

Cheers,

Remi.


libqcow-20160123.tar.gz
Description: application/gzip

[NEW] devel/libolecf

[Remi Pointel]

Hi,

attached is libolecf: library and tools to access the OLE 2 Compound 
File (OLECF) format, needed for Plaso.


Ok?

Cheers,

Remi.


libolecf-20161113.tar.gz
Description: application/gzip

[NEW] devel/liblnk

[Remi Pointel]

Hi,

attached is liblnk: library and tools to access the Windows Shortcut 
File (LNK) format, needed for Plaso.


Ok?

Cheers,

Remi.


liblnk-20170111.tar.gz
Description: application/gzip

[NEW] devel/libmsiecf

[Remi Pointel]

Hi,

attached is libmsiecf: library and tools to access the Microsoft 
Internet Explorer (MSIE) Cache File (index.dat) files, needed for Plaso.


Ok?

Cheers,

Remi.


libmsiecf-20160904.tar.gz
Description: application/gzip

[NEW] devel/libfwsi

[Remi Pointel]

Hi,

attached is libfwsi: a library to access the Windows Shell Item format, 
needed for Plaso.


Ok?

Cheers,

Remi.


libfwsi-20160110.tar.gz
Description: application/gzip

Re: [NEW] devel/libfvde

[Remi Pointel]

On 01/18/17 20:56, Remi Pointel wrote:

Hi,

attached is libfvde: a library and tools to access FileVault Drive
Encryption (FVDE) encrypted volumes, needed for Plaso.

Ok?

Cheers,

Remi.


with the correct tarball...


libfvde-20160918.tar.gz
Description: application/gzip

[NEW] devel/libfvde

[Remi Pointel]

Hi,

attached is libfvde: a library and tools to access FileVault Drive 
Encryption (FVDE) encrypted volumes, needed for Plaso.


Ok?

Cheers,

Remi.


libfvde-20160918.tar.gz
Description: application/gzip

[NEW] devel/libfwnt

[Remi Pointel]

Hi,

attached is port of libfwnt: a library for Windows NT data types, needed 
for Plaso.


Ok?

Cheers,

Remi.


libfwnt-20161103.tar.gz
Description: application/gzip

[NEW] devel/libfsntfs

[Remi Pointel]

Hi,

attached is libfsntfs: library and tools to access the New Technology 
File System (NTFS), needed for Plaso.


Ok?

Cheers,

Remi.


libfsntfs-20160418.tar.gz
Description: application/gzip

[NEW] security/libbde

[Remi Pointel]

Hi,

attached is the libbde port: library and tools to access the BitLocker 
Drive Encryption (BDE) encrypted volumes, needed for Plaso.


Ok?

Cheers,

Remi.


libbde-20160731.tar.gz
Description: application/gzip

Re: 10GB zipfile

[Jan Vlach]

Hi Jan,

I believe 7z (p7zip package) can uncompress *zip files too. Give it a
shot.

Jan

On Wed, Jan 18, 2017 at 06:33:17PM +0100, Jan Stary wrote:
> I have a big zipfile that I am trying to unzip witn archivers/unzip.
> 
> $ unzip -ql file.zip 
> warning [file.zip]:  6682546438 extra bytes at beginning or within
> zipfile (attempting to process anyway)
>   error [file.zip]:  start of central directory not found; zipfile corrupt.
> 
> $ ls -l file.zip
> -rw-r--r--  1 hans  hans  10977521995 Jan 18 18:24 file.zip
> 
> I am pretty sure the zipfile is OK. Given that the fie size
> minus the "extra bytes" is very near 4GB, could this be
> a 4GB file-size problem? If so, would people please recommend
> an unzipper which can go beyond 4GB?
> 
>   Thank you
> 
>   Jan

10GB zipfile

[Jan Stary]

I have a big zipfile that I am trying to unzip witn archivers/unzip.

$ unzip -ql file.zip 
warning [file.zip]:  6682546438 extra bytes at beginning or within
zipfile (attempting to process anyway)
  error [file.zip]:  start of central directory not found; zipfile corrupt.

$ ls -l file.zip
-rw-r--r--  1 hans  hans  10977521995 Jan 18 18:24 file.zip

I am pretty sure the zipfile is OK. Given that the fie size
minus the "extra bytes" is very near 4GB, could this be
a 4GB file-size problem? If so, would people please recommend
an unzipper which can go beyond 4GB?

Thank you

Jan

Re: Help to port missing PHP extensions required for running Laravel

[Erling Westenvik]

On Wed, Jan 18, 2017 at 02:49:36PM +0100, Otto Moerbeek wrote:
> On Wed, Jan 18, 2017 at 02:34:57PM +0100, Erling Westenvik wrote:
> 
> > Hi,
> > A customer require a PHP project to be developed using the Laravel
> > framework. According to their home page, Laravel requires:
> > 
> > - OpenSSL PHP Extension
> > - PDO PHP Extension
> > - Mbstring PHP Extension
> > - Tokenizer PHP Extension
> > - XML PHP Extension
> > 
> > AFAIK, only the PDO Extension is available for PHP in OpenBSD as for now.
> > 
> > I'd prefer to do the development using my OpenBSD machines. The
> > alternatives are rather depressing:
> > 
> > - either set up a dedicated Linux machine, or
> > - try running a Linux VM in QEMU
> > 
> > My question:
> > 
> > Would it be easy for me to create ports for the extensions above? And if
> > so, if someone would be kind enough to point me in the right direction?
> > 
> > I'm running amd64-current on both my primary workstation and on my laptop.
> > 
> > Thanks in advance for any help.
> > 
> > Erling
> > 
> > -- 
> > Erling Westenvik
> 
> No work needed. The mentioned extensions are already buit-in and thus
> available. Check phpinfo() output.

Thanks! I didn't bother checking phpinfo(). Made my assumption based on
the package list in pkg_mgr.

*is putting on Jarre's "The Heart of Noise" (2016) and attempts to
pretend like nothing...*

Erling

Re: Help to port missing PHP extensions required for running Laravel

[Erling Westenvik]

On Wed, Jan 18, 2017 at 01:46:53PM +, Pedro de Oliveira wrote:
> I run a laravel site on my OpenBSD server, everything works correctly.

Nice. The Laravel home page states that PHP > 5.6.4 is required for
Laravel 5.3. The latest PHP < 7 for OpenBSD seem to be 5.6.29. Which
versions of Laravel and PHP are you running?

(I installed PHP 7 from packages yesterday.)

Erling
 
> On Wed, Jan 18, 2017 at 1:34 PM, Erling Westenvik <
> erling.westen...@gmail.com> wrote:
> 
> > Hi,
> > A customer require a PHP project to be developed using the Laravel
> > framework. According to their home page, Laravel requires:
> >
> > - OpenSSL PHP Extension
> > - PDO PHP Extension
> > - Mbstring PHP Extension
> > - Tokenizer PHP Extension
> > - XML PHP Extension
> >
> > AFAIK, only the PDO Extension is available for PHP in OpenBSD as for now.
> >
> > I'd prefer to do the development using my OpenBSD machines. The
> > alternatives are rather depressing:
> >
> > - either set up a dedicated Linux machine, or
> > - try running a Linux VM in QEMU
> >
> > My question:
> >
> > Would it be easy for me to create ports for the extensions above? And if
> > so, if someone would be kind enough to point me in the right direction?
> >
> > I'm running amd64-current on both my primary workstation and on my laptop.
> >
> > Thanks in advance for any help.
> >
> > Erling
> >
> > --
> > Erling Westenvik

CVS: cvs.openbsd.org: ports

[James Turner]

CVSROOT:/cvs
Module name:ports
Changes by: jtur...@cvs.openbsd.org 2017/01/18 07:08:59

Modified files:
devel/fossil   : Makefile distinfo 

Log message:
Update fossil to 1.37.

Changelog online: 
http://fossil-scm.org/index.html/doc/trunk/www/changes.wiki#v1_37

powerpc bulk build report

[landry]

bulk build on macppc-1.ports.openbsd.org
started on  Thu Jan 5 11:18:31 MST 2017
finished at Wed Jan 18 07:06:46 MST 2017
lasted 13D12h48m
done with kern.version=OpenBSD 6.0-current (GENERIC.MP) #56: Wed Jan  4 
17:28:32 MST 2017

built packages:7817
Jan 5:478
Jan 6:486
Jan 7:480
Jan 8:412
Jan 9:368
Jan 10:331
Jan 11:400
Jan 12:360
Jan 13:397
Jan 14:377
Jan 15:527
Jan 16:435
Jan 17:1019
Jan 18:1746



build failures: 6
http://build-failures.rhaalovely.net//powerpc/2017-01-05/devel/cargo.log
http://build-failures.rhaalovely.net//powerpc/2017-01-05/devel/llvm.log
http://build-failures.rhaalovely.net//powerpc/2017-01-05/devel/reposurgeon.log
http://build-failures.rhaalovely.net//powerpc/2017-01-05/devel/xulrunner/24.log
http://build-failures.rhaalovely.net//powerpc/2017-01-05/lang/guile2.log
http://build-failures.rhaalovely.net//powerpc/2017-01-05/lang/rust,-doc.log

recurrent failures
 failures/devel/llvm.log
 failures/devel/reposurgeon.log
 failures/lang/guile2.log
new failures
+++ ls-failures Wed Jan 18 07:07:14 2017
+failures/devel/cargo.log
+failures/devel/xulrunner/24.log
+failures/lang/rust,-doc.log
resolved failures
--- ../old/powerpc/last//ls-failuresFri Dec 16 12:02:08 2016
-failures/audio/moc.log
-failures/graphics/tesseract/tessdata,-afr.log
-failures/lang/node.log
-failures/math/py-bottleneck.log
Base libs:
curses.14.0 edit.5.2 event.4.1 expat.11.0 form.6.0 formw.6.0 fuse.1.1
iberty.12.0 menu.6.0 menuw.6.0 ncurses.14.0 ncursesw.14.0 objc.6.0
ossaudio.4.0 panel.6.0 panelw.6.0 perl.17.1 readline.4.0 rpcsvc.2.0
skey.6.0 radius.1.0 sndio.6.1 stdc++.57.0 termcap.14.0 .14.0 z.5.0
usbhid.7.0 util.12.1 pthread.23.0 c.89.2 c.89.2.a kvm.16.2 m.10.0
pcap.8.3 crypto.41.0 ssl.42.0 tls.14.0

X libs:
FS.10.0 GLESv1_CM.1.0 GLU.9.0 GLw.6.0 ICE.10.0 SM.9.0 X11-xcb.2.0
X11.16.1 XRes.5.0 Xau.10.0 Xaw.15.0 Xaw7.15.0 Xcomposite.4.0 Xcursor.5.0
Xdamage.4.0 Xdmcp.11.0 Xext.13.0 Xfixes.6.0 Xfontcache.5.0 Xi.12.1
Xinerama.6.0 Xmu.11.0 Xmuu.6.0 Xpm.9.0 Xrender.6.0 Xss.6.0 Xt.11.0
Xtst.11.0 Xv.6.0 XvMC.6.0 XvMCW.2.0 Xxf86dga.6.0 dmx.2.0 Xxf86misc.6.0
Xxf86vm.6.0 fontenc.4.0 epoxy.2.0 pciaccess.2.0 pixman-1.32.6
pthread-stubs.2.0 txc_dxtn.0.0 xcb-composite.1.0 xcb-damage.1.0
xcb-dpms.1.0 xcb-dri2.1.1 xcb-dri3.0.0 xcb-ewmh.2.0 xcb-cursor.0.0
xcb-icccm.4.0 xcb-image.2.0 xcb-res.1.1 xcb-keysyms.3.0 xkbui.5.0
xcb-shm.1.1 xcb-xevie.1.0 xcb-xf86dri.2.0 xcb-util.0.0 xcb-xinerama.1.0
xcb-xtest.1.0 xcb-xvmc.1.0 xkbfile.6.0 Xrandr.7.1 XvMCr600.1.0
xcb-render-util.2.0 drm_nouveau.3.0 drm_radeon.4.0 Xfont.13.0 Xft.10.0
glapi.0.2 fontconfig.11.0 xcb-glx.1.1 xcb-randr.2.2 xcb-present.0.1
xcb-record.1.1 xcb-render.1.1 xcb-screensaver.1.1 xcb-shape.1.1
xcb-sync.1.2 xcb-xfixes.1.2 xcb-xkb.0.1 xcb-xprint.3.0 xcb-xv.1.1
xcb.4.0 freetype.27.0 xcb-xrm.0.0 drm.7.3 EGL.1.1 drm_amdgpu.1.2 GL.17.1
GLESv2.1.2 OSMesa.10.1 gbm.0.1

Re: Help to port missing PHP extensions required for running Laravel

[Otto Moerbeek]

On Wed, Jan 18, 2017 at 02:34:57PM +0100, Erling Westenvik wrote:

> Hi,
> A customer require a PHP project to be developed using the Laravel
> framework. According to their home page, Laravel requires:
> 
> - OpenSSL PHP Extension
> - PDO PHP Extension
> - Mbstring PHP Extension
> - Tokenizer PHP Extension
> - XML PHP Extension
> 
> AFAIK, only the PDO Extension is available for PHP in OpenBSD as for now.
> 
> I'd prefer to do the development using my OpenBSD machines. The
> alternatives are rather depressing:
> 
> - either set up a dedicated Linux machine, or
> - try running a Linux VM in QEMU
> 
> My question:
> 
> Would it be easy for me to create ports for the extensions above? And if
> so, if someone would be kind enough to point me in the right direction?
> 
> I'm running amd64-current on both my primary workstation and on my laptop.
> 
> Thanks in advance for any help.
> 
> Erling
> 
> -- 
> Erling Westenvik

No work needed. The mentioned extensions are already buit-in and thus
available. Check phpinfo() output.

-Otto

Re: Help to port missing PHP extensions required for running Laravel

[Pedro de Oliveira]

I run a laravel site on my OpenBSD server, everything works correctly.

On Wed, Jan 18, 2017 at 1:34 PM, Erling Westenvik <
erling.westen...@gmail.com> wrote:

> Hi,
> A customer require a PHP project to be developed using the Laravel
> framework. According to their home page, Laravel requires:
>
> - OpenSSL PHP Extension
> - PDO PHP Extension
> - Mbstring PHP Extension
> - Tokenizer PHP Extension
> - XML PHP Extension
>
> AFAIK, only the PDO Extension is available for PHP in OpenBSD as for now.
>
> I'd prefer to do the development using my OpenBSD machines. The
> alternatives are rather depressing:
>
> - either set up a dedicated Linux machine, or
> - try running a Linux VM in QEMU
>
> My question:
>
> Would it be easy for me to create ports for the extensions above? And if
> so, if someone would be kind enough to point me in the right direction?
>
> I'm running amd64-current on both my primary workstation and on my laptop.
>
> Thanks in advance for any help.
>
> Erling
>
> --
> Erling Westenvik
>
>

CVS: cvs.openbsd.org: ports

[Gonzalo L . Rodriguez]

CVSROOT:/cvs
Module name:ports
Changes by: gonz...@cvs.openbsd.org 2017/01/18 06:43:46

Modified files:
www/varnish: Makefile 

Log message:
Fix Makefile

Help to port missing PHP extensions required for running Laravel

[Erling Westenvik]

Hi,
A customer require a PHP project to be developed using the Laravel
framework. According to their home page, Laravel requires:

- OpenSSL PHP Extension
- PDO PHP Extension
- Mbstring PHP Extension
- Tokenizer PHP Extension
- XML PHP Extension

AFAIK, only the PDO Extension is available for PHP in OpenBSD as for now.

I'd prefer to do the development using my OpenBSD machines. The
alternatives are rather depressing:

- either set up a dedicated Linux machine, or
- try running a Linux VM in QEMU

My question:

Would it be easy for me to create ports for the extensions above? And if
so, if someone would be kind enough to point me in the right direction?

I'm running amd64-current on both my primary workstation and on my laptop.

Thanks in advance for any help.

Erling

-- 
Erling Westenvik

CVS: cvs.openbsd.org: ports

[Dmitrij Czarkoff]

CVSROOT:/cvs
Module name:ports
Changes by: czark...@cvs.openbsd.org2017/01/18 05:43:32

Modified files:
mail/s-nail: Makefile distinfo 

Log message:
Update to s-nail 14.8.15.

While at it, fix homepage.

CVS: cvs.openbsd.org: ports

[Dmitrij Czarkoff]

CVSROOT:/cvs
Module name:ports
Changes by: czark...@cvs.openbsd.org2017/01/18 05:42:28

Modified files:
devel/py-gevent: Makefile 
Added files:
devel/py-gevent/patches: patch-setup_py 

Log message:
This patch should have been included in previous commit.

Re: CVS: cvs.openbsd.org: ports

[Gonzalo L. Rodriguez]

Whoops, fix this in a while, sorry

Sent from my toaster...

> El 17 ene. 2017, a las 18:29, Landry Breuil  escribió:
>
>> On Tue, Jan 17, 2017 at 07:04:15AM -0700, Gonzalo L. Rodriguez wrote:
>> CVSROOT:/cvs
>> Module name:ports
>> Changes by:gonz...@cvs.openbsd.org2017/01/17 07:04:15
>>
>> Modified files:
>>www/varnish: distinfo
>>www/varnish/pkg: MESSAGE PLIST
>
> Seems you forgot to commit the Makefile part, fails in bulks :)

Re: [NEW PORT: audio/rubberband]

[Tobias Brodel]

hi stuart, thanks for your response.

On 01/17/17 23:10, Stuart Henderson wrote:

Hi, some quick feedback :

Makefile:
- "ONLY_FOR_ARCHS =  amd64 i386", why?


this was due to a build i tried on armv7 which failed with:

Error: selected processor does not support `fmrx r3,fpscr'

i figured this was inline x86 assembly but your question promted
metolook further. turns out its an issue with floating point
instructionson arm.

i tried copying other ports with `--target=generic' and
`--arch=generic' in CONFIGURE_ARGS with no success. then i tried
CFLAGS+='-mfloat-abi=hard' which the base gcc must not support?
pulling in ports' gcc got me a bit further:

{standard input}: Assembler messages:
{standard input}:18: Error: selected processor does not support 
`fstmfdd sp!,{d8,d9}'

{standard input}:19: Error: unknown pseudo-op: `.vsave'
{standard input}:24: Error: selected processor does not support 
`fcpyd d9,d0'
{standard input}:25: Error: selected processor does not support 
`fcpyd d8,d1'
{standard input}:37: Error: selected processor does not support 
`fcpyd d0,d9'
{standard input}:38: Error: selected processor does not support 
`fcpyd d1,d8'
{standard input}:46: Error: selected processor does not support 
`fldmfdd ip!,{d8-d9}'


unsure how to proceed, uncertain what OpenBSD support
for hardware floating point is like on armv7.


- "#GPLv2 only" please add a space, "# GPLv2 only"
- "COMMENT = Library for ..." lower-case first letter -> "library for"

pkg/DESCR:
- don't list WWW, it comes automatically from HOMEPAGE in Makefile

pkg/PLIST, Makefile:
- the linux-style shared library handling needs modifying.


the attached tarball should have fixed these issues.



Since you are pretty new to ports on OpenBSD, please get the first
one in good shape before sending others, as most of my comments apply
to the others too.



sure thing, sorry for the noise, i now realise it was
poor etiquette.

thanks for having a look at this,
toby/


rubberband.tar.gz
Description: application/gzip

Re: NEW: libmpack (needs discussion)

[Stuart Henderson]

We already have infrastructure for multiple flavours of lua ports, so I'd 
just use that. If the default lua version is changed we'll need a wider 
diff anyway because we'll need to switch from "unflavoured = 5.1" / "lua-XX 
prefix = 5.1" to something else, and that will need handling across the 
whole tree, so I wouldn't worry about that situation here.


--
 Sent from a phone, apologies for poor formatting.



On 17 January 2017 23:56:14 Edd Barrett  wrote:


Hi,

(CCing some people who have worked on lang/lua, hoping one of them knows
the answer to my question below).

This is (yet another) neovim dependency. libmpack (not to be confused
with libmsgpack):

---8<---
libmpack is a small binary serialization/RPC library that implements both the
msgpack and msgpack-rpc specifications.
--->8---

This isn't quite ready as it requires some thought. Neovim (on some
arches) will use this via LuaJIT, not plain Lua. We don't have to do
anything special to build against LuaJIT as plain Lua extensions are
binary compatible with LuaJIT [1].

What I don't think will work is mixing Lua versions. So how do we guard
against the case where (e.g.) the default Lua is bumped to target a
newer Lua than LuaJIT? This means the library will not be found by
LuaJIT.

Although I could explicitly set the Lua version used in this port,
setting it to anything other than the default version seems wrong too,
since then regular Lua users won't have access.

Do we need (versioned) lua flavors, e.g. -lua51, -lua52?

We could just use plain Lua across the board, but that would be a shame.
One of the attractions of neovim is to use a higher performance (and
a less "argh, my eyes, they burn") scripting language than vimscript.

Any ideas, or other comments?

[1] http://luajit.org/extensions.html

--
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk