On 11/26/24 12:59, Mario Marietto wrote:
2)
# apt install nvidia-detect nvidia-driver
You first did an `update`.
Also the wiki at [1] suggest to install other PKGs.
[1]
https://www.reddit.com/r/debian/comments/1h08w9v/ssl_error8002system_libraryno_such/?rdt=41730
--
John Doe
/sign-file sha512
/var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der
/lib/modules/5.19.0-23-generic/updates/dkms/nvidia.ko
At main.c:298:
- SSL error:FFFF8002:system library::No such file or directory:
../crypto/bio/bss_file.c:67
- SSL error:1080:BIO routines::no suc
On Tue, Jul 06, 2021 at 11:06:22PM -0400, Stefan Monnier wrote:
> > I'm aware of that. My critique was specific to the "we take it out
> > because it's dangerous to the user" part.
>
> That's often an explanation but not the main motivation.
That would be even worse :)
The reason I'm "in" free s
> I'm aware of that. My critique was specific to the "we take it out
> because it's dangerous to the user" part.
That's often an explanation but not the main motivation.
For the `none` cipher, I think it was, tho.
IIRC the problem was that using the `none` cipher causes the
authentication to be e
d largely untested
functionality is part of what can be done for that.
>> If you want ancient crypto options, just run an ancient binary.
>> They're very easy to find in archive.debian.org.
> They're not as easy to run as soon as they start being outrun by
> their depende
>> If they have buffer overflow-style holes, those should be fixed.
>> Other than that I can't see how they can be less secure than the "none"
>> cipher.
> I guess since the "none" cipher isn't supported in debian's ssh
Good point.
> you will just drop this questionable line of argument?
It jus
On 7/6/21, Ralph Aichinger wrote:
> Hi, everybody, as a bullseye user I am seeing messages like
>
> | Unable to negotiate with 10.0.17.52 port 22: no matching
> | key exchange method found. Their offer: diffie-hellman-group1-sha1
>
> with increasing frequency, especially when trying to ssh into
>
I have a slightly different question about this issue.
when open ssh decided that dh keys, for public and global use were somehow
insecure, the ssh tool I use, sshdos, became limited allowing me to reach
shellworld, but not say the Linux shell provided with our office dreamhost
account any lon
On Tue, Jul 06, 2021 at 05:30:27PM -0400, Stefan Monnier wrote:
[...]
> > That's the attitude of authoritarian software: "my software is smarter
> > than you".
>
> I think the reality is a bit more subtle ;-)
>
> In most cases, the real driver is a desire to keep the code simple and
> to ease m
On Tue, Jul 06, 2021 at 04:45:50PM -0400, Michael Stone wrote:
[...]
> This is ridiculous [...]
Let's simply agree to differ.
Cheers
- t
signature.asc
Description: Digital signature
>> I think the first reaction should be to report it as a bug, so that the
>> old cipher is re-added. I think the same argument in favor of including
>> the "none" cipher should apply to including old deprecated ciphers.
> The old ciphers are generally removed for a reason: because they are hugely
ovide
them with things. But hey, it's a free world--dislike whatever you want.
The only authoritarian thing here is people trying to tell other people
what they need to put in the software they maintain.
If you want ancient crypto options, just run an ancient binary.
They're very ea
de the
> most secure and maintainable tool for the vast majority of users.
That's the attitude of authoritarian software: "my software is smarter
than you".
The authors are free to hold that position, but so am I to utterly
dislike it.
> If you want ancient crypto options, just
> Like you, I have been using CLI options to the ssh command to adjust the
> necessary algorithms if I need something "insecure".
You should be able to set that option for a specific (set of) hosts in
.ssh/config so you don't have to repeat it on the CLI every time.
> My thought is that once that
On Tue, Jul 06, 2021 at 03:20:43PM -0400, Stefan Monnier wrote:
If they have buffer overflow-style holes, those should be fixed.
Other than that I can't see how they can be less secure than the "none" cipher.
I guess since the "none" cipher isn't supported in debian's ssh
Good point.
you wil
On Tue, Jul 06, 2021 at 02:16:53PM -0400, Roberto C. Sánchez wrote:
Of course, the real answer is to not purchase products with "secure"
management that can't be upgraded when it becomes "insecure" management.
Sadly, this is not always possible. There are times where someone else
decides what
On Tue, Jul 06, 2021 at 02:11:21PM -0400, Michael Stone wrote:
>
> If you want ancient crypto options, just run an ancient binary. They're very
> easy to find in archive.debian.org.
>
Thankfully, Debian makes this sort of thing about as painless as it can
be.
> Of course, t
-cipher-honestly or something.
It's entirely too common for obsolete encryption options that are kept
for "compatibility" end up being a vector for compromise, and entirely
reasonable to remove such options in order to provide the most secure
and maintainable tool for the vast majority o
On Tue, Jul 06, 2021 at 01:43:07PM -0400, Michael Stone wrote:
> On Tue, Jul 06, 2021 at 01:02:49PM -0400, Stefan Monnier wrote:
> >>>I think the first reaction should be to report it as a bug, so that the
> >>>old cipher is re-added. I think the same argument in favor of including
> >>>the "none"
On Tue, Jul 06, 2021 at 01:02:49PM -0400, Stefan Monnier wrote:
I think the first reaction should be to report it as a bug, so that the
old cipher is re-added. I think the same argument in favor of including
the "none" cipher should apply to including old deprecated ciphers.
The old ciphers are
On Tue, Jul 06, 2021 at 12:05:41PM -0400, Stefan Monnier wrote:
> > Like you, I have been using CLI options to the ssh command to adjust the
> > necessary algorithms if I need something "insecure".
>
> You should be able to set that option for a specific (set of) hosts in
> .ssh/config so you don'
On Tue, Jul 06, 2021 at 10:40:00AM +0200, Ralph Aichinger wrote:
> Hi, everybody, as a bullseye user I am seeing messages like
>
> | Unable to negotiate with 10.0.17.52 port 22: no matching
> | key exchange method found. Their offer: diffie-hellman-group1-sha1
>
> with increasing frequency, esp
On Tue, Jul 06, 2021 at 10:40:00AM +0200, Ralph Aichinger wrote:
> Hi, everybody, as a bullseye user I am seeing messages like
>
> | Unable to negotiate with 10.0.17.52 port 22: no matching
> | key exchange method found. Their offer: diffie-hellman-group1-sha1
>
> with increasing frequency, esp
Hi, everybody, as a bullseye user I am seeing messages like
| Unable to negotiate with 10.0.17.52 port 22: no matching
| key exchange method found. Their offer: diffie-hellman-group1-sha1
with increasing frequency, especially when trying to ssh into
proprietary, obsolete stuff. Above comes from
Hi,
I have a TPM chip in my desktop computer
CPU : AMD A6-5400B APU with Radeon(tm) HD Graphics
System : HP Compaq Pro 6305 SFF
I don't use the onboard GPU for graphic display.
I got a discrete GPU based NVidia GT710 board.
If I could use my onboard GPU for number crunching this would be great.
Is
L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> Do not CC me, I am subscribed to the list. This is clear in the CoC
> for lists.debian.org,
Not CCing this once. I recently explained in great length why this point of
the CoC is broken and should be ignored.
> an
Do not CC me, I am subscribed to the list. This is clear in the CoC
for lists.debian.org, and it's prominently in the mail signature of
my mail you replied to.
On Fri, Jul 15, 2016 at 12:36:46PM +0200, Nicolas George wrote:
> L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> > FWIW, la
nts to that implementation. Well, MD5 is pretty much set in stone
and can be completely tested, so it is not a serious concern, but I wanted
to underline it for the record.
More importantly, by doing that, you are depriving yourself of all
optimizations that were introduced in more mature crypto libraries
Hi Everybody,
I am trying to cancel the erase data step of the partman-crypto
configuration via preseed (Jessie amd64).
The following lines are not working for me:
d-i partman-crypto/warn_erase boolean false
d-i partman-crypto/erase_data boolean false
d-i partman-crypto/confirm_erase_data
On 3 Aug 2014 17:16 +0200, from lazyvi...@gmx.com (B):
> * Is C a good candidate to write crypto?
>NOT AT ALL, a _very strict_ language should be used instead,
>such as ADA (think contracts, and do not think it is slow).
>Programs have bugs, we all know that, but cry
On Mon, 04 Aug 2014 04:08:15 +1000
Andrew McGlashan wrote:
> All good points, trouble I see is that even /good/ teams can become
> violated by someone ... NSA working with NIST is one example;
This is why an international team is important, with
redundant checks and controls.
> I'm
> not going
On 4/08/2014 1:16 AM, B wrote:
> The question raise the underlying problems:
> * Should we pay for good crypto (and very good cryptanalysis)?
> I think YES (stop yelling, think crowfunding;), because
> good crypto skills are rare and thus expensive;
> furth
On Sun, 03 Aug 2014 10:43:18 -0400
Harry Putnam wrote:
> Gack,,, I duplicated your posted URL before seeing your post
You will rot in a windows-only hell for that!
(without a debugger) *<;-p)
The question raise the underlying problems:
* Is crypto a specialist affair?
YES it is,
I see how to create raid devices:
d-i partman-auto-raid/recipe string \
1 2 0 ext2 /boot
/dev/sda1#/dev/sdb1
1 2 0 lvm -
/dev/sda2#/dev/sdb2
And then making lvm or crypto devices seems easy enough. However, how
do I create one on top of the other (I'd prefer luks inside lvm so
essage:
> >
> > [fail] Stopping early crypto disks vg-root_crypt (busy) failed
> >
> > I'm wondering what's goin on, and if there needs to be done something
> > about
> > it. Except for the message, everything appears to work fine.
>
> The basi
On Tue, 03 Dec 2013 17:43:39 +0100
Volker Wysk wrote:
> Hi !
>
> I've encrypted my hard drives, but when I shut down the computer, amongst the
> shutdown messages, I get the following message:
>
> [fail] Stopping early crypto disks vg-root_crypt (busy) failed
>
>
Hi !
I've encrypted my hard drives, but when I shut down the computer, amongst the
shutdown messages, I get the following message:
[fail] Stopping early crypto disks vg-root_crypt (busy) failed
I'm wondering what's goin on, and if there needs to be done something about
it.
On Mar 18, 2013, at 6:46 AM, Simon Hollenbach wrote:
Hello.
I set up an encrypted partition with randomly regenerated password
that I want to mount at /tmp with some older(6w) wheezy netinstall.
Apparently I need to create a file system there before mounting on
every boot, don't I?
I wrot
Hello.
I set up an encrypted partition with randomly regenerated password that I
want to mount at /tmp with some older(6w) wheezy netinstall.
Apparently I need to create a file system there before mounting on every
boot, don't I?
I wrote myself a little mount script, that:
Tries to mount ("mount /
07/07/2011 08:35, Jochen Schulz wrote:
>> Colin:
[trim]
>> I guess if I didn't have it I would need a separate dm-crypt and LUKS
>> partition for each of /, /home and swap which in turn would mean 3
>> separate keys + passwords.
>
> Yes. You could get away with only one passphrase if you put key f
Colin:
>
> Wow ... now I have a lot to do :-)
Hey, it's only about seven comands, plus some file editing. :) Don't let
my lengthy explanations scare you from doing it that way. It's a great
feeling to shuffle an OS around under your butt while it's running!
> Just glancing through I'm thinking if
Wow ... now I have a lot to do :-)
Just glancing through I'm thinking if I even need LVM. It was done
automatically by the installer.
I guess if I didn't have it I would need a separate dm-crypt and LUKS
partition for each of /, /home and swap which in turn would mean 3
separate keys + passwords.
E
Colin:
>
> I want to move the crypto volume to new disk so I can use it and boot
> from the new.
Thanks for the information. Now I know what your setup looks like. I am
still a bit unsure about your exact partition layout, because I didn't
ask for that either, but AFAICS you have
o move the encrypted volume to the new disk and
> keep the old one?
I want to move the crypto volume to new disk so I can use it and boot
from the new.
The old disk with the old crypto will be recycled to another machine.
$ pvs
PV VG Fmt Attr PSize PFree
/dev/m
Jochen Schulz:
> Colin:
>>
>> I don't remember the specifics when I did the install but here's what I got:
>
> Thanks. Now please add the output of 'pvs', 'lvs'.
Erm, that probably sounded rude. What I forgot to add is that I should
have asked for this information in the first place. Sorry!
J.
Colin:
>
> I don't remember the specifics when I did the install but here's what I got:
Thanks. Now please add the output of 'pvs', 'lvs'. And just to make
sure: you only want to move the encrypted volume to the new disk and
keep the old one?
J.
--
I use a Playstation to block out the existence
On Tue, Jul 5, 2011 at 10:57 AM, Jochen Schulz wrote:
> Colin:
>>
>> So I have this machine with a lvm crypto volume done with a debian
>> testing install. This is on a disk with 160GB.
>> But now I would like to clone it to a new disk: 500GB.
>> What are my opt
Colin:
>
> So I have this machine with a lvm crypto volume done with a debian
> testing install. This is on a disk with 160GB.
> But now I would like to clone it to a new disk: 500GB.
> What are my options?
What's the order of the block layers?
- LVM on top of dm-crypt on t
Hi all,
So I have this machine with a lvm crypto volume done with a debian
testing install. This is on a disk with 160GB.
But now I would like to clone it to a new disk: 500GB.
What are my options?
I thought about using clonezilla but I don't think it could resize a
lvm crypto volume...
C
On 24 March 2011 11:18, Dr. Ed Morbius wrote:
> Apropos some of the recent discussion we've had here of various Debian
> signing keys.
>
> A major CA (certificate authority) has issued fake SSL certs for
> Google.com, Yahoo.com, and Skype.com (and apparently 6 other sites)
> after its signing key
d for with the 'ssh-vulnkey'
command, and ssh client and server software are largely now configured
to disallow connections based on blacklisted keys (either server or
client keys may have been compromised).
Which is to say: crytpography is important, but it's not the only
attack vect
* Norbert Stöffler wrote:
> Any suggestions how to work around that?
Have you checked http://loop-aes.sourceforge.net/loop-AES.README ?
Sounds like § 2.8 is what you are looking for:
"Compatibility with other loop encryption implementations"
HTH
--
left blank, right bald
pgpyJ7218UhIi.pgp
Hi,
I have a crypted disk that I have been carrying with me through several
linux installations (SuSE, Ubuntu). Most recently I was still able to
mount it on Ubuntu using the following fstab entry:
/dev/hdb1 /bup ext2 encryption=twofish,noauto,user,exec
Recently I switched back to Debian. I
On Thu, Sep 27, 2007 at 11:00:52AM +0200, Jan Prunk wrote:
> I made a debian lenny installation with 1 drive. I do have another
> empty drive where I would like to set up RAID. The first drive is
> encrypted with crypto+LVM. i was googling for some informations on how
> to do that. If
Hello !
I made a debian lenny installation with 1 drive. I do have another
empty drive where I would like to set up RAID. The first drive is
encrypted with crypto+LVM. i was googling for some informations on how
to do that. If someone has an URL link of the installation procedure,
could you
Sorry, but my is not very clear, so:
I tried to setup a new install (using the Lenny install CD (1)), with
RAID1, crypto and LVM. Everything went fine during install and I even
did execute the steps required as of (2). The only problem I got, was
after the install/reboot, when the there seems to
Hello all,
Having received 2 identical hard drives, and trying to be a bit
paranoid, I am trying to setup a system with the following
characteristics:
/dev/hda1 + /dev/hdc1 -> RAID1 --> /boot
/dev/hda2 + /dev/hdc2 -> RAID1 + crypto + LVM -> / + swap + reserve
I am using the following
On Saturday 25 June 2005 20:53, nuno romano wrote:
> I got the following warning trying to create a
> crypto file system in hda10 partition of my
> hard disk: I did ->
>
> modprobe cryptoloop
> modprobe aes
>
> losetup -e aes-256 /dev/loop0 /dev/hda10
> Password: xxx
I got the following warning trying to create a
crypto file system in hda10 partition of my
hard disk: I did ->
modprobe cryptoloop
modprobe aes
losetup -e aes-256 /dev/loop0 /dev/hda10
Password:
ioctl: LOOP_SET_STATUS: Invalid argument
I have a PowerPC kernel 2.6.8,util-linux 2
Hello,
I'd like to use the crypto module. It's not there in the default kernel.
What kernel can I install on Woody to get that module? Is that possible,
or do I have to upgrade to compile the kernel myself, or upgrade to
testing?
Thank you!
Nicolas.
--
To UNSUBSCRIBE, email
usage claims to support the new /proc/crypto interface,
the source code for lomount.c refers only to the older, nested tree
under /proc/crypto/ciphers.
Based on the (fairly acrimonious) discussion that took place on the
cryptoapi-devel list in february[1], there seems to be a fair amount
of contro
Karsten M. Self writes:
> Does the registration apply to the software or the exporter?
The software.
> Either way, an email is very cheap insurance.
IIRC the notice must include full source.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
--
To UNSUBSCRIBE, email to [E
on Mon, Aug 18, 2003 at 09:48:11PM -0500, John Hasler ([EMAIL PROTECTED]) wrote:
> Karsten M. Self writes:
> > For "publicly available" encryption source code, the requirement is
> > notification of intent to export.
>
> For software in Debian/main that notification has already been filed and
> ne
Karsten M. Self writes:
> For "publicly available" encryption source code, the requirement is
> notification of intent to export.
For software in Debian/main that notification has already been filed and
need not be filed again. You can legally export computers with Debian
installed on them.
--
J
g to find a version of Linux that we could
> install, but we are being told that we can't export systems with
> current encryption. Do you have a version of Linux with 56-bit
> encryption that we could obtain?
This is my understanding of latest crypto regs. The situation is fluid,
and sin
Right now im running 2.4.20 kernel. Was curious if
anyone has been able to successfully patch the kernel
with the crypto updates to allow encrypted
filesystems.
I started to go through this
"http://encryptionhowto.sourceforge.net/Encryption-HOWTO.html";
And it doesnt really clearly s
On Wed, 2003-01-01 at 00:42, Jack O'Quin wrote:
> I did it the Debian Way, which works very well. :-)
>
> But, that *does* involve running make-kpkg, the Debian Way to compile
> kernel images. Charlie, if you haven't tried this script, it's a
> really clean way to make kernels and kernel module
Stefan Radomski <[EMAIL PROTECTED]> writes:
> It seems to me that Jack managed to get cryptoloop working without
> recompiling the kernel, he did it 'the debian way', as reported here:
>
> http://lists.debian.org/debian-user/2002/debian-user-200212/msg05110.html
I did it the Debian Way, which wo
On Tue, 2002-12-31 at 21:25, Charlie Reiman wrote:
> Thanks. You mean:
>
> http://lists.debian.org/debian-user/2002/debian-user-200212/msg04708.html
>
> It looks like I have to rebuild the kernel to get this working. As I
> mentioned, I really can't do that. Is it possible to get the patched
> c
> -Original Message-
> From: Stefan Radomski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 31, 2002 12:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Crypto issues
>
>
> Hi Charlie,
> please search the archive, exactly this issue was solved a week ago..
Hi Charlie,
please search the archive, exactly this issue was solved a week ago..
--
"boredom is not a burden anyone should bear"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rnel
ioctl: LOOP_SET_STATUS: Invalid argument
I've attempted to apt-get install anything that I thought would help but I'm
still coming up short.
What .deb to I need to get serpent (or any other decent crypto for that
matter) installed and recognized by the kernel?
I'd rather not r
anyone know how to fix this? i have the cryptoapi and cipher modules loaded,
but losetup doesn't work.
The cipher does not exist, or a cipher module needs to be loaded into the kernel
ioctl: LOOP_SET_STATUS: Invalid argument
unfortunetly, the cryptoapi list is no help. also, there's a two year o
Hi,
ist there an apt-get source for crypto-enabled kernel-sources and
util-linux packages? Please tell me if (and where!)
Thanks,
Karsten
--
Karsten Heymann <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
CAU-University Kiel, Germany
Registered Linux User #221014
* David Gardi ([EMAIL PROTECTED]) spake thusly:
> Hi to all,
> I am in posession of this small router device that has 1 ethernet and 1
> ISDN plug. By sticking this device onto my network it can perform
> various services such as NAT, dialout(ISDN) and some routing. It is
> configurable by telne
Hi to all,
I am in posession of this small router device that has 1 ethernet and 1
ISDN plug. By sticking this device onto my network it can perform
various services such as NAT, dialout(ISDN) and some routing. It is
configurable by telnetting to it by IP. The problem is that it is an old
piec
info> about it?
>
> please do make an effort to read the archives and/or bugreports on a
> package, before you post to the list. this question has been asked a
> number of times!
>
> anyway, it's a bug and it's been filed, and it's been fixed, so either
a bug and it's been filed, and it's been fixed, so either
jist --force-overwrite, wait until it reaches woody, or get
kdebase3-crypto from unstable...
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "
can I find info
about it?
"[EMAIL PROTECTED]:~# apt-get install kdebase-crypto
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
kdelibs3-crypto
The following NEW packages will be installed:
kdebase-crypto kdelibs3-crypto
0
also sprach Ralf G. R. Bergs <[EMAIL PROTECTED]> [2001.12.27.1847 +0100]:
> Hi there,
>
> I get duplicate files warning when trying to install kdelibs3 and kdelibs3-
> crypto on my Debian testing system:
>
> dpkg: error processing .../kdelibgs3-crypto_4%3a2.2.1-11_i386.de
Hi there,
I get duplicate files warning when trying to install kdelibs3 and kdelibs3-
crypto on my Debian testing system:
dpkg: error processing .../kdelibgs3-crypto_4%3a2.2.1-11_i386.deb (--unpack)
trying to overwrite '/usr/share/apps/kssl/caroot/ca-bundle.crt', which is also
Hi,
I am compiling the crypto options into kernel under
potato r4. The kernel part was a breeze but when I
try to compile util-linux, I ran into compilation
errors:
cc -c -O -pipe -O2 -m486 -fomit-frame-pointer -I../lib
-Wall -Wmissing-prototypes -Wstrict-prototypes -DNCH=1
-DSBINDIR=\"
<[EMAIL PROTECTED]>
To: cryptography@wasabisystems.com, [EMAIL PROTECTED]
Subject: Please make stable NON-US homes for strong crypto projects
It's clear that the US administration is putting out feelers to
again ban publication of strong encryption. See:
http://www.wired.com/ne
on Wed, Apr 25, 2001 at 01:24:59PM -0500, Stephen E. Hargrove ([EMAIL
PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> i'm trying to set up security on konqueror. it advises me that i
> need to install the kdebase-crypto package. however, apt-g
kdebase-crypto IS in non-free. I have it installed from that particular
apt line, except I use unstable (actually, I had some problems with
non-US some time back so also added ftp.debian.nl, but that shouldn't
matter too much as they're the same computer). Perhaps you just caught a
w
ere.
> > That's correct for FTP, but not for HTTP. (Don't you love virtual
> > hosting?)
>
> deb ftp://non-us.debian.org/debian-non-US/ testing/non-US main contrib
> non-free
> deb http://non-us.debian.org/ testing/non-US main contrib non-free
>
> # apt-get
rg/debian-non-US/ testing/non-US main contrib
non-free
deb http://non-us.debian.org/ testing/non-US main contrib non-free
# apt-get update
# apt-get install kdebase-crypto
E: Package kdebase-crypto has no installation candidate
so, either i'm an idiot (high probability)
"Stephen E. Hargrove" <[EMAIL PROTECTED]> wrote:
>On Fri, 27 Apr 2001, John Galt wrote:
>> deb http://non-us.debian.org/debian-non-US/ testing/non-US main contrib
>> non-free
>>
>> (single line...)
>>
>> crypto packages are in non-US.
>
>
On Fri, 27 Apr 2001, Stephen E. Hargrove wrote:
> On Fri, 27 Apr 2001, Simon Law wrote:
>
> > I'm guessing you're running testing? kdebase-crypto is in
> > unstable, and I'm guessing that it hasn't filtered down into testing yet.
> > If you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 27 Apr 2001, John Galt wrote:
>
> Hrm. You need
>
> deb http://non-us.debian.org/debian-non-US/ testing/non-US main contrib
> non-free
>
> (single line...)
>
> crypto packages are in non-US.
okay, i added the
Hrm. You need
deb http://non-us.debian.org/debian-non-US/ testing/non-US main contrib
non-free
(single line...)
crypto packages are in non-US.
On Fri, 27 Apr 2001, Stephen E. Hargrove wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Fri, 27 Apr 2001, Sim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 27 Apr 2001, Simon Law wrote:
> I'm guessing you're running testing? kdebase-crypto is in
> unstable, and I'm guessing that it hasn't filtered down into testing yet.
> If you want, you can just download th
On Fri, 27 Apr 2001, Stephen E. Hargrove wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> i'm trying to get konqueror set up to access https pages. the setup tells
> me that i need to install kdebase-crypto, but apt-get install
> kdebase-crypto responds:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'm trying to get konqueror set up to access https pages. the setup tells
me that i need to install kdebase-crypto, but apt-get install
kdebase-crypto responds:
Package kdebase-crypto has no available version, but exists in the
database.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i'm trying to set up security on konqueror. it advises me that i
need to install the kdebase-crypto package. however, apt-get install
kdebase-crypto results in:
Reading Package Lists... Done
Building Dependency Tree... Done
Package kdebase-c
Personally, I rarely use the debianized kernel source... to impatient
to wait for new releases to be packaged! :-) For whatever it's worth,
I'm having good results with the crypto patches and upstream source.
The one thing to watch out for is loopback filesystems (whether
encryp
[EMAIL PROTECTED] wrote:
>
> Hi,
> I want to compile the 2.4 kernel + crypto patch.
> apt-getting the kernel-source is no problem, but the international
> kernel patch isn't yet debianized.
>
> What's the best option?
> -Patching the debianized kernel sour
Hi,
I want to compile the 2.4 kernel + crypto patch.
apt-getting the kernel-source is no problem, but the international
kernel patch isn't yet debianized.
What's the best option?
-Patching the debianized kernel source.
-Patching the non-debianized kernel source.
Thanks for reading,
Jurgen
[EMAIL PROTECTED] wrote:
>I get this error after an "apt-get install kdebase-crypto"...
>Package kdebase-crypto has no available version, but exists in the database.
>This typically means that the package was mentioned in a dependency and
>never uploaded, has been obsolet
I get this error after an "apt-get install kdebase-crypto"...
Package kdebase-crypto has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the c
1 - 100 of 122 matches
Mail list logo
