[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#829740: (no subject)



Sorry, I did not get e-mail notifications so I missed your replies here
and answer late.

My Debian packaging questions (copyright lintian warning and combined
man page) have been sorted out after asking on Debian mentors mailing list.

I have forked and successfully packaged corridor for Debian. [1] There
are no lintian --pedantic warnings. One additional, rather simple [also
litian --pedantic warning free] dependency, genmkfile. [2]

The package has been uploaded to Whonix's deb repository and is
currently being tested. [3]

u:
> I'm not sure how useful this is exactly.

corridor can be used to check systems / programs that should cause only
Tor traffic really do. corridor can log any clearnet, non-Tor traffic.

Ideally, corridor gets installed on a physically isolated device running
Debian with two network adapters. Let's call that corridor-Gateway. Then
start Tails, TBB or Whonix behind such a corridor-Gateway. Should there
be any accidental clearnet traffic (leaks), then corridor could log it
and would block it.

Alternatively, corridor can be installed in a Debian based VM. Another
VM could run Tails, TBB or Whonix-Gateway. These VMs would be configured
to connect through corridor-Gateway.

Perhaps I am not the greatest corridor evangelist. Does that make more
sense now?

> It's still beta?

corridor by rustybird is perhaps not beta anymore? Quote:

"Not such a terribly early release anymore" [4]

I have opened a ticket to inquiry about the release status. [5]

Cheers,
Patrick

[1] https://github.com/adrelanos/corridor
[2] https://github.com/adrelanos/genmkfile
[3] https://www.whonix.org/wiki/Corridor
[4]
https://github.com/rustybird/corridor/commit/4390c2a3f8ff34983cb18074f1865a33f5255af0
[5] https://github.com/rustybird/corridor/issues/25


Reply to: