But someone else, who finds the stick and has physical access to the laptop, can get access to all data stored on it. Therefore, in case one loses the stick, the passphrase stored on it must be revoked immediately. I haven't tried this with an arbitrarily generated file, though.

gargamel

A LUKS device has 7 slots in which to store key/passphrase material.
The first slot is taken by the passphrase you used to create the volume. If you add a key-file later, that information will be added to the second slot.

If you want to remove a key from a LUKS volume, (for instance because it has been corrupted) you can do so using the "cryptsetup luksKillSlot <device> <key slot number>" but in that case you will have to provide another valid key/passphrase.

The command "cryptsetup luksDump <device>" will show you which slots are occupied.

Eric

Oh, my Gawd, I hope so.

For those of us on a slow connection, downloading
all the necessary files to make Slackware64 mulitlib is a royal pain in the ***.

Yes that'd be great.

in /extra would be good for me and then slackpkg could deal with the updates.

samac

Hi Eric

I would like to know how does one include a kernel module for Crypto support.

You know... the "Math" thing is quite easy for me... Inversion over Galois Fields, Modular Arythmetics, all this is trivial ( well, when you have read *A LOT* about that in your spare time in youth... ), C++ algorythmics is not that difficult also...

The "Unknown" part for me is the implementation issue....
And I really would like to make a "customized" encryption protocol...

Do you know some good bibliography about this...?

( Outside of NSA Library of course... )




Hi Didier_Spaier

I undestand your point of view... but let me remind you of this... :


The technical specifications of the Airbus A 340 were long known before its first operational flight, by Boeing, due to security breaches in the comm links of work sessions among investigation centers in Europe, intercepted by Echelon Network, and fed to the NSA computing Behemoths...

... can you or anyone here ascert the loss that has already been done to Airbus because of this ?
Can anyone here ascert WHY is it that every single attempt to merge the European States into single unified political-military centralized command ( very much like the USA )is ill fated from the beginning... ? lots of coincidences... you know...


It is also known that the Battle of Midway might have ended differently if the United States Navy Signal Intelligence Corps had not deciphered radio transmissions... That way, the "Tokyo Express" logistic corridor might have been secured long enough to the Empire of Japan to develop its nuclear capability, forcing the USA to sign the end of hostilities in different terms...

There was a heavy ongoing investigation effort at the RIKEN in the begining of the forties... AFAIK Yoshio Nishina Sensei had a preliminary draft of an implosion type nuclear weapon, although he never adressed issues like the mitigation of the Rayleigh Taylor instability in the focusing of the convergent shock wave...


Anyway...

All this to say that regadless of the value of Freedom of Speech, ppl have the right to privacy and secrets as long as these rights do not endanger others...


- Henry Stimson, Secretary of State of the USA, on the closing of the "Black Chamber" and the MI-8.


BRGDS

Alex

Hi Alex_Vader,

I realize that, wouldn't Polish and British codebreakers have been able to decrypt a vast number of messages which had been enciphered using the Enigma machines (according to Wikipedia), issue of World War II could have been different (and I probably wouldn't be typing on a keyboard to answer you as I wouldn't have existed).

While I appreciate free speech, yet I recognize that "ppl have the right to privacy and secrets as long as these rights do not endanger others" and that this right is threatened nowadays, especially under the pretext of "fight against terrorism".

Best regards

1 members found this post helpful.

Quite true...

Polkit doesn't _REQUIRE_ PAM. It can be easily built with shadow. Check out the Slackbuilds of policykit in Slacky, Gnome SlackBuild and GWARE.

I am probably wrong for newer versions or the functionality required by KDE.

Indeed... Have you already tried building version 0.95 or even "polkit-1" (which is the code available in policykit repository). Distros are moving to polkit-1 which is a change in course for policykit. The git snapshot of polkit has a lot more PAM entanglement, which will require more work to undo than the relatively small fixes you could get away with in 0.9.

Also, in order to make use of polkit in the console (which we need because the average Slacker still startx X from the console with "startx") we need consolekit supporting the shadow utilities (or the reverse, shadow utilities supporting consolekit) as well.

It is not so simple unfortunately. If the *kit could be made to work with shadow that would be quite beneficial for Slackware.

Eric

I think it's not about the kits supporting shadow, but shadow must be made a simple front-end to the kits.

Anyway, are you talking for something different? I'm talking for the Policykit with the source package name "PolicyKit-0.9.tar.gz". Try with the "policykit-pamdisable" (http://mirrors.dotsrc.org/gsb/gsb-2....sable.patch.gz) patch. Then when configured, use that "--with-authfw=shadow". It's not a elegant solution, not at all. I prefer adding PAM.

It's time to open your minds and trash shadow in the way you know it.

ConsoleKit is an awesome little session tracking daemon...nothing bad about it.
PolicyKit is also not bad.
PAM is... a bit complex, but... ok.

PolicyKit 0.9 is already a thing of the past. It is not api-compatible with the current work on what is not called polkit-1.

The rapid morphing of applications like polkit-1 that provide a distro's core functionality (see how PolicyKit evolves and breaks everything in its path, it is unstable and buggy and causes other software to be unstable and buggy) is a clear sign that this kind of software development should really be avoided like the plague.

Unfortunately, the arrogance of "major distros" forces all the rest along this slippery slope and in the end, I think it will be inevitable that we as Slackware will either fall into this dark pit or else are forced to stop being a consumer desktop distribution.

Eric

Can anyone even begin to "ascert" the economic lost via the thousands, if not tens of thousands, of jobs lost across the entire American aviation industry because of a company who built aircraft it couldn't otherwise afford to build if it hadn't been for the "illegal" funding provided by a consortium of European countries?

1 members found this post helpful.

Well, I think that every country tries to protect its citizens' jobs, despite or using WTO's rules.

And American pension funds are among major shareholders, if not of EADS at least of more and more big European companies.

What about civil projects in the US funded by own capital of American companies... accumulated through revenues of contracts with DoD ?

I realize on the other hand that if not initially requested and funded by DoD, may be we wouldn't be communicating through the Internet as easier

I am not sure we be still on topic anyway

What is this "slippery slope" and how will it end, i.e., what will it do to Slackware (and Linux as a whole) if it were incorporated?
Thanks.