11 Dec 15 22:33, you wrote to All:

 JS>  bundle c:\Radius\inbound\ca2f6c6c.fr1: renaming to .tos
 JS>  bundle c:\Radius\inbound\ca2f6c6c.tos: tossing in unsecure inbound,
 JS> security violation Renaming pkt/arc to .sec

 JS> If I manually unzip the .PKT files then call HPT the .PKT files toss fine.
 JS> ZIP is the agreed upon archiver.

*how* is your link zipping them? what is their zip command in their tosser?
what are the first 8 bytes (in hex please) of the file they are sending you?

 JS> I have tried both the internal Unzip support as well as an external
 JS> Unzip program to no avail.

what is your unzip command? here's both of mine and the spacing on the two
lines had to be like shown for some reason...


Unpack       "unzip -j -Loqq $a $f -d $p" 0 504b0304
Pack   zip   "zip -9 -j -q $a $f"


i should note that this system connects to only one other system and no packer
is defined for that system so we are sending raw PKTs to each other... this day
 in time, there's no real reason to be bundling up PKTs... especially when the
available protocols can compress on the fly during transmission just like a web
 server...

 JS> I am not sure where the "Security Violation" determination is coming
 JS> from.

probably because it cannot determine the originating system and/or the pkt
format...

)\/(ark

"So let me ask you a question about this brave new world of yours. When you've
killed all the bad guys, and when it's all perfect, and just and fair, and when
 you have finally got it exactly the way you want it, what are you going to do
with the people like you? The trouble makers. How are you going to protect your
 glorious revolution from the next one?" - The twelfth Doctor

... Any Co-Moderators here?"  <<BANG>>  "Any more?
---
 * Origin:  (1:3634/12.73)