similar to: app works when copied with tar, not with rsync

Seems our current libarchive? That support FreeBSD's tar implementation has a bug where it can create archives it cant read back. This can be seen by simply creating an empty tar.gz file and then trying to expand or list it. In doing the above you get the following error: tar: Unrecognized archive format: Inappropriate file type or format N.B. gtar can list and expand the created file

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:10.gtar Security Advisory The FreeBSD Project Topic: gtar directory traversal vulnerability Category: contrib Module: contrib_tar Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:10.gtar Security Advisory The FreeBSD Project Topic: gtar directory traversal vulnerability Category: contrib Module: contrib_tar Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

Hello people, me again ... Just an FYI this time, I think: 0[209]1 sunray1:/contrib > gtar zxf R-1.4.1.tgz tar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar: Error exit delayed from previous errors 2[210]1 sunray1:/contrib > gtar zxvf R-1.4.1.tgz "R-1.4.1/date-stamp" R-1.4.1/date-stamp gtar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar:

I reported the following vulnerability to AUSCERT, but they weren''t interested. People on this list might be, though! GNU tar is lazy about file creation modes and file owners when unpacking a tar file. Because GNU tar defaults to creating files owned by the userid running tar when the username is not found on your system, it can be possible to inadvertantly create setuid root

On Mon, Jul 06, 2020 at 01:58:35PM -0500, Eric Blake wrote: > so if we like the idea, we'd have to allow the user to specify > mutually-exclusive config parameters: either file= to something > within the file, or exportname=on to allow the client to choose, > where we then validate that exactly one of those two options is > configured. Right, I think that would be the way to do

Hello. I'm trying to use smbtar/smbclient (2.0.3) to copy an NTFS share on an NT Server, onto a Solaris 2.5 system. The NTFS partition is 10Gb. At the 2Gb mark, the tar stops. No errors, the file just stops. The process (smbtar) returns. Is this a problem with Solaris 2.5 ? I believe it is, and if I upgrade to 2.6, I can create larger tar files. However, does anyone know if

Hi folks, I've got a bit of a different scenario than I imagine most, and have spent the last 60 or 90 minutes searching Amanda list archives and googling, but did not come up with anything much. Then I went browsing around the Amanda website and found "vaulting" and was wondering whether this would suit my needs. I'm basically searching around for a backup solution and

Please, note: http://secunia.com/advisories/23115/ A port maintainer CC'ed. -- Dixi. Sem.

Ref: http://blogs.sun.com/timf/entry/zfs_bootable_datasets_happily_rumbling Ref: http://mediacast.sun.com/share/timf/zfs-actual-root-install.sh This is my errata for Tim Foster''s zfs root install script: 1/ Correct mode for /tmp should be 1777. 2/ The zfs boot install should allow you to have /usr on a separate zpool: a/ We need to create /zfsroot/usr/lib in the root partition and

I am copying from a rsync --daemon (have tried from both W2K/cygwin & Linux daemons) to a W2K machine. Some files get copied every time even though they haven't been touched since the last copy. I have experimented and deturmined that the file size seems to be important. If the file is between 926 & 933 bytes long it will always be copied!! Other sizes and possibly other aspects of

Hey folks, I looked at the man page and don't see any way to do this - maybe it is a function of the compression program used I dunno. Is there any way to get gtar to report on the compression it achieved? I can't just check file sizes because I'm writing data to tape. The basic problem is that I know how much data is there to begin with but I don't know how much room it took

Hi! A (small) tar archive with files exposing an apparent LLVM optimizer bug is attached; I didn't find a way to attach files in the bugzilla interface. What's the best way to report bugs taking several files to reproduce? -- Yossi -------------- next part -------------- A non-text attachment was scrubbed... Name: bugreport.tgz Type: application/x-gtar Size: 2242 bytes Desc: not

Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Apr 27, 2015 at 2:13 PM, Joerg Schilling > <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Les Mikesell <lesmikesell at gmail.com> wrote: > > > > There was no court case, but VERITAS published a modifed version of gtar where > > additional code was added by binary only libraries from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, if deliver is started with: deliver -f sender -d user (no -a option) and no Envelope-To header exists in the mail, two problems show up in this block in main(): if (destaddr == NULL) { destaddr = deliver_get_address(mail, "Envelope-To"); if (destaddr == NULL) { destaddr = strchr(user, '@') == NULL ? user :

I have some folders with a good amount of spam. While demonstrating full text search to a user, we found a folder that would crash dovecot while doing a fts. While splitting up the mailbox to narrow it down, I found there are a good number of messages in that folder that all made it crash in the same manner. I figured I'd narrow down a single one, get that fixed, then retest the rest. I

Hello, We have recently added a 64-bit 2 x Dual-Core Athlon server running Red Hat Enterprise Linux AS release 3 to allow for processing of large data sets (>4GB) in R. To integrate this server into our Linux cluster, I have been trying (unsuccessfully) to use Rmpi/lam-mpi to parallel process some of our scripts. While I have successfully compiled R 2.4.0 and lam-mpi 7.1.2 on this server using

My manifest includes this snippet class app_client_openbsd { $app_client_pkgs_obsd = [ ''glib2-2.24.1p2'', ''gtar-1.23p1'' ] package { "${app_client_pkgs_obsd}": ensure => ''installed'', source => "http://${installserver}/openbsd/${operatingsystemrelease}/packages/${hardwaremodel}/${name}.tgz", } This