On Feb 27, 2016 1:30 AM, "Jean-Baptiste Thomas" <cau2jeaf1ho...@laposte.net> wrote: > > De: "Himanshu Shekhar" <irm2015...@iiita.ac.in> > > > The problem is about reading metacharacters. For example, username is > > "harry", password is "harry@123" , proxy server "10.101.12.1:8080". > > Thus, apt.conf would have text > > "http://harry:harry@123@10.101.12.1:8080";. > > > > This leads to unwanted behaviour. Apt stops reading the password after > > the first @, but it should after the last one. > > How to resolve this? > > I find your choice of words confusing. Firstly "@" is not a
Oops! I shall workout on that. > "metacharacter", not for the shell anyway. Secondly, if an at > sign ends up in apt.conf, it means that your script successfully > "read" it, right ? So it's not a shell problem, it's an Apt > problem. > Got it. My bad. , > Things you could try : > > - Editing apt.conf and manually replacing the first "@" by > "%40". Or maybe even "\@", "\\@", "\100", "\0100", "\x40", > that sort of thing. > > - Seeing what RFC 3986 and Apt's documentation have to say on > the matter. > Thanks! I got some help here http://askubuntu.com/questions/60217/apt-get-update-with-an-in-password-error
